Cartful + Google Tag Manager (GTM)

Does Cartful integrate with Google Tag Manager?

Yes. Cartful has a native GTM plugin in Studio. It pushes quiz events directly to the dataLayer with default parameters pre-populated. You configure GTM tags and triggers to route those events to GA4, ad platforms, or any other destination.

Why this matters for GTM users

GTM is the routing layer for most analytics and marketing stacks. If your team already uses GTM to manage tags, the fastest path to instrumenting quiz events across every destination is to push them to the dataLayer and let GTM handle distribution.

Cartful’s Studio plugin does exactly that. You select which quiz events to push, customize names and parameters if needed, and the events land in the dataLayer like any other site event. From there, your existing GTM workflow takes over — no special handling required.

This means quiz data can flow to GA4, Meta, TikTok, or any other destination you already have tags for, without touching Cartful configuration for each one.

What this integration does

The Studio plugin pushes quiz events to the dataLayer. This is a two-step model:

1. Cartful → dataLayer — Studio pushes selected events with default parameters. You control which events fire and can customize names and parameters.
2. dataLayer → destination — You configure GTM tags and triggers to route events wherever they need to go. This part is standard GTM workflow.

Available events

Cartful supports 10 canonical quiz events — including quiz:start, quiz:complete, product:addToCart, recommendations:loaded, and others. You select which to push to the dataLayer in Studio, and can rename any of them. Default parameters are pre-populated per event type (e.g., price for product:addToCart, recommended product data for recommendations:loaded) and can be modified.

How it works (setup)

Setup is split between Studio (Cartful side) and GTM (your side):

In Cartful Studio:

1. Create a GTM plugin for the quiz you want to instrument.
2. Select which events to push to the dataLayer.
3. Rename events or modify parameters if your GTM setup uses a different convention (optional).

In GTM:

4. Create triggers that listen for the Cartful dataLayer events.
5. Create tags that fire on those triggers and send data to your destination (GA4, ad pixels, etc.).
6. Set up variables if you need to extract specific event parameters for dynamic values.

Validation:

7. Use GTM Preview mode and Studio debug mode together to see events flowing end-to-end.
8. Disable debug mode in Studio before going to production.

Data mapping

Cartful	dataLayer	Notes
Quiz event (e.g., quiz:start)	dataLayer event (customizable name)	Customer controls naming in Studio.
Default parameters per event	dataLayer event properties	Pre-populated (e.g., price for product:addToCart, product data for recommendations:loaded). Modifiable.

The two-step model

It is worth understanding what Cartful does and does not own in this integration:

• Cartful owns the push. The Studio plugin is responsible for pushing events with the right names and parameters to the dataLayer.
• You own the routing. GTM tags and triggers determine where those events go and what they become at the destination.

This separation is intentional. It means you can add a new destination (another ad platform, a new analytics tool) without changing anything in Cartful — just add a new GTM tag.

Good to know

• Customer configures GTM. After setting up the Studio plugin, you must create the corresponding tags, triggers, and variables in GTM. Cartful does not auto-create GTM tags.
• Debug mode. Available and useful during setup, but must be disabled before production.
• Client-side only. Events are pushed to the dataLayer from the browser.

See: Integrations hub · Product