Integrations

Analytics

Track visitors and conversions with Google Analytics 4, Google Tag Manager and the Meta (Facebook) Pixel. Configure everything in Admin → Analytics Settings — no code edits.

Google Analytics 4

analytics.google.com → Admin → Data Streams → your web stream.
Copy the Measurement ID (looks like G-XXXXXXXXXX).
Paste it into the GA4 field and enable.

Google Tag Manager (optional)

If you prefer to manage tags through GTM, paste your container ID (GTM-XXXXXXX) into the GTM field. Use GTM or GA4 directly — not usually both.

Meta (Facebook) Pixel

Meta Events Manager → Data Sources → your Pixel.
Copy the Pixel ID (a long number).
Paste it into the Pixel field and enable.

📈

Once saved, the tracking snippets are injected into your storefront automatically, and the IDs are forwarded to the Customer app so in-app screens are tracked too.

Conversions API (server-side)

Browser-side pixels lose events to ad blockers, iOS tracking prevention and dropped page-unloads — purchases are exactly the events you least want to lose. The Meta Conversions API sends the purchase event from your server instead, so it arrives regardless of the browser.

Meta Events Manager → your Pixel → Settings → Conversions API → Generate access token.
Paste the token into the Conversions API field in Admin → Analytics Settings.
Save. Purchase events now fire server-side as well as from the browser.

Meta de-duplicates the browser and server copies of the same purchase automatically, so you will not double-count.

Turning tracking on per surface

Two master switches decide where tracking runs at all:

Track on Website

Injects the scripts into the storefront's public pages.

Track on Customer App

Exposes the same IDs to the mobile app via config.

Switching a surface off suppresses every provider on that surface at once — useful when you need to stop tracking quickly without deleting your IDs.

📱

App-side IDs are read when the app fetches its configuration, so a change reaches installed apps on their next launch, not instantly.

Verify it is working

GA4

Google Analytics → Reports → Realtime. Open your storefront in a private window; you should appear within ~30 seconds.

Meta Pixel

Events Manager → Test Events, or install the Meta Pixel Helper browser extension and load your storefront.

Conversions API

Events Manager → Test Events shows a "Server" source alongside the browser event once a real order completes.

GTM

Use GTM's Preview mode to confirm the container loads and your tags fire.

Troubleshooting

Nothing appears in Realtime

Wrong ID format (GA4 is G-…, not the old UA-…), the surface switch is off, or your own visit is filtered by an internal-traffic rule.

Pixel Helper finds no pixel

Usually an ad blocker in your own browser — test in a clean private window before assuming it is broken.

Purchases missing but pageviews fine

The purchase event fires on the order-confirmation step; if buyers are redirected away by a payment gateway and close the tab, only the Conversions API captures it. Add the token.

Events counted twice

The same pixel is loaded both directly and again through GTM. Use one path, not both.

🍪

Depending on your region (GDPR/CCPA), you may need a cookie-consent banner before loading analytics. Add your cookie policy text in Admin → Settings.

👉

Next: reCAPTCHA & Turnstile.