Contact person: Business Client

Phone:Show

Email:Show

Location: Brampton, Canada

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I have already wired together Google Tag Manager, Acuity Scheduling, and GA4, but the tracking logic still needs to be made rock-solid and production-ready. My initial plan was to capture every successful booking inside the embedded Acuity iframe, fire a GA4 event that contains the city name, and then surface thirty separate conversion actions (one per city) inside Google Ads. Time and patience ran out, so I need you to finish the job exactly where I left off.

Here’s the flow I want, end to end:

• Detect every booking completion. First choice is a secure postMessage from the Acuity iframe to the parent page. If postMessage proves impossible, fall back to a MutationObserver in GTM or a small server-side webhook that listens to Acuity’s native notifications and forwards the outcome via the Measurement Protocol.
• Push a GA4 event on each confirmed booking and include a city parameter pulled from the page path, a URL parameter, or a hidden form field.
• Build thirty unique GA4 conversions—one for each city—and import them into Google Ads so campaign bidding can optimize locally.
• Validate with both live and test bookings, keeping detailed logs to confirm that GA4, Google Ads, and the webhook (if used) all reconcile.

Deliverables I expect:
1. Fully functioning GTM container (or server-side endpoint) that handles the detection logic and event push.
2. GA4 property with the thirty conversion actions created and verified.
3. Screen-recorded walkthrough (Loom), a brief verification report, and concise implementation notes so I can maintain the setup later.

Everything is already partially configured; you’ll be completing—not starting—the implementation. Once finished, I should see clean, city-specific conversion data in both GA4 and Google Ads without manual intervention." (client-provided description)