Add GA4 on checkout
Google Analytics 4 (GA4) helps you measure checkout activity in a GA4 property. In AtomicPay, GA4 is configured per product in the product checkout integrations area.
Use this guide when analytics needs a direct measurement ID on checkout, when you are validating funnel or campaign performance in GA4, or when you want DebugView confirmation before scaling traffic. Combine GA4 with checkout links and UTMs and Campaigns, not as a substitute for AtomicPay revenue reporting in Financial Overview.
What GA4 on checkout controls
| Area | Purpose |
|---|---|
| Measurement ID loading | Sends checkout activity to one or more GA4 properties. |
| Checkout-scoped analytics | Applies to the configured product checkout path. |
| Validation rules | Requires valid G-XXXXXXXXXX IDs and no empty rows on save. |
| Launch verification | Supports GA4 DebugView or real-time validation. |
| Multi-property setups | Allows up to 5 measurement IDs per product when needed. |
GA4 vs GTM vs ad pixels
| Tool | Best for |
|---|---|
| GTM on checkout | Managing many tags from one container |
| GA4 on checkout | Direct measurement in a GA4 property |
| Facebook pixel | Meta ads attribution |
| Pixels and attribution | Overall tracking strategy |
| Financial Overview | Revenue, fees, refunds, and net performance |
Configure GA4 on checkout
- Confirm you are in the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the product that should send checkout events to GA4.
[Screenshot: Product opened — checkout integrations area accessible.]
- Go to the product checkout integrations area.
[Screenshot: Checkout integrations tab — GA4 section visible.]
- Enable GA4.
[Screenshot: GA4 toggle enabled on product checkout.]
- Add one or more measurement IDs in the format
G-XXXXXXXXXX.
[Screenshot: Measurement ID field — G-XXXXXXXXXX format entered.]
- Add up to 5 measurement IDs per product and remove empty rows before saving.
[Screenshot: Multiple measurement ID rows — empty rows removed.]
- Save the configuration.
[Screenshot: GA4 configuration saved successfully.]
- Open the live checkout link as a buyer.
[Screenshot: Live checkout opened — buyer path for GA4 validation.]
- Use GA4 DebugView or real-time reports to confirm activity.
[Screenshot: GA4 DebugView — checkout event visible in real time.]
[Screenshot: GA4 and Sales — purchase cross-checked across systems.]
What to verify before launch
| Check | Why it matters |
|---|---|
| Measurement ID belongs to the correct property | Wrong property corrupts analytics decisions. |
| Checkout is published | Draft checkout changes can invalidate tests. |
| UTMs are already on campaign links | GA4 does not replace UTM naming. |
| No duplicate purchase events | Coordinate with GTM and ad pixels. |
| Revenue questions still use AtomicPay reports | Use Financial Overview for net revenue and refunds. |
Best practices
- Test from the exact checkout link buyers will use.
- Document which GA4 property maps to which product or campaign.
- Review Campaigns after first tracked sales.
- Keep analytics validation separate from withdrawal readiness.
- Fix attribution gaps at the link level before blaming GA4.
Common mistakes
- Enabling GA4 on the wrong product.
- Saving blank measurement rows.
- Double-counting events with GTM and direct GA4 together.
- Using GA4 as the only source for payout or refund decisions.
- Testing on an outdated checkout URL.
FAQ
Is GA4 on checkout the same as ad pixels?
No. GA4 measures analytics activity in your Google Analytics property. Ad pixels in pixels and attribution and Facebook pixel setup focus on platform-specific campaign attribution.
Why is save blocked?
Common causes are an empty measurement row, an invalid ID format, or GA4 enabled with no measurement IDs added.
Can GA4 and GTM both be enabled?
Yes. Coordinate event design with whoever manages GTM on checkout.