Canada Analytics

iGaming Conversion Tracking in Ontario & Alberta: FTDs, Affiliates and Ad Compliance

In short: Canada now has two regulated, privately operated online gambling markets. Ontario opened in April 2022 under iGaming Ontario and the AGCO. Alberta’s market went live on July 13, 2026, run by the AGLC and Alberta iGaming Corp. In both, the conversion that matters is a verified first-time deposit (FTD). That deposit happens after identity (KYC) and geolocation checks inside the operator platform, so a browser pixel on the sign-up page can’t see it. The reliable pattern is: capture the click IDs at sign-up, fire the FTD from the platform to server-side GTM, deduplicate it against affiliate postbacks, and send it to Google Ads and Meta without bonus or gambling-behaviour data.

This guide covers measurement, not legal advice. Advertising rules change; confirm every campaign with your compliance team and the current AGCO and AGLC standards.


What the advertising rules mean for tracking

These rules change what you are allowed to collect, target and send:

  • Google Ads: Google accepts gambling ads in Ontario only from provincially licensed operators that hold a Google gambling certification. Ads must target only the approved province and link to a landing page with responsible-gambling information (iGaming Business; Google Ads policy update). Google updated the policy for Alberta operators ahead of that market’s launch (Yogonet).
  • Bonuses: both provinces restrict public advertising of bonuses and free bets. Offers belong on the operator’s own site or in opt-in marketing (Covers).
  • Audiences: no targeting of minors, and no marketing to self-excluded players during their exclusion period. Operators are also accountable for what their advertising partners do (Gowling WLG).

For tracking, that translates into three rules of thumb:

  1. Keep offer data out of ad-platform events. Don’t send bonus_code or promo_name parameters to Google or Meta.
  2. Every remarketing or customer-match list needs a suppression step for self-excluded players and accounts under the legal age (19 in Ontario, 18 in Alberta).
  3. Scope campaigns and conversion actions by province, so Ontario and Alberta data and budgets stay separate.

The event model operators actually need

StageWhere it happensHow to track itSend to ad platforms?
Landing & sign-up startYour siteWeb GTM, Consent Mode v2GA4 only
Registration completedPlatformPlatform webhook → sGTMYes, as a secondary conversion
KYC / age & identity verifiedPlatform / KYC vendorWebhook → sGTMOptional, as a quality signal
First-time depositCashier (often another domain)Platform event → sGTM, with value in CADYes, as the primary conversion
Retained player (e.g. day 30)Data warehouseBigQuery → offline importYes, if your compliance team approves

The primary conversion should be the FTD, with a value your finance team agrees on: the deposit amount, a predicted lifetime value, or a fixed value per province. Registrations are cheap to generate and a poor bidding target.

Capturing click IDs before the user leaves your site

  1. On the landing page, store gclid, gbraid, wbraid, fbclid/_fbc, _fbp and the affiliate ID in first-party cookies, set server-side from your own subdomain.
  2. Pass them into the registration call so the platform saves them on the player record.
  3. When the platform confirms the FTD, it calls your server-side GTM endpoint with the player ID, the stored IDs, the CAD value and the province.
  4. sGTM sends the event to GA4 (Measurement Protocol), to Google Ads (offline conversion or enhanced conversions with hashed email) and to Meta CAPI. It uses one event_id, so the event is deduplicated against any browser event.

Hash email and phone with SHA-256 before they leave your server. Send nothing about bet types, game categories or losses. The ad platforms don’t need it, and it is the kind of data regulators and platforms treat as sensitive.

Deduplicating affiliates and paid media

Affiliate networks (for example Income Access or MyAffiliates setups) receive their own FTD postbacks. If Google Ads, Meta and an affiliate all report the same deposit, your cost per depositor is wrong. The fix:

  • One player ID, one FTD record, one owning channel, decided by a written rule. The usual rule is last paid click within your window, with affiliates winning when their ID is present.
  • Reconcile in BigQuery by joining FTDs to click IDs and affiliate IDs, then report cost per depositor by province and channel once.
  • Send conversions to ad platforms only for players the rule assigns to that platform, or label the rest as secondary, so Smart Bidding doesn’t learn from affiliate-driven players.

Ontario operators expanding into Alberta

Build Alberta as a separate setup, not a copy of the Ontario one. That means:

  • a separate Google certification and separate conversion actions
  • a province value on every event
  • separate audiences with their own suppression lists
  • a clean landing-page set with the responsible-gambling information Alberta requires

That keeps reporting, budgets and compliance reviews clean from day one.

Where to go next

Direct Implementation White-Label for Agencies

Need this implemented, audited, or white-labeled?

Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.

✓ 24–48h Emergency SLA ✓ Strict Non-Solicitation & NDA ✓ 8.5+ Event Match Quality
Jobair Mahmud

Jobair Mahmud

AI-Driven Performance Marketing & Web Analytics Consultant

Helping eCommerce brands and marketing agencies trust their ads data, scale Smart Bidding, and eliminate wasted ad spend through bulletproof server-side tracking and PPC management.