Checkout tracking guide

Checkout Attribution in GA4

When source and campaign look correct on the landing page but disappear or change near checkout, inspect the checkout path instead of rebuilding every campaign URL.

Build a clean test URL Manual setup

Campaign attribution flowing from landing page through checkout to GA4 purchase reporting

Core question

Does the same session keep campaign context from landing page to checkout to purchase?

Common break

Checkout runs on a different domain, subdomain, embedded flow, or app-controlled step.

Practical test

Click one campaign URL, complete a test checkout path, and compare the event sequence in GA4.

Checkout attribution QA steps

Generate one clean campaign URL and save the exact source, medium, and campaign values.
Click the URL and confirm GA4 sees the landing visit.
Move through product view, add to cart, and begin checkout.
Watch whether the session continues or a new source appears.
Complete a supported test purchase path if your platform allows it.
Compare begin_checkout and purchase against the original campaign context.

What can break attribution

Area	Symptom	Check next
Checkout domain	Checkout starts a new session or source.	Cross-domain behavior, platform docs, checkout settings.
Payment redirect	Payment provider appears as source.	Referral handling and return URL behavior.
Consent banner	Events start late or appear incomplete.	Consent mode, region behavior, tag firing order.
Duplicate tracking	Events duplicate or disagree.	Native integration, GTM, app scripts, theme code.

What to record during QA

Landing URL:
UTM source:
UTM medium:
UTM campaign:
Landing page event seen:
view_item seen:
add_to_cart seen:
begin_checkout seen:
purchase seen:
Source changed during checkout:
Notes:

Important limits

Some checkout behavior is controlled by the ecommerce platform and may not be fully editable.
GA4 Realtime is useful for launch QA but not a final truth source for every attribution question.
Privacy settings, consent, ad blockers, payment redirects, and cross-domain flows can affect reporting.
Transparent tracking is the goal. Do not hide redirects or misrepresent the destination.

Keep URL QA and checkout QA separate

That split makes it much easier to explain what is broken and what still works.

Build a clean test URL