Skip to main content
PlaygroundCRMs and lead management

Playground conversion tracking that credits ads with enrollments

Families fill out your Playground interest form or book a tour, yet Google and Meta can't say which campaign filled a classroom. Playground has no GA4 setting; it hands your website two browser signals and leaves the rest to you. Fixed means every tour and enrollment traces back to the ad click that started it.

Free30 minutesNo obligation

Playground · what breaks

What goes wrong with Playground tracking

  1. 01

    "Google Ads says we got zero tour bookings"

    Playground only reports a form fill or tour booking when its analytics script sits on that exact page. Miss a page, or send families to the shared form link or QR code instead of your site, and GA4 and your ad tags never see the submission, so campaigns look dead while tours fill up.

  2. 02

    "Half our Facebook leads show no source"

    UTMs only land on a lead when the properties are named exactly right, the embed code is newer than May 2026, and the family goes straight to the form. A parent who clicks through from your homepage arrives untagged.

  3. 03

    Meta is learning from inquiries that never tour

    Report only the interest form and Meta and Google bid toward parents who never come in. Playground can send later stages, but that beta integration is off by default, and Meta makes you sign in again about every 60 days or the stage conversions stop reaching it.

  4. 04

    Parents call instead of filling out the form

    Playground records calls to your CRM number on the lead, but its docs describe one number per location, not one per campaign, so a call from a Google ad looks like a call from a yard sign. Those enrollments never get credited to the ad.

Playground · the fix

What changes — Playground

  • Ads bid on enrollments

    Your tour and enrolled stages flow back to Google Ads and Meta from the pipeline, and Meta gets each family's expected annual tuition as the value.

  • Every lead keeps its source

    UTMs and click IDs follow the family from the ad into the Playground lead, by form, tour booker or phone.

  • One count per family

    Website signals and stage conversions each get one job, so a tour isn't reported twice.

Playground · architecture

What Playground actually lets you hook into

Playground documents more than most child care tools. Here's what's there and what isn't.

  1. 1

    Embed analytics script with two browser signals

    Pages with an embedded form or tour booker emit playground:lead_form_submitted and playground:event_booked. Nothing forwards them to GA4; Google Tag Manager has to pick them up.

  2. 2

    UTM and click ID capture

    The same script passes UTMs and click IDs into the embedded form. UTMs save to matching lead properties; click IDs are stored but hidden.

  3. 3

    Stage-to-conversion ads integration (beta)

    Maps pipeline stages to a Meta Pixel event (such as Lead, Schedule or Purchase) and to Google Ads Import from clicks actions, once per lead per stage. Your account manager switches it on.

  4. 4

    CRM API for server-side leads

    Form submissions, bookings and leads can be posted from your server with UTMs and gclid, fbclid, fbc, msclkid or ttclid. It's the route for custom forms, and for Facebook Lead Ads through Zapier Premium.

  5. 5

    What we confirm, because it isn't documented

    Webhooks on stage changes, hashed email or phone matching, a Conversions API connection, and whether a Playground-managed site accepts a GTM container.

Playground · diagnose

Where Playground tracking breaks, in the order we check

Most Playground accounts report something. The question is whether it's the right thing, from every page, once.

  1. 01

    Is the analytics script on every page with an embed?

    Ad landing pages are where it's most often missing.

  2. 02

    Is the embed code from before May 2026?

    Older embeds don't carry UTMs, so leads arrive with no source.

  3. 03

    Do the UTM lead properties match exactly?

    They're case-sensitive. utm_Source and utm_source are different fields.

  4. 04

    Is the same tour counted twice?

    A website Lead event plus a stage sent as Lead, or a submit label plus a stage import, can double report one family.

  5. 05

    Is the Meta connection still signed in?

    An expired sign-in stops stage conversions to Meta until someone signs back in.

  6. 06

    Are calls tied to ad visits?

    One CRM number per location can't show which ad drove the call.

Playground · prove

The QA evidence — Playground

Real submissions from ad-tagged URLs on your live site, moved through your actual pipeline.

Source of truth

Your Playground CRM pipeline: leads with source, stage history and enrollment date, plus the CCMS enrollment record

  • A tagged test inquiry arrives in Playground with the right utm_source and campaign.
  • Form and tour signals each land once in GA4, Google Ads and Meta.
  • Moving the lead into your tour and enrolled stages sends exactly one conversion per stage.
  • An imported lead, or one created straight into a later stage, sends nothing.
  • A test call from an ad visit links to its Playground lead.
  • A closed month of enrolled families matched against both platforms, family by family.
  • Repeated 30 days later and after any website or embed change.

Playground · free audit

What we check in the free audit

  • Is the analytics script on every page with an embed?
  • Is the embed code from before May 2026?
  • Do the UTM lead properties match exactly?
  • Is the same tour counted twice?
  • Is the Meta connection still signed in?
  • Are calls tied to ad visits?

Checked against

Your Playground CRM pipeline: leads with source, stage history and enrollment date, plus the CCMS enrollment record

Get my free conversion tracking audit

Free30 minutesNo obligation

Playground · when not to buy

When you don't need us for Playground

Some centers need a short settings check or nothing at all.

  • If you're full with a waitlist and not running paid ads, UTM tags on your shared links are plenty.
  • If every form uses the current script and the beta integration already sends Enrolled once per family, leave it alone.
  • If families mostly come from state referral lists or word of mouth, ad attribution won't change your decisions.
  • If the only fault is a misspelled UTM property, rename it in Playground yourself.

Playground · what we deliver

The event map on Playground

  • Interest form submitted

    From Playground's form signal, with UTMs and click IDs. A GA4 key event, not the main bid target.

  • Tour booked

    From the booking signal on your embedded tour page, reported once.

  • Call from an ad visit

    Tied to the visit that produced it, then matched to the lead Playground created.

  • Tour completed or qualified

    Sent when the family enters the stage you treat as qualified.

  • Enrolled

    The conversion that matters, sent to both platforms. Meta receives the family's expected annual tuition; Google uses the value we set on its Import from clicks action.

  • Excluded on purpose

    Imported or hand-entered leads, leads created straight into a later stage, re-enrolling families and staff tests.

Written guarantee

95%+ tracking accuracy

Measured against Your Playground CRM pipeline: leads with source, stage history and enrollment date, plus the CCMS enrollment record. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Playground questions, answered

Not directly. Embedded forms and tour bookers send two browser signals that someone has to route into GA4, usually through Google Tag Manager. Submissions through the direct form link never reach GA4.

Free · 30 min

Find out which ads actually fill your classrooms

Free30 minutesNo obligation