How iframe tracking works
An iframe is a window on your page showing a document from somewhere else: a booking calendar, a hosted enquiry form, a payment window, a map, a video player. Browsers deliberately keep that window sealed. If the embedded document comes from a different domain, your page’s scripts cannot see inside it, cannot read what was typed and cannot detect a click. This is a security rule, not a configuration you have missed, and no tag manager setting turns it off.
That leaves a few honest routes. If the embed comes from your own domain, your scripts can reach into it and the frame can also write into the parent page’s data layer. If it comes from someone else, the provider has to cooperate: many send a message out of the frame that your page can listen for, and some offer their own conversion or webhook features. Failing all that, the outcome can be confirmed on the server when the booking or payment is recorded.
Why iframe tracking matters
The things businesses embed are almost always the things that make money. Appointment bookings, hosted enquiry forms, ticket purchases and payment steps are exactly the moments you need to measure, and they are exactly the moments hidden behind a frame. A site can look thoroughly tracked while every conversion happens in a box nobody can see into.
The consequence is not just a gap in reporting. Ad platforms learn from the conversions they receive, so an unmeasured booking widget starves automated bidding of the only signal that matters and makes paid campaigns look far worse than they are.
Where iframe tracking goes wrong
The most damaging mistake is loading your own analytics tag inside the frame. The frame counts as its own page, so you get extra pageviews, an artificially split session and a self-referral from your own domain, all while still failing to link the conversion to the visit that produced it.
The second is measuring a click on the frame instead of an outcome inside it. Recording that somebody clicked where the form appears tells you about interest, not about submissions, and if it is set up as a conversion it will report success for people who typed nothing.
The third is assuming a provider’s tracking counts as yours. A booking platform’s own dashboard may show submissions, but if those numbers never reach your analytics or your ad platform, they cannot be attributed to a channel or used for bidding.
What to do about it
Start by asking the provider what they publish: a message posted out of the frame, a callback, a webhook, or a redirect to a confirmation page on your own site. A redirect is the easiest of all, because the confirmation page is yours to tag normally.
Where a message is available, listen for it and push a single clear event into the data layer, then build the conversion on that event rather than on a form submission trigger that cannot see the form. Where nothing is available, send the outcome from the server, or replace the embed with a form you control. Then test it properly: complete a real booking and confirm one event arrives, not two, and that no extra session appears. If the site is full of embeds from different suppliers, a structured tracking audit will find the gaps faster than guesswork.
