A cleaner record of every booking.
Activate’s bookings start on its website and finish in ROLLER checkout. Tracking had grown across native integrations, custom scripts and Google Tag Manager, so one booking could be recorded twice and credited to Activate’s own site. We gave tracking one home and repaired the hand-off to checkout.
GTM preview · booking BK-58214playactivate.com → ROLLER checkout
- page_view · Mega GridFrom a Meta ad · Spring Weekend
- begin_checkout · ROLLERMega Grid · 4 players · Sat 15:00
- purchase · $96.00Sent once · source: Meta, Spring WeekendTags fired
One booking became two purchases, credited to Activate’s own site.
Bookings started on Activate’s website and finished in ROLLER. Tags in three places could record one purchase twice and credit Activate’s own site instead of the channel that sent the visitor, while a Reddit tag sent missing or zero revenue.
What happened
What the reports recorded
One booking event, one home for tags, one purchase sent to each platform.
Booking tags now live in Google Tag Manager, and a repaired bridge passes each ROLLER purchase to analytics and ad platforms once.
Activate Games’ environment
Website + checkout
Booking event bridge
- Checks message origin
- One listener, no repeats
- Clears stale cart data
Google Tag Manager
- PurchaseOnce per booking
- ValueMapped to live data
- ProductsOne shared structure
One purchase per booking
GA4Purchase, value and channel
MetaMoved to a template
TikTokShared product data
RedditPurchase value mapped
How Activate’s booking data changed, step by step.
Four fixes, from giving tracking one home to sending the right purchase details to each platform.
- 01
Give tracking one home
We consolidated tracking in Google Tag Manager, removed overlapping native integrations, paused legacy tags and handed Activate a documented configuration.
BeforeTags spread across native integrations, custom scripts and GTM
AfterOne documented place to manage how booking events reach each platform
- 02
Repair the hand-off to ROLLER
The event bridge now checks where messages come from, prevents duplicate listeners and clears old ecommerce data before the next event.
BeforeThe same purchase could be sent more than once, or carry stale values
AfterDuplicate tracking resolved
- 03
Credit the channel, not the site
At the February 26 handoff we confirmed the self-referral issue was resolved, and the team reviewed the effects in Google Analytics and Facebook.
BeforeBookings credited to Activate’s own website
AfterSelf-referrals resolved, checked in GA and Facebook
- 04
Align purchase details
We moved Meta from legacy custom code to a template, corrected Reddit’s purchase-value mapping and aligned TikTok’s product data with the shared ecommerce structure.
BeforeReddit purchases with missing or zero revenue
AfterPurchase values and product data mapped correctly
One booking in ROLLER. One purchase event sent to each platform.
An example check of the purchase events each platform received against bookings in ROLLER. Consent choices and ad blockers leave small gaps, and ad platforms report only the purchases they’re credited with.
Purchase events received
GA4 purchases by channel
Bookings don’t add up across your platforms? We’ll trace one booking from ad to checkout and show you where the count splits.
Book a walkthroughTake your bookings from double-counted to one clean record.
Start with a free scan of your booking flow, or have us trace and fix it from ad to checkout.