Documentation Index
Fetch the complete documentation index at: https://docs.tagada.io/llms.txt
Use this file to discover all available pages before exploring further.
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
- You configure pixel IDs in the TagadaPay dashboard (Settings → Integrations)
- TagadaPay injects the pixel scripts into checkout sessions automatically
- E-commerce events (PageView, AddToCart, Purchase, etc.) fire to all active pixels at the right moments
Supported Pixels
| Platform | Config Key | What fires |
|---|---|---|
| Meta (Facebook) | Meta Pixel ID | PageView, ViewContent, AddToCart, InitiateCheckout, Purchase |
| TikTok | TikTok Pixel ID | page, ViewContent, AddToCart, InitiateCheckout, Purchase |
| Google (GTM / GA4 / Google Ads) | Container ID — GTM-XXXXXX, G-XXXXXX, or AW-XXXXXX | All events pushed to dataLayer (GTM) or via gtag('event', …) (GA4 / Google Ads) |
| Snapchat | Snap Pixel ID | PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, PURCHASE |
| Pinterest Tag ID | pagevisit, viewcategory, addtocart, checkout, purchase |
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 loadsgtm.jsand pushes events todataLayer. Configure GA4 / Ads conversion tags inside your GTM container.G-XXXXXX→ Google Analytics 4. TagadaPay loadsgtag.jsdirectly and fires events viagtag('event', 'purchase', { value, currency, items }).AW-XXXXXX→ Google Ads. Samegtag.jsloader; conversionsend_tois handled per-event when configured in the dashboard.
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:Event Mapping
TagadaPay fires these standard e-commerce events and maps them to each pixel’s native event format:| Event | When it fires | Meta (fbq) | TikTok (ttq) | GTM dataLayer | GA4 (gtag) |
|---|---|---|---|---|---|
| PageView | Page load | PageView | page() | PageView | page_view |
| ViewContent | Product viewed | ViewContent | ViewContent | ViewContent | view_item |
| AddToCart | Item added to cart | AddToCart | AddToCart | AddToCart | add_to_cart |
| InitiateCheckout | Checkout started | InitiateCheckout | InitiateCheckout | InitiateCheckout | begin_checkout |
| AddPaymentInfo | Card info entered | AddPaymentInfo | AddPaymentInfo | AddPaymentInfo | add_payment_info |
| Purchase | Payment succeeded | Purchase | Purchase | Purchase | purchase |
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. TheCheckoutSession 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.
