Help Center

Connecting GA4 is a one-click OAuth flow:

1. From your Dashboard, click "Add data source" and select Google Analytics 4.
2. You'll be redirected to Google's sign-in page. Sign in with the Google account that has access to your GA4 property.
3. Google will ask you to grant Morning Pulse read-only access to your Analytics data. Review the permissions and click "Allow."
4. Select the GA4 property you want to track from the dropdown.
5. Done. Morning Pulse will immediately start pulling yesterday's data.

If your property is missing, check the following:

• Right Google account: Make sure you signed in with the Google account that has access to the GA4 property. Many people have multiple Google accounts — try signing out of Google entirely, then signing back in with the correct one.
• GA4, not Universal Analytics: Morning Pulse only supports GA4 properties (not the older Universal Analytics / UA-XXXXXXX). If you're still on UA, you'll need to create a GA4 property first.
• Sufficient permissions: You need at least Viewer role on the GA4 property. Ask your Google Analytics admin to grant you access under Admin > Property Access Management.
• Recently created property: Brand-new GA4 properties can take up to 24 hours to appear in the API. Wait and try again.

If none of these work, disconnect and reconnect Google Analytics from Dashboard > Settings > Connections.

A few common causes:

• Data processing delay: GA4 data can take 24-48 hours to fully process. If you connected today, your first complete report arrives the day after tomorrow.
• Wrong property selected: Double-check you selected the correct GA4 property in Dashboard > Settings > Connections.
• Filters or data streams: If your GA4 property has internal traffic filters or limited data streams, the numbers may look lower than expected. Verify in GA4 directly that the property has real traffic data.
• Token expired: In rare cases, your Google OAuth token may have expired. Go to Connections, click "Reconnect" next to GA4, and re-authorize.

If the problem persists after checking all of the above, send us an email at support@morningpulse.app with your property ID and we'll investigate.

Yes. Each "app" in Morning Pulse can have its own GA4 property. If you have a website and a mobile app each with their own GA4 property, create two apps in Morning Pulse and connect the respective properties.

How many apps and properties you can track depends on your plan: Free covers 1 app and 1 property; Starter covers 1 app with unlimited properties; Pro and Agency give you unlimited apps and unlimited properties. Each app gets its own separate email so reports stay clean and focused.

App Store Connect uses API keys for authentication. Here's the step-by-step:

1. Sign in to App Store Connect at appstoreconnect.apple.com.
2. Navigate to Users and Access > Integrations > App Store Connect API.
3. Click "Generate API Key" (or use an existing one).
4. Set the role to "Sales and Reports" or "Finance" — this gives Morning Pulse read-only access to the data it needs without any write permissions.
5. Download the .p8 private key file. You'll also need the Key ID and your Issuer ID (shown at the top of the API keys page).
6. In Morning Pulse, go to Dashboard > Add data source > App Store Connect.
7. Paste your Issuer ID, Key ID, and upload (or paste the contents of) the .p8 key file.
8. Select the app(s) you want to track, then click "Connect."

We recommend the "Sales and Reports" role. Here's why:

• Sales and Reports — Gives access to app units, impressions, page views, in-app purchases, and proceeds. This is exactly what Morning Pulse needs and nothing more.
• Finance — Also works, but includes financial reporting data you may not need. Use this if you want revenue breakdowns by territory.
• Admin / App Manager — More permissions than necessary. We strongly recommend against using these roles for Morning Pulse.

The principle of least privilege: give Morning Pulse only the access it needs.

Common connection issues and fixes:

• "Invalid API key" — Double-check that you pasted the correct Issuer ID, Key ID, and .p8 key content. The key content should start with -----BEGIN PRIVATE KEY----- and end with -----END PRIVATE KEY-----.
• "Key revoked or expired" — If someone on your team revoked the API key in App Store Connect, you'll need to generate a new one and reconnect.
• "Insufficient permissions" — Your key's role may not include sales data. Verify the role is set to Sales and Reports or Finance.
• "No apps found" — The API key may be too new. Apple can take up to 30 minutes to propagate new keys. Wait and retry.
• "Data unavailable" — Apple considers data complete 2 days after the reporting date, with delays of up to 72 hours documented. See "Why is my App Store data delayed or missing?" below for full details.

This is an Apple limitation, not a Morning Pulse limitation. Apple's Analytics Reports API has several built-in restrictions that affect when and whether data appears.

2-day completeness rule

Apple considers data complete 2 days after the reporting date. If today is April 1, yesterday's data (March 31) won't be considered final until April 2. This is Apple's official data completeness window.

First report delay

When you first connect App Store Connect, your initial report takes approximately 24-48 hours to generate. After that, reports are generated daily — but always subject to the 2-day completeness lag.

In practice: up to 72 hours (sometimes more)

Apple's own documentation states data can be delayed up to 72 hours. In practice, delays of 3-5 days have been reported by developers. The App Store Connect dashboard itself has the same limitation — the closest selectable day is typically 2 days ago.

What this means for your daily email

• Your morning email will typically contain App Store data from 2-3 days ago, not yesterday.
• GA4 data is faster (usually available within hours), so GA4 metrics will be more recent in the same email.
• Morning Pulse clearly labels the date range for each data source so there's never confusion.

Additional restrictions that can suppress data

• Privacy thresholds — Apple omits data rows with fewer than 5 unique users or devices. For low-volume apps, some metrics simply won't appear regardless of timing.
• Opt-in dependency — Usage metrics (sessions, installs/deletions, crashes) are collected only from users who opted in to share diagnostics. Low-volume apps may not have enough opted-in users to produce data at all.
• Statistical noise — Apple adds a small amount of noise to metrics to prevent reverse-engineering individual activity, which can cause minor discrepancies.
• Data gaps — Developers have reported occasional gaps (e.g., data on day 1, nothing on days 2-4, then data resumes). This is a known Apple API behavior.

If data is missing for more than 5 days, check your connection status in Dashboard > Settings > Connections, or contact us.

Stripe uses a Restricted API Key with read-only access — no OAuth needed. You read your own Stripe data directly. Here's how:

1. Sign in to your Stripe Dashboard at dashboard.stripe.com.
2. Navigate to Developers > API keys.
3. Click "Create restricted key".
4. Name it something like Morning Pulse (read-only).
5. Set the following permissions to "Read" only:
   • Charges — to pull daily purchase totals
   • Customers — to count active customers
   • Subscriptions — to calculate MRR and ARR
   • Balance Transactions — to compute revenue by country and monthly totals
6. Leave all other permissions set to "None."
7. Click "Create key" and copy the key (starts with rk_live_...).
8. In Morning Pulse, go to Dashboard > Add data source > Stripe.
9. Paste the restricted key and click "Connect."

Morning Pulse needs read-only access to exactly four Stripe resources:

All other permissions should remain set to "None." Never use a full-access secret key (sk_live_...) — always create a restricted key for Morning Pulse.

Once connected, your daily Morning Pulse email can include:

• Yesterday's total purchases — Successful charges from the previous day.
• Current MRR — Monthly Recurring Revenue calculated from active subscriptions.
• Current ARR — Annual Recurring Revenue (MRR × 12).
• Active customers — Total customers with at least one active subscription.
• Revenue by top 5 countries — Geographic breakdown of your revenue.
• Current month total revenue — Running total for the calendar month.

All metrics include trend comparisons vs. yesterday, last week, and last month — just like every other data source in Morning Pulse.

Common issues and fixes:

• "Invalid API key" — Make sure you pasted the full restricted key, including the rk_live_ prefix. Test mode keys (rk_test_) won't return production data.
• "Insufficient permissions" — Your restricted key is missing one or more required permissions. Go to Stripe Dashboard > Developers > API keys, find your key, and verify that Charges, Customers, Subscriptions, and Balance Transactions are all set to "Read."
• "Key revoked" — Someone on your team may have deleted or rolled the key. Create a new restricted key and reconnect in Morning Pulse.
• "No data available" — If your Stripe account is brand new or has no charges yet, there's nothing to report. Morning Pulse will start populating data as soon as transactions occur.
• Using the wrong account — If you have multiple Stripe accounts (e.g. test vs. production), verify you're creating the key in the correct account by checking the account name in the top-left of the Stripe Dashboard.

If none of these resolve the issue, email support@morningpulse.app with the error message you see and we'll investigate.

Use a live mode restricted key (rk_live_...) to track real revenue and customer data in your daily email.

Test mode keys (rk_test_...) only access Stripe's sandbox environment with fake data. They're useful if you want to preview how Stripe metrics look in Morning Pulse before going live, but they won't reflect real transactions.

To switch: disconnect the current Stripe source in Morning Pulse, create a new restricted key in the correct mode, and reconnect.

Shopify connects in one click — no API key to copy or paste. Morning Pulse installs as a Shopify app with read-only access to your orders. There are two ways to set it up:

Option 1 — Install from the Shopify App Store

1. Open the Morning Pulse listing on the Shopify App Store and click Install.
2. Approve the install on Shopify's consent screen — Morning Pulse only requests read access to your orders.
3. You'll land on Morning Pulse to sign in or create a free account. Your store is now linked; if it isn't yet tied to a specific app, attach it from Dashboard > your app > Attach Shopify.

Option 2 — Connect from your Morning Pulse dashboard

1. In Morning Pulse, open your app and go to Connect Shopify, then click Install via Shopify.
2. Enter your store domain (for example, my-store.myshopify.com).
3. You'll be redirected to Shopify to approve the read-only install, then sent straight back — the store attaches to that app automatically.

Once your store is connected, your daily Morning Pulse email can include:

• Orders — yesterday's order count.
• Net sales — yesterday's net sales, after refunds and discounts.
• Unique customers — how many distinct customers ordered.
• Average order value — net sales divided by orders.

Every metric includes trend comparisons vs. yesterday, last week, and last month, shown alongside your GA4, Stripe, App Store, and Google Play numbers in the same email.