Your whole quote journey in Google Tag Manager, with real premiums attached.
InsureOS publishes every step of the quote, with real premium and payment values, into the GTM container your marketing team already runs. It installs as a ready-made container, and payment conversions are confirmed by our server rather than inferred from page views.
The embedded quote form publishes a named event into your site's existing data layer each time something meaningful happens: a quote starts, a step is completed, a price is shown, a payment is made. Your tags trigger on what the customer did, so they keep working when questions move, steps are added, or the form appears on a new page.
Every event has the same documented shape, and every priced event carries the numbers marketers ask for: product, currency, premium before and after fees, the selected excess and the instalment options. Your analytics can report on premium quoted and premium paid, not just form completions.
dataLayer.push({
event: "insureos.checkout_viewed", insureos: { event_name: "checkout_viewed", flow: "full", product_code: "TRAILER_BOAT", first_occurrence: true, commercial: { product_name: "Trailer boat cover", currency: "NZD", premium_subtotal: 612.17, fees_total: 25, premium_total: 637.17, excess_amount: 500, has_installments: true, }, consent: { analytics: "granted", advertising_user_data: "granted", }, },});01
Triggers built on step addresses or button text stop firing the day a question moves, a step is added, or the form goes onto a new page. Nobody notices until the campaign report is wrong.
02
A customer who closes the tab at the payment provider, pays from an emailed link, or pays by bank transfer never sees the thank-you page. Those sales never reach the ad platform.
03
Counting form completions tells the ad platform that a $300 policy and a $3,000 policy are worth the same, so bidding optimises for volume instead of premium.
Each event is pushed as insureos. plus its name, with a flag for the first time it happens in a journey, so funnel reports count people rather than page reloads.
Download a GTM container from the portal with the variables, triggers, GA4 event tags and Google Ads conversion tags for your IDs. Every tag imports paused, so nothing fires until your team has previewed it.
Enquiries and payments are recorded by InsureOS when they actually happen, then sent to Google Ads with the original ad click. The browser event becomes a copy, not the source of truth.
Nothing is published until your consent platform reports analytics consent. Each purpose is passed through separately, and an unknown answer is never treated as a yes.
A confirmed payment is recorded when the payment settles: a card payment returning from the provider, a provider notification, a payment link, or a bank transfer your team marks as paid. Each payment counts once, and it reaches Google Ads with the click that brought the customer in.
Products and prices are what marketing needs, so they are in every event that knows them. Everything else stays inside InsureOS, alongside the payment and policy records it belongs with.
Usually not, if the quote form is already embedded. Your website’s address is registered as a tracking installation in the InsureOS portal and the form picks it up. GTM stays where it is; the InsureOS container is imported on top.
Yes. The download is a standard GTM import file, merged into your existing workspace. It adds InsureOS variables, triggers and tags and leaves everything else alone. Tags arrive paused, so your agency decides when they go live.
Any tag that runs from Google Tag Manager can trigger on InsureOS events, including GA4, Google Ads, Meta and LinkedIn tags. The ready-made container includes GA4 and Google Ads tags. Server-side conversions are available for Google Ads today.
No. Each conversion has one owner, either your browser tags or the InsureOS server, and every conversion event says which. The container only fires its Google Ads tag when the browser owns the conversion. Both sides use the same conversion reference, so Google can deduplicate if both ever send.
Product, currency, premium before and after fees, fees, the selected excess, the price range across excess options, payment options and instalments, the amount due today and the amount paid. Referred quotes carry the referral count and the customer-facing reason.
By default nothing is published to the data layer until analytics consent is granted. Server conversions are checked against the consent recorded with the enquiry before anything is sent, and hashed email is only sent when both advertising purposes were granted.
No. A missing data layer, a failing tag, a consent platform that is not loaded yet or an unavailable tracking service are all ignored. Quoting, saving, rating and payment carry on regardless.
Online quoting
Embed a real quote-to-bind flow
Automatic rating
Product definitions, rules, tables, explainable factors
Third-party integrations
Plug in the tools you already run
Payment collection
Cards, bank transfers, finance
Renewals
Re-rate, payments, automatic renewals
Document generation
Branded policy docs, certificates, receipts
Automation
Webhooks, events, integrations
APIs
Headless when you need it