Tracking & Attribution

Tracking & Attribution Setup | Make Every Conversion Count

Without accurate data, every optimization is a guess. We build and verify the entire Pixel, CAPI, GA4, UTM chain — every conversion event correctly tracked, correctly attributed, correctly sent back, with test records attached at every step. Server-side delivery in high-blocking iGaming environments is our daily work, not an add-on.

Book a consultation
01 / Tracking Stack

The Tracking Stack

Pixel

Meta Pixel

Browser-side event infrastructure: standard + custom events, advanced matching parameters, page-by-page firing tests. Not just pasting a code snippet — we verify, one by one, exactly which parameters every event sends.

CAPI

Conversion API

Server-side delivery: dual-send with the same event_id as the Pixel, automatic dedup on Meta's side — bypassing blocks and interceptors to recover from the server the signals the browser loses. Acceptance is measured against events_received, not "it's installed, we're done".

GA4

GA4 Integration

Property + Data Streams setup, event and conversion mapping, event-by-event DebugView verification. Ad platform dashboards always skew optimistic — GA4 is your cross-channel control group.

UTM

UTM Standards

A unified naming template + fixed vocabulary + link builder — no hand-typed links, ever. Cross-channel attribution can only be consistent if naming is consistent first: messy UTMs turn channel reports into garbage in, garbage out.

Events

Event Tracking Design

A custom event map covering the full funnel: impression → click → sign-up → deposit. Every event defines its trigger conditions, parameters and dedup key, with front end and back end aligned on the same sheet.

sGTM

Server-Side Tracking

sGTM container deployment, first-party domain data collection, signal completeness maximized. However hostile the front end gets (ITP, blockers, iOS restrictions), the server side has you covered.

02 / Plans

Three tiers, one-time setup

One-time USDT pricing | Every tracking asset — Pixel / GA4 / sGTM — registered under your name

BASIC SETUP

Basic Setup

Just starting out — get one platform's core events tracked correctly and establish a clean measurement baseline

Fee$150–250 USDT
  • Single-platform Pixel install (Meta or Google)
  • 5 core events configured
  • UTM naming standards document
  • Per-event firing test records
Talk to us
Most Popular PRO SETUP

Dual-Channel Setup

Ads already running — recover the signals lost since iOS and feed the algorithm real data

Fee$400–600 USDT
  • Pixel + CAPI dual channel (same-event_id dedup)
  • 10+ custom events covering the full funnel
  • GA4 integration (Property + event mapping)
  • Tracking monitoring dashboard
Talk to us
ENTERPRISE

Enterprise Attribution

Multi-platform, multi-market — you need a server-side data hub and one unified basis of comparison

Fee$800–1,200 USDT
  • Multi-platform: Meta + Google + TikTok
  • sGTM container deployment (first-party data)
  • Cross-device attribution model
  • Advanced reporting with unified cross-channel metrics
Talk to us
03 / Why It Matters

Why tracking is worth building right, once

Signal Loss

Signal Loss

Since iOS 14.5+, 30–40% of browser-side events simply vanish — you are still converting, the platform just can't see it. CAPI backfills from the server side so the algorithm gets its full sample back.

Attribution

Accurate Attribution

Which channel deserves more budget is decided by attribution, not gut feeling. Only when UTM conventions, click IDs and the event map are aligned do you get cross-channel numbers you can actually compare.

Bidding

Bid Optimization

The algorithm bids with the signals you send back: the higher the signal quality (EMQ), the better events match back to real users — sharper learning, lower CPA. Our on-site intent events hold a field-tested EMQ of 6–7.

Compliance

Compliance

GDPR / CCPA is not optional. Consent mode plus a server-side architecture lets you collect data with consent in place — compliance and data completeness can coexist.

Free Tracking Audit

Send us a URL and we'll lay your current tracking gaps out in the open — which events aren't firing, which are double-counted, and what your signal quality scores.

  • ✓Pixel firing check (every page, every event)
  • ✓CAPI event comparison (browser vs server)
  • ✓GA4 data stream verification
  • ✓Signal quality score (EMQ)
Request a free audit

Deliverables

  • ▸Pixel + CAPI install with same-event_id dual-send dedup
  • ▸GA4 Property + Data Streams + conversion event mapping
  • ▸Full event map document (events × parameters × trigger conditions)
  • ▸UTM naming template + link builder
  • ▸Tracking monitoring dashboard (Pro and above)
  • ▸Verification records: Test Events / measured events_received / EMQ scores
04 / Timeline

5 working days, deliverables every day

Day 1
Current-State Audit

Full inventory of your existing Pixel / GA4 / UTM: which events fire, which double-count, which are missing entirely

Day 2–3
Setup & Deployment

Pixel + CAPI + GA4 build-out, event map implemented, UTM template and link builder delivered

Day 4
Verification & Testing

Live Test Events runs, event_id dedup comparison, event-by-event DebugView verification, EMQ check

Day 5
Handover & Docs

Event map, verification records, dashboard handover — every asset registered under your name; when we leave, you keep it all

05 / Further Reading

Field notes from real projects

Tracking

Track first, scale later: Pixel + CAPI dual-send dedup in practice

The full implementation log behind this page's methodology — same-event_id dual-send, matching-key normalization, the road to a field-tested EMQ of 6–7 and the traps along the way.

Read the article →

 Automation

Check-ins, payouts and raffles on full auto: a membership LINE bot

When deals close off-site, membership data has to feed back into the ad loop — the system design behind member binding and automation.

Read the article →
06 / FAQ

Tracking setup and attribution

What is server-side tracking?
Browser-side tracking relies on the user's browser to fire events, and gets eaten by ITP, ad blockers and iOS privacy restrictions. Server-side tracking sends events from your server (or an sGTM container) straight to the platform APIs — first-party data, unaffected by front-end conditions. In practice you run both tracks in parallel: the server side typically recovers 20–35% of the signals lost in the browser.
How does EMQ (Event Match Quality) affect ad performance?
EMQ is Meta's score (out of 10) for how complete each event's matching keys are. The higher the score, the better events match back to real users — sharper algorithm learning, more efficient bidding. Our approach: matching keys like email and phone are always normalized and SHA256-hashed server-side, with bad emails, short numbers and empty values automatically dropped — no stuffing junk signals to inflate the score. Our on-site intent events hold a field-tested EMQ of 6–7.
What's the difference between GA4 and the Meta Pixel? Do I need both?
Different roles: the Pixel serves Meta's algorithmic bidding and audience building, while GA4 is your cross-channel analytics hub (sessions, funnels, retention). Ad platforms always report their own performance optimistically — GA4 is your control group. Install both, and align event naming on the same event map, or the numbers will never reconcile.
How do you track iGaming / crypto sites? Platforms often block these events.
High-risk verticals depend even more on the server side: pixels are often blocked by browsers or restricted by platforms, while CAPI runs server-to-server and is unaffected. We also build your own first-party counting endpoint (independent of any ad platform) as an undeniable ledger of record. When deals close off-site (third-party order or deposit systems), we backfill with offline events — a route we have run and verified in production, not a paper plan. Details over TG.
How do I keep my UTM strategy from turning into a mess?
Three things: one naming template (source / medium / campaign / content all lowercase, a fixed vocabulary, no spaces), one link builder (no hand-typed links, ever), and one alignment pass (every team on the same sheet). UTM is the foundation of attribution — inconsistent naming writes off your GA4 channel reports entirely. Delivery includes the standards document and the builder.
How do you handle cross-device attribution?
Seeing the ad on a phone and ordering on a desktop is the norm. The fix: pass hashed matching keys (email / phone) into events so platforms can resolve them back to the same person; enable User-ID and Google signals in GA4; on the Enterprise plan, add sGTM first-party cookie lifetime extension on top. Cross-device can never be reconstructed 100%, but you can compress the broken links to a level you can make decisions on — the point is knowing exactly what you're undercounting.
What is the Conversion API (CAPI)?
Meta's server-side event interface: your server sends conversion events to Meta directly, without going through the browser. Done right, it dual-sends with the same event_id as the Pixel and Meta dedups automatically — the server fills in whatever the browser gets blocked on, without double-counting. Our dual-send implementation is accepted against measured events_received, and verification records ship with every install.
How do you audit my existing tracking setup?
Through the free audit flow: Pixel firing check (every page, every event — what parameters actually go out) → CAPI event comparison (browser vs server counts and dedup status) → GA4 data stream verification (live DebugView) → signal quality scoring (EMQ). You get an issue list plus a fix priority order. Drop a URL on TG to get scheduled — the audit is free.
What do I do when an iOS update breaks my tracking?
First separate "actually broken" from "just invisible": iOS restricts browser-side signals, not your sales. Short term, claw the numbers back with CAPI backfill plus offline event uploads; long term, move the architecture to server-side and first-party data — then every iOS release becomes routine maintenance, not a disaster. This is exactly why Pro and above default to dual channel.
How do I choose a multi-channel attribution model?
Get the data right before debating models: without solid UTM standards and event alignment, even the fanciest model runs on wrong inputs. GA4's default data-driven attribution (DDA) is enough for most volumes; the Enterprise plan pulls Meta / Google / TikTok into one cross-channel report and compares CPA on one consistent basis — models can change, the measurement basis must not.
Free Tools

Price it first, then talk

Drag the sliders on the cost calculator to see what it costs; when you're ready, send us your requirements.

Book a consultation
Free scoping and quotes · No lock-in contracts · An engineer answers you in person
Chat on TG