For agencies & lead-gen teams
Your client’s booking tool shouldn’t eat your ad attribution.
Embedded schedulers report bookings as “direct” traffic — the iframe swallows the gclid and your ROAS reporting goes dark. Cartoply’s embed fires the conversion in your client’s own analytics session, on their domain, automatically. No cross-domain configuration. No lost credit.
- Conversions fire in the client’s GA4, GTM, and Meta pixel — on their domain
- gclid, fbclid, and UTMs stored on every booking (first-touch, survives navigation)
- Zapier payloads carry attribution — CRM sync and offline conversion uploads
- Built-in A/B testing and instant booking to lift the conversion rate you’re paid on
Built for agencies running Google and Meta ads for home service and local business clients.
Report booked jobs, not clicks
The embed pushes a booking-confirmed event to the page’s dataLayer, gtag (including standard generate_lead), and Meta pixel — in the visitor’s live session. Mark it a Key Event, import it into Google Ads, and your campaign reports show real appointments.
Close the loop to revenue
Every booking stores its gclid, fbclid, UTMs, referrer, and landing page. Pipe them to the client’s CRM via Zapier and upload offline conversions when the estimate becomes a signed job — ROAS on revenue, not form-fills.
Convert more of the clicks you buy
Instant booking shows the soonest open times so urgent leads grab a slot instead of abandoning a calendar. Split test it against the classic view with built-in A/B experiments and promote whichever converts better.
How it works
Embed on the client site
One script tag — popup button or inline. It auto-detects GA4, GTM, and the Meta pixel; there’s nothing to wire up.
Ads run as usual
The embed captures UTMs and click IDs from the landing page and keeps them through the visitor’s session until they book.
Attribution just works
Conversions land in the client’s analytics with full campaign credit, and each booking carries its click ID for offline uploads.
Frequently asked questions
Why do embedded schedulers show conversions as direct traffic?
The booking happens in an iframe on the scheduler’s domain — a separate session with no gclid or UTM context. GA4 on the client’s site never sees the conversion. Cartoply fixes this by firing the event on the client’s page, inside their session, where attribution is native.
Do we need to set up cross-domain tracking?
No. Cross-domain tracking exists for sending visitors to another site; it’s fragile-to-impossible for third-party iframes. Cartoply’s embed listens for the booking confirmation and forwards it to whatever analytics is already on the page — dataLayer, gtag, fbq — plus a DOM event for anything custom.
Can we remove the Cartoply branding for clients?
Yes — paid plans remove the “Powered by Cartoply” badge from booking pages, and each client’s booking page carries their own logo, colors, and social share card.
How do we manage multiple clients?
One organization per client: each has its own team, territories, event types, booking pages, payments, and reporting. Your agency seat can administer all of them.
Stop explaining “direct traffic” to clients
Embed a Cartoply booking page on one client site and watch the conversions land in their GA4 — attributed.
Start free trial →14-day free trial · No credit card required