Integrations
Connect Trcker to Shopify, QuickBooks, ChatGPT Ads, and Google Ads, and learn how Trcker automatically preserves ad-platform click IDs so your own pixels can match conversions.
How Integrations Work
Trcker connects your affiliate program to the systems that drive conversions in, payouts out, and ad spend in:
- Shopify brings paid orders INTO Trcker as attributed conversions.
- QuickBooks pushes affiliate payouts OUT of Trcker into your accounting ledger.
- Ad Spend pulls read-only ad spend INTO Trcker to compute CPA and ROAS.
All are configured per-brand under Integrations in your sidebar.
Separately, Trcker automatically preserves ad-platform click IDs on every redirect so your existing ad pixels and Conversions APIs can match affiliate-driven sales. That requires no connection or setup. See Ad-Platform Click IDs below.
---
Ecommerce
Shopify
What it does: Turns paid Shopify orders into attributed affiliate conversions. Trcker registers an orders/paid webhook on your store. Each paid order that carries a Trcker click ID becomes a conversion automatically, with the order amount and transaction ID attached.
Setup:
1. Go to Integrations > Ecommerce > Shopify
2. Click Connect and authorize via your Shopify admin (read-only access to orders)
3. Trcker registers the orders/paid webhook for you
What you'll need: A Shopify store where you can install an app. Your affiliate tracking links must pass the Trcker click ID through to checkout so the resulting order can be attributed.
How it works: When Shopify reports a paid order, Trcker matches it to the originating click by click ID, then records a conversion with the order total, currency, and order ID. Orders without a Trcker click ID are ignored.
---
Accounting
QuickBooks
What it does: Syncs paid affiliate payouts into QuickBooks Online as expenses, so your finance team does not have to reconcile them by hand.
Setup: 1. Go to Integrations > Accounting > QuickBooks 2. Click Connect and authorize via QuickBooks 3. Trcker creates one expense per partner payout batch when you mark a payout Paid
What you'll need: A QuickBooks Online account you can authorize.
How it works: When a payout is marked Paid in Trcker, it is pushed to QuickBooks as an expense, with the partner name as the vendor and the payout period as the memo. Re-running a sync is idempotent, so the same payout will not be double-booked.
---
Ad Spend
OpenAI ChatGPT Ads
What it does: Pulls your real ad spend per campaign and joins it to your conversions, so you see CPA (cost per acquisition) and ROAS (return on ad spend) next to the revenue your paid traffic drives.
Setup: 1. Go to Integrations > Ad Spend 2. Paste your OpenAI Advertiser API key (Ads Manager → Settings → General → "Create New API Key") and click Connect 3. After the first sync, map each discovered campaign to a Trcker offer
What you'll need: Your OpenAI Advertiser API key — distinct from the Conversions API key. It's stored encrypted at rest, used only to read spend, and never logged.
How it works: A daily sync (and an on-demand Sync now button) pulls a trailing window of spend. Spend from campaigns you map to an offer drives per-offer Spend/CPA/ROAS columns on the Offers table; all pulled spend drives a brand-level Spend/CPA/ROAS tile on the Overview. CPA/ROAS divide spend by ad-sourced conversions only — never your organic conversions. Full details in Ad Spend (CPA & ROAS).
---
Google Ads
What it does: Pulls your real Google Ads spend per campaign, daily, and joins it to the conversions Trcker attributed to ad-sourced clicks — giving you CPA and ROAS in the same Overview tile and Offers columns as the ChatGPT Ads connector.
Setup: 1. Go to Integrations > Advertising > Google Ads 2. Click Connect and authorize with your Google account (read-only spend access — Trcker cannot change your campaigns) 3. After the first sync, map each discovered campaign to a Trcker offer
What you'll need: A Google account with access to the Google Ads account you want to connect. Authorization is via OAuth — no API keys to copy.
How it works: A daily sync pulls a trailing window of campaign spend and upserts it into Trcker. Spend is attributed to conversions whose originating click carried a Google click ID (gclid, gbraid, or wbraid) — Trcker captures and preserves these automatically on every redirect. Mapped campaigns drive per-offer CPA/ROAS; all pulled spend contributes to the brand-level blended tile. Full details in Ad Spend (CPA & ROAS).
---
Ad-Platform Click IDs
Trcker does not fire conversions to your ad platforms on your behalf. Instead, it does something simpler and more durable: it preserves the click IDs your ad platforms rely on so that your own pixels and Conversions APIs can match affiliate-driven sales. There is nothing to connect and nothing to configure. (Trcker can pull read-only ad spend to compute CPA/ROAS — see Ad Spend above — but that's a separate, opt-in connection.)
What it does:
- On every click through a Trcker link, Trcker captures any ad-platform click ID present in the URL.
- On the outbound redirect to the advertiser, Trcker writes those click IDs back onto the destination URL, so the landing page and the advertiser's own pixel or Conversions API can read them.
- This includes recovering click IDs that Safari and iOS strip in Private Browsing and inside Apple apps (roughly a quarter of global traffic). Publishers include both the canonical click-ID parameter and a tck_-prefixed mirror in their Trcker links; Apple only strips the names it recognizes, so the mirror survives, and Trcker restores the canonical name on the way out.
Platforms whose click IDs are captured and mirrored:
| Platform | Parameter |
|---|---|
| Google Ads / DV360 | gclid, gbraid, wbraid |
| Meta (Facebook, Instagram, WhatsApp) | fbclid |
| Microsoft Advertising (Bing) | msclkid |
| TikTok Ads | ttclid |
| Reddit Ads | rdt_cid |
| LinkedIn Ads | li_fat_id |
| X (Twitter) Ads | twclid |
| Pinterest Ads | epik |
| Snapchat Ads | snap_click_id |
| Outbrain | outbrain_clickid |
| Taboola | taboola_clickid |
How it works: Captured click IDs are stored on the click record. On redirect, Trcker sets both the canonical parameter (for example gclid) and its tck_ mirror on the outbound URL when not already present, so whichever name the ad platform expects is always there. Because the advertiser's existing pixel or CAPI does the matching, you keep using the conversion setup you already have inside each ad platform.
---