Home  /  Case studies  /  US Beauty Spa Franchise

Beauty & Wellness

Every lead from 33 landing pages now lands in the right report.

US Beauty Spa Franchise · United States · 12 locations

A 12-location US beauty spa franchise was running Meta and Google ads for every spa, sending traffic to 33 GoHighLevel landing pages. Nobody could say with confidence which page, which location or which ad produced a lead. We built one tracking system across every page, connected it to GA4, Meta, Google Ads and Microsoft Clarity, sent booked appointments back to Meta, and handed over a written playbook so the team can launch the next location without us.

US Beauty Spa Franchise
33/33

Landing pages verified end to end: form, GA4, consent and Clarity

23/23

Server-side lead routes with confirmed Meta receipts

12

Spa locations running on one Tag Manager container

3

Written guides: tracking SOP, new-location runbook, troubleshooting

The challenge

Thirty-three pages, a dozen spas, and no single version of the truth.

  • The page list did not match reality. The master tracker held 29 pages, while an audit of the live GoHighLevel accounts turned up more live pages that were missing from it.
  • Meta tracking was mixed up. Some Google Ads pages loaded two different Meta pixels, one page had no identifiable pixel at all, and Meta and Google traffic were not cleanly separated.
  • One location could not report to Meta at all. Its dataset had been restricted by Meta because of a category selected in error, so its server events were not being processed.
  • GA4 caps an account at 30 key events. With 33 pages, giving every page its own conversion was not an option, yet the team still needed per-page and per-location reporting.
  • Ads were learning from form fills, not bookings. Confirmed appointments lived in the spa booking system, so Meta never saw which leads actually turned into customers.
  • There was no way to watch real visitors. Without heatmaps or recordings, broken form behaviour could sit unnoticed on live pages.

The solution

One container, one naming system, every platform verified.

Audit and Page Register

Reconciled the client page list against every live GoHighLevel account, then built an approved 33-page register with a unique page code for each location, offer and traffic source.

One Tag Manager Container

A single Google Tag Manager container on every page. One shared GA4 lead event carries location, offer, placement and page code, plus a unique event per page, so reporting works per page and rolls up per location inside the 30-event limit.

Meta Pixel and Conversions API

Browser and server lead events per location dataset, paired with one event ID so Meta counts each lead once. Server events respect the visitor cookie choice. Meta Pixel kept off the Google Ads pages. The restricted dataset resolved with Meta Support.

Google Ads Lead Conversion

A Google Ads lead action built from GA4 for the paid search pages only, imported as a secondary conversion so the client gets lead reporting without any change to live bidding.

Microsoft Clarity and Page Fixes

Heatmaps and session recordings on every campaign page with cookies off and form fields masked. The recordings surfaced a form error, which was fixed and published across all affected pages, along with broken button, link and thank-you corrections.

Bookings Back to Meta

Confirmed appointments from the booking system reach GoHighLevel and are sent to Meta as Schedule events, so ads can learn from real bookings. Verified end to end with a controlled test booking.

How it is wired

From ad click to booked call.

Every accepted lead

  1. Cookie choice
  2. Accepted form and thank-you page
  3. GA4 shared lead plus page event
  4. Meta browser and server, one event ID
  5. Google Ads paid search action

Every booked appointment

  1. Spa booking system
  2. GoHighLevel booked appointment
  3. Meta Schedule event
  4. Ads learn from real bookings

Every new location

  1. Approved inputs
  2. 6 pages and 8 forms from the template
  3. Extend the tag map
  4. Full QA checklist
  5. Release with rollback point

Services used

Google Tag Manager & GA4Meta Pixel & Conversions APIGoogle Ads ConversionsMicrosoft ClarityGoHighLevel WorkflowsTechnical Documentation

Timeline: About six weeks from first platform access to full handover, then a controlled booking test to release appointment reporting

Featured work

The system, documented.

Client name, locations and account details are withheld under NDA. These are anonymised views of the actual register, lead path, naming system and handover pack delivered on the project.

Anonymised 33-page tracking verification register

The 33-page verification register

Every approved page checked for Tag Manager, form journey, GA4, consent, Clarity, Meta server reporting and Google Ads, location by location.

Accepted lead path from consent to booked appointment

The accepted lead path

Six steps from the visitor cookie choice to a booked appointment reaching Meta, with consent respected at every stage.

Event naming system for 33 landing pages

Event naming that fits inside GA4 limits

One shared lead event carrying the full page identity, plus a unique event per page, instead of 33 competing key events.

Handover pack contents

The handover pack

A 14-page technical guide, an editable 33-row register and a reusable template for every future location.

FAQ

Questions about this build

How do you track 33 landing pages when GA4 only allows 30 key events?

Instead of one key event per page, every page sends one shared lead event that carries its location, offer, traffic source and page code, plus its own page-level event. Reports still break down per page and per location, and there is room left for every new location the business opens.

Why keep the Meta Pixel off the Google Ads landing pages?

Meta and Google campaigns were run as separate channels with separate landing pages. Keeping the Meta browser Pixel off the paid search pages stops Meta from claiming credit for Google traffic. Those pages still report leads to Meta from the server through the correct location dataset, and to Google Ads through their own conversion action.

How do booked appointments get back to Meta?

Confirmed bookings already synced from the spa booking system into GoHighLevel. A workflow sends each confirmed appointment to the correct Meta dataset as a Schedule event with its own booking-level ID, so it never collides with the original lead event. It was released only after a controlled test booking was traced through GoHighLevel and Meta.

What else was handled during the project?

Alongside the tracking, routine GoHighLevel work across the franchise: promotional workflows with their emails and SMS copied and checked across a dozen sub-accounts, forms and automations rolled out to new locations, and oversized animated email banners compressed from 26 MB to under 14 MB so they upload without losing the animation.

Free consultation

Want something
like this?

Tell me what you are trying to automate and I will tell you exactly how I would build it, and what it would cost. If I am not the right person for the job I will say so.

Meetings available in US hours. I work IST, so progress happens overnight for you.