Payment rhythm
24 h · hourly buckets · America/Los_Angeles
00061218
Data healthChecking coverage…Details
Source coverage is shown below. A dashboard refresh does not mean all sources are current.
Checking data health…
How these figures are sourced
Revenue, orders and AOV in the sales reports use Stripe sales data;
purchase CVR and checkout completion use PostHog.
MRR run-rate uses Stripe-backed subscription data, while churn, recovery and
MRR movement use the subscription event ledger. Each report retains its coverage and
fallback notes. Local database coverage may be incomplete; compare sources in Reconciliation.
Summary
Across your business Source-specific snapshots
Revenue · last 30 days Stripe · daily gross
Conversion Funnel PostHog · events · proj 313971 · ◆ Vidalytics VSL
Initial purchase declines Stripe · charge attempts
Overlap Insights Stripe + PostHog + Meta + lifecycle
Upsell take rate Database · orders · eligible-base scoped
Global visitor & purchase locations PostHog visitors × Stripe purchases
Attribution
Open Attribution to load Meta tracking setup.
Open Attribution to load the Google Ads card.
Meta Ads · channel operations Meta · spend & ROAS
Retention
Lifetime value report Stripe · first paid purchase
MRR run-rate
Rebills Stripe · renewals · /v1/invoices
First-renewal rate Stripe · cycle 2 · first renewal
Dunning Stripe · renewal invoices
Rebills calendar Stripe · daily renewals · this month
Recovery Database · subscription_events
Churn Database · subscription_events
Cancellation surveys & payment failures Stripe
Retention & LTV Database · subscription_events
Email performance GoHighLevel · email · deliverability
Audit
Data audit missing · malformed · stale · miscalculated
Reconciliation Stripe canonical ↔ DB · GHL · PostHog · Meta
Data sources & timezones UTC canonical
All windows are computed in Pacific (America/Los_Angeles). Current window: —
| Source | Native timezone | Window translation | Alignment |
|---|---|---|---|
| PostHog · funnel | project: America/Chicago | toDateTime('…Z') → UTC (verified) | ✓ UTC |
| Stripe · sales / payments | UTC (unix epoch) | created[gte/lt] = unix seconds | ✓ UTC |
| MySQL · orders / subscriptions | UTC (app writes UTC Dates) | window instants vs occurred_at | ✓ UTC |
| GoHighLevel · reconciliation | location timezone | opps by createdAt (ISO / UTC) | ✓ UTC |
| Vidalytics · VSL retention | account tz · day granularity | dateFrom/dateTo = UTC date | ~ ±1 day |
| Meta · reconciliation | ad-account tz (reporting) | unix start/end_time | ~ acct-tz |
Every source receives the same UTC instant range; each translates it to its own format. The two ~ rows are day- or account-tz-attributed and can differ by up to a day at window edges — treat them as approximate, not instant-precise. (The standalone /sales chat command uses America/Chicago day boundaries and is intentionally separate from this dashboard.)
Tracking
Front-end tracking setup First-party · script install
No-code events First-party · published rules
Identity event graph Database · identity_events
Live feed
Live Orders Stripe · paid charges
Loading paid orders…
Paid charges
rolling 24 h · funnel.build · gross before refunds and fees
Charge sizes
$0
Meta spend today
0024
Meta's own day and attribution. A different window from the 24-hour charges, so it is not matched to them.
On site now Realtime · identity_events
client.js event feed Realtime · identity_events
Replays
Session replays First-party · session recorder
Signals Derived · from replay recordings
Heatmaps
Page heatmaps Derived · from replay recordings
Funnels
Funnel reports Database · mirrors · person-stitched
Experiments PostHog · experiments · vendor-computed
Connections
Assistant