GTM Platform Notes & Migration Guide

ClickMint CRO Platform — Supplemental Client Documentation Last updated: April 2026

Who this is for: teams working inside GTM, sGTM, or vendor-managed analytics stacks — and anyone migrating from the older "GTM Custom HTML" ClickMint setup.

← Back to Setup Hub

The recommended GTM integration

TL;DR: Install the ClickMint <script> tag in your page <head>, then import the events-only GTM template so GTM forwards the cm_tracking event into GA4. That is the primary and recommended way to integrate ClickMint with any GTM-centric deployment.

This pattern works with every vendor stack listed on this page (Elevar, Segment, Shopify + GTM, Tealium, Adobe, and more) because it does not touch your existing Google Tag or GA4 configuration.

Why manual `<head>` install + events-only template?

Concern	Why this is the right answer
Experiment speed	The ClickMint script in `<head>` loads before the page renders, preventing flicker. GTM Custom HTML is often appended near the end of `<body>`, which delays experiment application.
Existing analytics preserved	The events-only template adds only the `cm_tracking` event tag, trigger, and variables — nothing else changes in your GTM container.
Consent Mode compatible	Your existing Consent Mode v2 flow stays intact. ClickMint respects the same consent signals GA4 already uses.
Vendor safe	Elevar, Littledata, Triple Whale, and other vendor-managed data layers are left untouched.

Quick-start steps

Configure GA4 — complete the GA4 Experiment Tracking Setup
Install the ClickMint script in <head> — follow Approach 1 for platform-specific placement (Shopify, WordPress, Next.js, etc.)
Import the events-only GTM template — download, configure, and import from Approach 2, Option A
Preview and publish — confirm cm event tracking - serverless fires in Tag Assistant

Only use the complete GTM template (Option B) as a last resort — when you truly have no access to the page <head>. It works, but the experiment may appear visibly late.

What else is on this page

This page also covers:

Vendor-specific notes for Elevar, Segment, Shopify + GTM, Tealium, Adobe, and others
Migration instructions for teams moving from the older GTM Custom HTML setup

Vendor and platform notes

Microsoft Clarity

No ClickMint-specific change is usually needed.

Clarity does not own GA4 delivery by default
Clarity's GTM template can continue to run independently
Data-linking between Clarity and GA4 is separate from ClickMint

Segment (Twilio Segment)

Key question: does Segment own GA4 delivery, or is GA4 already managed in GTM / direct site code?

If Segment only enriches or forwards data elsewhere, no major ClickMint change is required
If Segment's Google Analytics 4 Web destination is the only reason gtag() exists, you should move GA4 ownership to direct page code or GTM before deploying ClickMint
Keep Segment for other destinations if you want — the goal is simply to ensure ClickMint can rely on standard GA4 / dataLayer behavior

PostHog

Usually no ClickMint-specific action is required.

PostHog operates independently of GA4 in most setups
If a PostHog plugin is injecting GA4 for you, move GA4 ownership to direct code or GTM before enabling ClickMint

Adobe Experience Platform Tags

Treat Adobe like any other managed tag system:

If Adobe already owns the Google tag flow, do not rip it out just for ClickMint
Prefer the GTM serverless / keep-existing-tag mental model: preserve the current GA4 owner, then add ClickMint in a way that respects that chain
If your Adobe team can place the ClickMint script directly in the page head, that is still the best-performing outcome

Tealium iQ

Tealium can act as the owner of GA4 delivery, so the same rule applies:

Avoid duplicating GA4 installs
Prefer keeping the current GA4 owner intact and adding ClickMint with an event-forwarding pattern
If your team can install the ClickMint script directly into head-managed site code, do that instead of relying on late script injection

Shopify + GTM

This is one of the most common places the new guidance matters.

If you can edit theme.liquid, install the ClickMint script there in <head> and use Approach 2 Option A for GTM event forwarding
If your theme only exposes a GTM container ID field and gives you no head script control, use Approach 2 Option B as a fallback
Do not use Shopify Pixels / Customer Events to host the ClickMint or GA4 base tag — the sandboxed iframe prevents the page-level dataLayer behavior ClickMint depends on

Klaviyo

Normally no change is needed.

Klaviyo does not typically own client-side GA4 delivery
Its UTM and email tracking can remain in place alongside ClickMint

Triple Whale

Normally no change is needed unless Triple Whale is injecting GA4 for you.

If Triple Whale owns GA4 delivery, move GA4 ownership to GTM or direct site code before enabling ClickMint
If Triple Whale is just consuming data, it can coexist normally

Elevar / Littledata

These stacks are a strong match for Approach 2.

Keep the existing Google Tag / GA4 Configuration tag in place
Keep vendor-provided data layer enrichment tags in place
Prefer Option A (events-only GTM template + manual head install) so you do not disturb the rest of the vendor-managed analytics stack
Use Option B only if the storefront team cannot place the ClickMint script in head code

Migrating from the older GTM Custom HTML setup

If you previously followed the older docs that created tags like ga4 html install and cm script, this is the safest migration order:

Document your current GTM workspace
- Save a GTM workspace version or take screenshots of the existing tags
Choose the new target path
- Preferred: Approach 2 Option A
- Fallback: Approach 2 Option B
Build and preview the new path first
- Do not pause the legacy tags until the new flow works in Preview mode
Verify ecommerce / downstream GA4 tags
- Especially purchase, add_to_cart, begin_checkout, and any vendor-managed tags
Pause the legacy ClickMint / GA4 Custom HTML tags
- Only after the new path is verified

Legacy patterns to look for

Common older tags include:

ga4 html install
cm script
Any Custom HTML tag that injects raw gtag.js
Any older ClickMint GTM tag that tries to replace your primary Google Tag

Migration warning

If your current GA4 Event tags reference an older GA4 Configuration tag directly, pausing that tag can break downstream reporting. That is why the new guidance prefers keeping the existing Google Tag in place and adding ClickMint on top.

Verification checklist

After applying the new setup, confirm all of the following:

A cm_tracking event appears in GA4 DebugView
The ClickMint script loads from experiments.api.clickmint.com
The experiment applies early enough on page load for your UX standard
Existing ecommerce events still fire as expected
No duplicate GA4 base tags are present
If GTM is involved, Tag Assistant shows the ClickMint GTM event tag firing when expected

← Back to Setup Hub | Approach 2: GTM Serverless Event Tracking