Forum Discussion

Contributor 4

26 days ago

Solved

Embedded forms + G4A/Google Analytics = Broken?

Hi all, We're pushing to get proper tracking sorted and start running some paid ads online. We're aiming to create low friction landing pages so we wanted to display a button that pops up an embedd...

campaigns

digital marketing strategies

lead gen

Randy_Warner
12 days ago
You've diagnosed this correctly. The iframe security boundary is the real issue — it's not a configuration problem you can work around on your end.
The "use your own form + Zapier" path is actually more powerful than it might seem as a workaround. A native form on your landing page gives you full GA4 tracking, GTM event firing, clean attribution per campaign — everything the embedded Jobber form can't provide.
Worth knowing: Jobber's native Zapier connector includes a Create Client action, but you can't map a custom lead source. There is also a Create Request action however it only creates a basic Request; you can't map all of the details from your custom form. There's a Jobber-specific integration in the app marketplace called Adhesion Connect that does support both of these things. It supports Create Request (with full form submission mapping into the Request details) and Create Client with custom fields and custom lead source, so you can map UTM parameters and campaign data directly into the request record in Jobber along with any additional information your form captures.
The lead source tracking you were trying to solve for with GA4 can actually live inside Jobber too, not just in your analytics platform. It's a better setup for paid campaigns than the embedded form would ever have been — you just have to build it that way intentionally.

Esther

Contributor 3

26 days ago

You’re basically dealing with the friction vs tracking tradeoff most people run into with embedded forms.

The problem usually isn’t GA4 itself- embedded/iframe forms often don’t pass submission events back properly, so conversions disappear unless you set up custom GTM events or a thank-you redirect.

Personally, I’d avoid sending users to a separate page if possible because every extra click tends to hurt conversions.

What I’ve seen work best:

Keep the embedded form for lower friction
Track via Google Tag Manager custom events
Or redirect to a thank-you page after submission so GA4 has a clean conversion event

And agreed on the single CTA limitation — that’s pretty restrictive for actual landing page behavior since people convert at different scroll points.

Conrad

Contributor 4

25 days ago

Thank you Esther, that helps explain it. Really appreciate your reply.

At first look I'm leaning towards a thank you page - I see this is a simple option in Jobber settings. 👍 This page doesn't need to be unique to each request form?

Is there any reason you'd opt for Google Tag Manager, will that give more flexibility in the long term?

I should add that we're planning on running a number of different campaigns year round - would that change which option you'd use?

Esther
Contributor 3
25 days ago
Glad it helped, Conrad.
You definitely don’t need a unique thank-you page for every form if you’re just trying to track overall conversions. One thank-you page can work perfectly fine.
That said, if you’re planning to run multiple campaigns year-round, I’d probably lean toward GTM long-term because it gives you much more flexibility once the campaigns start scaling.
The big advantage is that you can track:
Which campaign generated the lead
button clicks
scroll depth
abandoned forms
specific landing page performance
different conversion actions

A single thank-you page is the fastest/simple setup, but GTM gives you cleaner attribution and better optimization data over time, especially once ad spend increases.
Honestly, most businesses don’t realize the issue isn’t getting traffic… It’s not knowing which traffic is actually converting profitably.
You could even start with the thank-you page now for simplicity, then layer GTM in later once campaign/data volume grows.