Skip to content

See why your ad data and GA4 do not match

Review Meta Ads and Google Ads spend beside GA4-observed conversions and revenue. Pulse keeps each source separate and shows what data is available.

Account setup in minutesRead-only accessNo advertising changes
Pulse product preview
Illustrative 30-day period
Welcome, Guest!Here is what matters across your campaigns
Demo data
+18.6%
Spend€12,480
+24.3%
GA4-observed revenue€31,240
+8.7%
Blended ROAS2.50×
+15.2%
Leads captured487

Performance over time. Demo data

Spend and GA4-observed revenue
SpendGA4-observed revenue
30-day demo period · shared EUR scale
Illustrative values shown in the demo chart
PeriodSpendGA4-observed revenue
Sep 01€750€1,700
Sep 04€850€1,900
Sep 07€900€2,100
Sep 10€950€2,300
Sep 13€900€2,200
Sep 16€1,000€2,500
Sep 19€1,050€2,700
Sep 22€1,100€2,800
Sep 25€1,150€3,000
Sep 27€1,200€3,200
Sep 29€1,250€3,400
Sep 30€1,380€3,440
Meta and GA4 discrepancy21 conversions need review
Illustrative AI conceptExample: review the Leads_Form budgetA future assistant could suggest checking CPA stability before any budget decision.Not available in the current Alpha

Illustrative 30-day demo chart. Advertising spend bars and the GA4-observed revenue line share one EUR scale and trend upward overall. These are synthetic demo values, not live customer data.

Illustrative data
Illustrative product preview with synthetic values; the AI card is a future concept, not available in the current Alpha. This is not a customer dashboard or live dataset.

See where comparable sources differ

Pulse displays platform-reported and GA4-observed results side by side and does not treat a missing observation as zero.

Platform-reported ROAS

3.14×

Illustrative preview — no live data

GA4-observed ROAS

2.50×

Illustrative preview — no live data

Demo difference: GA4-observed ROAS is 0.64× lower

Illustrative preview — no live data

Clear source boundaries and honest data states

Pulse keeps platform-reported and GA4-observed results separate, uses goal-specific KPIs, and shows unavailable or stale data explicitly.

One dashboard for different campaign goals

Traffic, leads, messages, and sales remain separate. Pulse shows only the metrics supported by the selected campaign goal and connected source.

Goal-specific KPIs

Missing data is unavailable, never zero by default

Each source remains identifiable

Illustrative product preview
Traffic12,480Demo clicks · last 30 days
Leads286Demo leads · platform reported
Sales124Demo purchases · GA4 observed
Messages412Demo conversations started

Platform data and GA4 observations, side by side

Compare ad-platform results with GA4-observed conversions and revenue only where event definitions and reporting periods are genuinely comparable.

GA4-observed purchases and revenue

Consent-aware UTM sessions via Pulse Tag

No lead-quality or offline-sales claims without CRM data

Illustrative product preview
Platform reported3.14×
GA4 observed2.50×

Synthetic demo values use one matching 30-day period. Live comparison starts only after approved sources are connected.

Freshness, empty states, and provider errors

Pulse shows when data was last synchronized and distinguishes unavailable, disconnected, stale, and provider-error states.

Last successful sync and data freshness stay visible

Provider errors are shown without leaking sensitive payloads

No automatic replacement with demo data

Illustrative product preview
Freshness visibleThe last successful synchronization and data-through time are shown.
Provider error explicitA safe error state replaces stale assumptions or synthetic values.
Truthful empty stateNo campaigns or metrics is distinct from a reported zero.

Connect your data sources

Pulse supports Meta Ads, Google Ads, and GA4 through validated read-only connections. Each source remains separate and errors never become demo data.

ALPHA

Meta Ads

Spend, impressions, clicks, and results as reported by Meta.

Read-only connection; access remains scoped to the selected client.

ALPHA

Google Ads

Campaign spend and platform-reported results from Google Ads.

Read-only connection; access remains scoped to the selected client.

ALPHA

Google Analytics 4

GA4-observed website conversions, purchases, and revenue for the configured property.

Read-only connection; access remains scoped to the selected client.

ALPHA

Pulse Tag

Consent-aware UTM sessions and first-party website-event context.

Read-only connection; access remains scoped to the selected client.

Pulse reads data and cannot change advertising

Connections use the minimum read permissions required. Advertising write actions and automatic optimization are not available.

Read-only provider access

Pulse reads reporting data but cannot change campaign budgets, settings, or delivery.

Consent-aware measurement

Pulse Tag follows consent-management settings and data-minimization requirements.

Write actions unavailable

The current Alpha has no advertising write path.

Create your account and open Pulse

Start with a secure workspace, then connect approved read-only Meta Ads, Google Ads, and GA4 sources.

Read-only accessNo advertising changesMeta Ads, Google Ads, and GA4