Keep the tags you already have.
Your existing GTM and GA4 tags keep working. There is nothing to re-tag.
Your GTM and GA4 tags already work
This is the part most teams expect to be a migration and is not. The tracker reads window.dataLayer, so every dataLayer.push({ event: 'sign_up' }) from a Tag Manager tag, and every gtag('event', 'purchase', …), arrives as an event of that name under Goals & Events — where you can nominate any of them as a goal.
- Nothing to re-tag if your site is already instrumented for GTM or GA4.
- Pushes that happened before the script loaded are replayed, so a conversion inlined on a thank-you page is not missed.
- value and currency, top-level or in a GA4 ecommerce object, are recorded as revenue; scalar parameters become props.
- GTM’s own gtm.* messages and page_view are skipped, and the whole capture is one attribute to disable.
Installed with one tag, on any stack
One script tag before </head>, with attributes rather than a configuration UI: SPA and hash routing, wildcard path include/exclude rules, outbound links, file downloads, form submissions, scroll depth and engaged time, site-search capture, and per-page props. Everything is on by default and each is turned off with ="false". On Shopify the tag goes in theme.liquid, and a custom pixel from the app, pasted into Shopify’s Customer events, covers the checkout, thank-you and order status pages the theme never renders, recording purchases with the order total as revenue.
Connectors, when you want them
Connectors for Google Analytics 4, Google Search Console, Google Ads and Calendly are built, and they ship behind a single switch that is off — so nothing in your workspace talks to a Google API until you ask it to. Say the word and we turn them on for you.
One tag, not a catalogue
There is no marketplace to shop and no integration directory to wire up. Getting your numbers into something else goes through the read API — deliberately small, and the same one the dashboard runs on.