Skip to main content

​
Pixel Tracking

TagadaPay handles client-side pixel tracking for your store. When you configure pixels in the dashboard, they’re automatically loaded and fired at the right moments during the checkout flow — no extra code needed.
Pixel tracking is not the same as analytics. Pixels fire client-side events to ad platforms (Meta, TikTok, etc.) for attribution and retargeting. Analytics (dashboards, reports, conversion metrics) is a separate feature in the TagadaPay CRM.

​
How It Works

  1. You configure pixel IDs in the TagadaPay dashboard (Settings → Integrations)
  2. TagadaPay loads the pixel scripts and fires the events — on the pages it hosts by itself, on the pages you code once you report your steps
  3. Each event reaches the pixels bound to that page on the canvas
There are two cases:
  • Pages TagadaPay hosts (checkout, offers, thank-you): no code at all. Pixels are platform-managed.
  • Pages you code with the Headless SDK: declare them as a coded funnel and call tagada.track.step() on each one. The SDK loads the pixels you bind on the canvas and fires them; you never add a pixel script yourself.

​
Supported Pixels

One Google row, three products. The “Google” pixel slot accepts any of three ID formats — TagadaPay auto-detects which Google product to load based on the prefix:
  • GTM-XXXXXX → Google Tag Manager. TagadaPay loads gtm.js and pushes events to dataLayer. Configure GA4 / Ads conversion tags inside your GTM container.
  • G-XXXXXX → Google Analytics 4. TagadaPay loads gtag.js directly and fires events via gtag('event', 'purchase', { value, currency, items }).
  • AW-XXXXXX → Google Ads. Same gtag.js loader; conversion send_to is handled per-event when configured in the dashboard.
No separate “GA4” or “Google Ads” provider exists — they all live behind the same gtm config slot in the SDK. If you have both a GTM container and a direct GA4 measurement ID, add them as two separate Google entries.

​
Configure Pixels

In the TagadaPay dashboard:
Select the platform, paste your pixel ID, and save. TagadaPay handles the rest — script injection, event mapping, and deduplication.

​
Event Mapping

TagadaPay fires these standard e-commerce events and maps them to each pixel’s native event format: A coded funnel can also send Lead (track.event('lead')) and any custom event you declare. It loads Meta, TikTok, Snapchat, Google Tag Manager and Microsoft Clarity — not Pinterest. All purchase events are deduplicated — they won’t fire twice for the same order, even if the customer refreshes the thank-you page.

​
Funnel Step Tracking

TagadaPay also tracks funnel step progression for conversion reporting in the CRM dashboard. This happens automatically when using TagadaPay-hosted funnels or the checkout session flow.

​
Pixels on Pages You Code

For a headless store, let the SDK fire the pixels:
Checkout and purchase events fire on their own, with the same event id as the server-side events TagadaPay sends, so Meta and TikTok count each conversion once. The whole setup — the manifest, the push, binding pixels on the canvas — is on Coded Funnels.
Do not also add the same pixel to your page by hand: every event would count twice. SDK health reports it as Pixel fired twice. If your site sends a Content-Security-Policy, allow the pixel origins.
The CheckoutSession returned by loadSession() does not contain pixel config — pixel IDs are a store-level setting, not a session-level one.