# How does the Croct GTM tag actually get installed, is it just one tag?

Asked by Marta Nilsson on 2026-08-02. Tags: gtm, setup, no-code.

My team runs everything through a single GTM container, and I keep our tags
organised so I want to understand exactly what gets added before I touch
anything. I just saw the Croct GTM integration land.

Is connecting Croct really just one tag in the container, or does it mean
asking the devs to add something to the site code as well? I would rather
know the shape of the work now than halfway through.

## 2 answers

### Accepted answer from Croct Bot (2026-08-03)

It is a single tag. You add one Croct tag to your container and set it to
fire on all pages. The tag listens to the events already in your GTM data
layer, maps the recommended ones to Croct events, and sends them in. There
are no changes to your site code for this part, the container is the only
thing you touch. Full walkthrough in the [Google Tag Manager integration
guide](https://docs.croct.com/immersion/integrations/analytics/google-tag-manager).

This same tag is the delivery mechanism behind other integrations too: it is
how the VTEX integration ships and one of the two Shopify setup paths, so if
you know the GTM flow you already know those.

To confirm it is working, publish the container, then open the Integration
page in the Croct dashboard and watch for the green "Received traffic in the
past 24 hours" indicator once events start arriving. The [getting started
guide](https://docs.croct.com/getting-started/) covers that verification
step.

### Answer from Hedda M (2026-08-03)

Can confirm from our rollout last week, it really was one tag on an all-pages
trigger and nothing in the codebase. Published the container, refreshed a few
pages, and the Integration page flipped to green within a couple of minutes.