If you installed Converly through Google Tag Manager, you set up consent in Tag Manager itself rather than in your website's code. This works whichever cookie banner you use.
Once it's set up, the Converly tag only fires for visitors who accept marketing cookies, and visitors who decline aren't tracked at all.
To set it up, follow the instructions below:
Step 1: Make sure your cookie banner talks to Tag Manager
This only works if your cookie banner tells Tag Manager when a visitor accepts. Most popular cookie banners (Cookiebot, Complianz, OneTrust, Termly, Usercentrics and others) have a Google Tag Manager setup of their own, and each time a visitor accepts marketing cookies, they send Tag Manager a signal called an event.
If your cookie banner is already controlling other tags in Tag Manager (like your Google Ads or Meta tags), it's already set up and you can move on to Step 2. If not, follow your cookie banner's own Google Tag Manager setup instructions first.
Step 2: Create a trigger for marketing consent
The next step is to create a trigger that fires when a visitor accepts marketing cookies. In Tag Manager, go to Triggers in the left menu and click New. Choose Custom Event as the trigger type, and enter the event name your cookie banner uses:
- Cookiebot:
cookie_consent_marketing - Complianz:
cmplz_event_marketing - OneTrust:
OneTrustGroupsUpdated, then set the trigger to fire on Some Custom Events where theOnetrustActiveGroupsvariable matches the regular expression,C0004,(you'll need to create that variable first, as a Data Layer Variable) - Termly: Termly provides a ready-made trigger called Unblock Advertising Cookies when you import its Tag Manager setup, so use that instead of creating your own
For any other cookie banner, its Google Tag Manager instructions will tell you the name of the event it sends when someone accepts marketing or advertising cookies.
Give the trigger a name you'll recognise, such as Marketing consent given, and save it.
Step 3: Switch the Converly tag to that trigger
Now open your Converly tag (go to Tags and click on it). In the Triggering box, remove the All Pages trigger and add the marketing consent trigger you created in Step 2. Then click Save.
Important: Make sure you remove All Pages. If it's still there, the Converly tag will fire for every visitor whether they accept cookies or not.
Step 4: Publish your container
Tag Manager changes don't go live until you publish them. Click Submit in the top right, make sure Publish and Create Version is selected, give the version a name such as Converly consent, then click Publish.
Step 5: Test it works
That's it! The final step is to test it, and it only takes a couple of minutes.
First, open a new incognito window (or private window) and go to your website. When the cookie banner appears, decline marketing cookies. Then submit a test entry through one of your forms.
Now open the Activity page in Converly. The test entry should NOT appear there, because Converly never ran for that visitor.
Next, close that window, open another new incognito window, and go to your website again. This time accept marketing cookies (or click accept all), then submit another test entry. Head back to the Activity page, and this time the test conversion should show up within a moment.
If both of those happen, your cookie banner is holding Converly back properly.