Sean pulled roughly five days of this plan forward into a single session on Thu 24 Apr. Status badges below have been updated. Biggest architectural shift: the YGB redirect approach is off the table — Trackman doesn't expose a post-payment redirect. It's replaced by a Cloudflare Worker at nineteenthgc-capi.sean-5f6.workers.dev that consumes Trackman's Purchase Paid webhook and fires server-side Purchase events to Meta CAPI (verified working) and GA4 Measurement Protocol (code ready, Antonio to deploy). See verification-week1.md in the project folder for the full evidence pack. Three things for Antonio on Monday: bump Sean's GTM account access from Read-only, deploy the updated Worker source, and configure the Trackman webhook URL once their support enables it.
Why this week matters
The audit on 14 April told us something clear and useful: the website itself is in good shape, but almost nothing behind the scenes is being tracked. GA4 isn't running, Google Tag Manager isn't installed, the Meta Pixel isn't verified sitewide, there's no Google Ads conversion tag, and the homepage is missing LocalBusiness schema. On top of that, when someone books through Your Golf Booking the handoff doesn't pass anything back to the main site, so when a booking happens we can't tell where it came from.
That makes next week our foundation week. Turning on paid ads right now would mean flying blind, so the job is to get the tracking working before we spend a single pound on traffic. Once the foundation is in, every ad, post and campaign that follows becomes measurable and tunable.
By Sunday 3 May we want GA4 running, the Meta Pixel verified, a working thank-you page that fires conversion events when a booking completes, LocalBusiness schema live on the homepage, and a tidy Meta Business Manager with Page, Pixel, Ads account, Instagram and billing all linked in one place.
- GA4 Real-Time shows a test session (open the site from a phone and see it register).
- Meta Pixel Helper shows
PageViewon every page and firesLeadon every Book-Now click. - A test booking on YGB returns the user to
nineteenthgc.com/thank-youand fires PixelPurchase, GA4purchase, and a Google Ads conversion. - Google's Rich Results Test returns a valid
LocalBusinessschema from the homepage. /sitemap.xmland/robots.txtreturn 200 and the sitemap is submitted in Search Console.
Every task on the day-by-day plan carries a status tag so progress is clear at a glance.
Day-by-day plan
nineteenthgc.com. Paste the head and body snippet into the Framer project via Site Settings, then publish.GTM-XXXXXX firing on every page.nineteenthgc.com appears verified in the GSC dashboard.fbq() snippet is firing through GTM on every page.PageView on /, /pricing and /gallery.Lead event on every Book-Now click Done 24 Aprfbq('track','Lead') plus a GA4 book_now_click event on the same trigger. This becomes our mid-funnel soft conversion.Lead in Pixel Helper and book_now_click in GA4 DebugView.nineteenthgc.com/thank-you on Framer Copy drafted · Framer build pending/thank-you, mobile responsive, set to noindex so it doesn't rank./thank-you?booking=1 Not available in Trackman?booking_id={value} if YGB exposes a transaction ID so we can deduplicate events later./thank-you?booking=1./thank-you): fbq('track','Purchase') with an event_id, a GA4 purchase event, and a Google Ads Purchase conversion action. Pass a value if YGB exposes one in a URL parameter./robots.txt and /sitemap.xml Done 24 Apr · auto-gen by Framerrobots.txt that points to the sitemap. Submit the sitemap in Search Console.Nineteenth Golf Club | 24/7 Golf Simulator Sydney · Silverwater (under 60 characters). Hero subhead updated to read "Your first 30-minute session free with code Trial25", which removes the duration ambiguity the audit flagged.book.nineteenthgc.com custom-domain request to YGB Nextgtm-verification-w1.pdf saved to the project folder.What gets delivered by Sunday 3 May
| Deliverable | Form | State |
|---|---|---|
| GTM container | Published on nineteenthgc.com, firing on all pages | Live |
| GA4 property | Routed via GTM, Real-Time verified, Search Console linked | Live |
| Meta Pixel | Base code sitewide, Lead event on Book-Now, Purchase event on /thank-you | Live and verified in Pixel Helper |
| Google Ads conversion | Purchase conversion action firing from /thank-you | Live |
| /thank-you page | Branded confirmation page with YGB redirect wired in | Live |
| LocalBusiness schema | JSON-LD block in homepage head, passing the Rich Results test | Live |
| robots.txt and sitemap.xml | Published and submitted to Google Search Console | Live |
| Google Business Profile | Claimed, fully populated, 15+ photos uploaded | Live or pending verification |
| Homepage pricing and testimonials | Three-tier pricing block and three-quote review band deployed | Live |
| Rewritten title tag and hero subhead | Keyword-weighted title, 30-minute trial specified in hero | Live |
| Business Manager asset group | Page, Pixel, Ads, Instagram and billing linked with Antonio and Sean access | Configured |
| UTM taxonomy doc | Shared Google Sheet pinned in Slack | Published |
| CAPI approach decision | Short doc in the project folder, build scheduled for Week 2 | Decided |
| Week-1 verification pack | PDF of screenshots, one per audit checklist row | Sent Sunday evening |
Who's doing what
- Monday: Bump Sean's GTM account access from Read-only to User
- Monday: Deploy updated Worker source with GA4 MP branch (capi-worker/src/index.js) via wrangler or clean paste into CF editor
- Monday: Create GA4 Config tag in GTM using G-MXCKE9M24B, submit + publish the container
- Monday: Google Ads — create or link account, Purchase conversion action, link GA4→Ads
- Monday: Verify Search Console via GTM, connect GA4 for query data, submit sitemap
- Tuesday: GTM click trigger for outbound YGB links + GA4 book_now_click event tag
- Once Trackman replies: configure webhook URL from DEPLOYED.md in Trackman Portal → Admin → Settings → Manage Integrations
- Already done: GTM container created, Pixel set up, BM asset group linked
- Assembles the verification evidence pack (Sean has pre-populated in verification-week1.md)
- Installed Meta Pixel + Lead event on site; verified firing (24 Apr)
- Built + deployed Cloudflare Worker for Trackman → Meta CAPI bridge (24 Apr, verified events_received=1)
- Created GA4 property (G-MXCKE9M24B) and Measurement Protocol API secret
- Installed GTM container GTM-WND2LDFZ on the Framer site; now awaiting Antonio's tags
- Added LocalBusiness JSON-LD, hidden H1, title rewrite, and published UTM taxonomy doc
- Sent Trackman Support ticket for webhook enablement
- Briefs and captures 15+ GBP-ready photos of bays, Trackman, lounge and exterior
- Writes the three homepage testimonial quotes once GBP reviews accumulate
- Confirms with the client on Google Ads account status and GBP verification ownership
- Holds all Meta creative until the end-to-end test passes
Risks and mitigations
- HighYGB's redirect field might not be self-serve. If the booking platform doesn't expose a post-payment redirect, the whole /thank-you strategy stalls. Mitigation: raise a YGB support ticket on Monday rather than Wednesday, so we have two full working days of lead time before the cross-domain task becomes critical.
- HighGoogle Business Profile verification takes time. Postcard verification can take 10 to 14 days, and video verification is faster but not guaranteed. Mitigation: Sean confirms with the client on Monday whether the profile is already claimed. That alone could save a week.
- MediumFramer may not expose a clean robots.txt override. If it doesn't, the fallback is a Framer Pro SEO setting, or a Cloudflare Worker rewrite in the worst case. Mitigation: check the Framer docs during Monday's setup so it doesn't become a Thursday blocker.
- MediumThe client may be hard to reach for admin access. Google Ads account access and GBP ownership both need client input. Mitigation: Sean flags every required admin ask in the Monday catch-up rather than spreading them across the week.
- LowThe CAPI vendor decision might slip. This is a Week-2 build, so a Friday decision is fine. Mitigation: none needed unless the decision slides past the following Monday.
What Week 2 unlocks
Because the CAPI pipeline is already built and Meta-side attribution is verified, Week 2 (4 to 10 May) skips directly to campaign launch. Once Trackman enables the webhook and the three verification bookings clear, Sean kicks off the Meta funnel starting with awareness against the now-live Pixel + CAPI. Antonio stands up the Google Search campaign on branded and high-intent non-brand terms like "golf simulator sydney" and "trackman near me". We also finalise the GA4 + Google Ads link so GA4's server-side Purchase flows automatically into Ads as a conversion.
Week 3 (11 to 17 May) becomes the post-booking email sequence (day 1, day 3, day 7, day 14) and the review-request flow. Every real booking in May turns into a future Google review and a second visit — the point where tracking setup stops being the story and actual results take over.