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 injects the pixel scripts into checkout sessions automatically
  3. E-commerce events (PageView, AddToCart, Purchase, etc.) fire to all active pixels at the right moments
No SDK code required for standard checkout flows. Pixels are platform-managed.

​
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: 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.

​
Custom Pixel Configuration (Advanced)

If you’re building a fully headless store and need to fire pixel events yourself, configure your pixel IDs in the TagadaPay dashboard (Settings → Integrations) or via the Node SDK’s store settings. The CheckoutSession returned by loadSession() does not contain pixel config — pixel IDs are a store-level setting, not a session-level one.
For headless stores, you manage pixel script injection yourself using the pixel IDs from the TagadaPay dashboard or your store’s settings via the Node SDK. TagadaPay provides the configuration — you control when and how scripts load.