Google Ads and GA4 tracking for React
GA4 on React needs explicit route-change events. The default behaviour records the first page view and nothing else, which produces a session count that looks right and a page view count that is silently wrong.
Free30 minutesNo obligation
React + Google · what breaks
What goes wrong on React
- 01
Route changes fire no page views
A client-side navigation isn't a page load.
- 02
Hydration timing
Events firing before data exists dispatch empty values.
- 03
Effects double-firing
StrictMode in development, and sometimes carelessness in production.
- 04
Ad blockers hitting client-side tags
More effective against SPA bundles than against server calls.
React + Google · the fix
What changes — React + Google
Route changes emitting proper events
Bound to the router.
Events firing after data is available
Not before.
Money events from your API
Removing client-side fragility entirely.
React + Google · architecture
How the Google destinations behave on React
Explicit route-change events, or GA4 sees one page per session.
- 1
Route-change events bound to the router
The single most important fix on any SPA.
- 2
Events after hydration
Or with server-rendered values.
- 3
transaction_id from your backend
Not generated client-side.
- 4
All four click parameters captured on first load
Before any routing happens.
- 5
Enhanced Conversions from the API
Where the customer data actually is.
React + Google · diagnose
Where React tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Navigate between routes and watch for events
Nothing firing is the classic SPA fault.
- 02
Check whether first events have empty values
A hydration timing signature.
- 03
Grep for duplicate pixel initialisations
Components mounting more than once.
- 04
Confirm where the money event is emitted
Client or API.
- 05
Reconcile against your backend records
For a closed month.
React + Google · prove
The QA evidence — React + Google
Run on React specifically, on a live conversion rather than in preview mode.
Source of truth
your backend order or CRM records
- Route changes confirmed emitting events on a real navigation.
- First-render events confirmed carrying populated values.
- No duplicate events from remounting components.
- Money events confirmed arriving from the backend.
- Counts reconciled against backend records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
React + Google · free audit
What we check in the free audit
- Navigate between routes and watch for events
- Check whether first events have empty values
- Grep for duplicate pixel initialisations
- Confirm where the money event is emitted
- Reconcile against your backend records
Checked against
your backend order or CRM records
Free30 minutesNo obligation
React + Google · when not to buy
When you don't need this on React
Worth reading before you buy anything, from us or anyone.
- If your React app already emits route-change events and sources money events from the API, the SPA-specific problems don't apply.
- Your own engineers can do all of this — it's their codebase and there are no platform constraints.
- If your app is a single-page marketing site with no routing, the route-change problem doesn't exist.
- Reconcile against your backend before assuming anything is broken.
React + Google · what we deliver
What gets built for Google on React
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
Written guarantee
95%+ tracking accuracy
Measured against your backend order or CRM records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
React + Google questions, answered
Bind an event to your router's navigation callback. Every router exposes one; nothing emits it automatically.
On first load, before any client-side routing. Store them for later backend events.
From your API, yes. From DOM selectors in a re-rendering tree, unreliably.
One view per session is the signature of missing route-change events.
Free · 30 min
Get Google Ads and GA4 right on React
WhatsAppFree30 minutesNo obligation
