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.

​

Tracking & Attribution Overview

TagadaPay ships first-class integrations for the most popular ad attribution platforms. You don’t need to install pixels on your checkout or thank-you page — once an integration is enabled in the dashboard, TagadaPay handles the wiring server-side on every paid order. This page explains what each tool actually does, where they differ, and which one to pick.

---

​

The Three Categories

​

1. Postback Ad Trackers (S2S, click-id-based)

A merchant-owned tracking service that issues a unique click_id when a visitor clicks an ad, sets it as a first-party cookie or URL parameter on the lander, and expects an HTTP request from your backend whenever a conversion happens. The five we support, all firing automatically on order.paid: How it works under the hood:

1. Visitor clicks an ad → tracker assigns a click_id, drops it on the lander URL and as a first-party cookie.
2. TagadaPay’s mapper script captures URL params + cookies into the customer record at checkout creation.
3. When the order is paid, TagadaPay’s server fires a single HTTP GET to the tracker’s documented postback URL with the click_id, payout, currency, and order id.
4. Tracker matches the click_id back to the original click and credits the ad source.

When to pick a postback tracker: you already use one of these for cross-network ad-spend optimisation or you cloak/rotate offers across many traffic sources. Ignore them entirely if you only run Meta + Google Ads — those have their own native pixels.

---

​

2. PII-Based Attribution (Hyros)

A different beast. Hyros doesn’t use click_ids or cookies — it identifies customers by email and phone, then matches conversions back to the original ad click on its own side. This survives iOS Smart Tracking Protection, adblockers, and cross-device flows that break every click-id tracker on the planet. How it works:

• TagadaPay POSTs every paid order to https://api.hyros.com/v1/orders with email, phone, line items, and amount.
• Hyros stitches it back to the original click via deterministic identity matching.
• No cookie or URL parameter required on the lander.

When to pick Hyros: you’re running serious ad spend ($10k+/month) on cookieless platforms (TikTok, YouTube), you have a high-LTV product where cross-device matters, or your audience skews heavily mobile / iOS.

---

​

3. Shopify Pixel Injection (Wetracked)

Wetracked is a client-side e-commerce attribution pixel that runs only on Shopify storefronts. TagadaPay injects two <script> tags into your Shopify theme during the next theme sync; Wetracked auto-attributes via cookies it sets on first visit — no API key, no pixel ID. When to pick Wetracked: you have a Shopify store and want a no-config attribution pixel layered on top of TagadaPay’s own analytics.

---

​

Decision Matrix

---

​

What TagadaPay Captures Automatically

Every checkout session captures the visitor’s URL params and cookies into the customer’s metadata field. The captured set includes ad-tracker click ids for every supported provider: URL parameters — gclid, fbclid, msclkid, ttclid, twclid, li_fat_id, epik, dclid, yclid, irclickid, cf_click_id, rtkclickid, cid (Voluum), clickid, click_id, cmid, awc (Awin) Cookies — _gclid, _fbc, _ttclid, cf_click_id, _voluum, _binom, rtkclickid-store, _rtkclickid, _mck (ClickMagick), and the platform’s standard click cookies. This means the click_id capture works the same way regardless of which tracker you’ve enabled — flip the integration on, hand the merchant the correct tracking domain, and conversions start flowing within minutes of the next paid order.

---

​

Common Setup Pattern

Every postback tracker integration follows the same three-step pattern:

---

​

What’s Different vs Doing It Yourself

If you’ve ever installed a postback by hand on a Shopify thank-you page or a custom checkout, you know the pain: pixel order matters, cookies vanish on Safari, click_ids get truncated, refunds aren’t synced, and one cleared cache breaks the whole funnel. TagadaPay’s integrations side-step every one of those:

• Server-side firing — the postback comes from our backend, not the customer’s browser. Adblockers, Safari ITP, and cleared caches don’t matter.
• No theme code — for non-Shopify stores you don’t touch the thank-you page at all. For Shopify with Wetracked, we own the inject/remove cycle.
• Idempotent — the postback fires once per paid order. Refresh, refund, dispute — no duplicate conversions.
• Captured on lander, fired on server — the click_id round-trips through TagadaPay’s session, so even if the customer abandons checkout and returns later through a different device, attribution stays intact.

---

​

Next Steps

Pick your tracker and follow its dedicated setup guide: