Skip to main content
Connect Usercentrics in Scripts & Pixels so its banner collects each visitor’s choice and your scripts wait for it.

Before you begin

Make sure your Usercentrics account has a service for each script you run on the site, including one for Replo’s own pixel. A custom service works, for example one named “Replo Analytics”.

Connect Usercentrics

1

Open Scripts & Pixels

In Site Builder, open Site settings and choose Scripts & Pixels.
2

Enter your Settings ID

Under Cookie consent, choose Usercentrics and enter your Settings ID. Find it in Usercentrics under Implementation, as the data-settings-id value. Script tags using data-ruleset-id aren’t supported yet.
3

Match your Usercentrics version

Under Usercentrics version, match your other sites. If their script loads from app.usercentrics.eu, choose V2. If it loads from web.cmp.usercentrics.eu, keep V3.
4

Choose a service for each script

Open each script in Scripts & Pixels and choose its Usercentrics service. Replo lists the services from your Usercentrics settings, and you can type a name too. Do this for Replo pixel as well. Scripts that still need a service show Needs service.
5

Load Usercentrics from one place

If you pasted the Usercentrics script into your site, remove it. Replo loads it for you, and Scripts & Pixels warns you if it finds a second copy. If Google Tag Manager already loads Usercentrics, let it keep doing that.
6

Publish

Publish your site to apply the change.
Connecting Usercentrics turns off Replo’s own consent banner, so visitors see one banner. It also replaces any other consent tool connected to the site.

Load Usercentrics through Google Tag Manager

If your Google Tag Manager container already loads Usercentrics, Replo shouldn’t add a second copy.
1

Connect your container

Connect Google Tag Manager in Scripts & Pixels.
2

Choose who loads Usercentrics

Open Usercentrics and set Loaded by to Google Tag Manager, before or after entering your Settings ID. If you connected more than one container, choose the one that loads Usercentrics. If you connected your container first and it already loads Usercentrics, Replo sets this for you.
3

Check your container on this domain

Check that the container’s Usercentrics tag runs on the domain your Replo site is published on, with the same Settings ID you entered here. If your tag chooses its Settings ID by domain, add this domain to that list.
Replo still holds each script until the visitor consents to its service. The difference is who loads the banner:
  • Your container runs for every visitor, because it has to run before Usercentrics can load. Tags inside it follow the consent rules you set in Google Tag Manager.
  • If the container doesn’t load Usercentrics on this domain, there’s no banner and your scripts stay off. A temporary replosites.com address may not match your container’s rules, so test on your own domain.
If other code on your site loads Usercentrics instead, choose Other site code. That code has to run for every visitor, so it can’t be a script waiting for Usercentrics consent.

How your scripts follow Usercentrics

Usercentrics works in services, so each script waits for the service you chose for it, whatever its category.
  • Names must match exactly. A script with no service, or a name that isn’t in your account, stays off for every visitor.
  • Scripts marked as necessary run for every visitor and don’t need a service.
  • Replo’s own analytics needs its own service. Until you choose one under Replo pixel, the pixel doesn’t run and Insights gets no data for the site.
If your site’s own code checks consent by category, such as with marketingAllowed(), those checks turn on only when the visitor accepts every optional service.

Check your Usercentrics settings

  • Blocking: Replo uses manual blocking, so you don’t need auto-blocking on this site.
  • Allowed domains: if your Usercentrics settings limit which domains can use them, add the domain your Replo site is published on.
  • Subdomains: if you use cross-domain consent sharing, check that a visitor’s choice carries over to your Replo subdomain. If it doesn’t, they’ll see the banner again there.

When a visitor changes their mind

Usercentrics stores the visitor’s choice and lets them change it. If a visitor turns off a service they allowed, the page reloads, because a script that has already run can’t be unloaded.

Scripts Usercentrics doesn’t cover

Usercentrics only controls scripts added through Scripts & Pixels. A script pasted straight into your site runs for every visitor, whatever they choose. Scripts & Pixels lists these under Unmanaged scripts. Convert to managed brings one under Usercentrics, and you choose its service as you convert it.

Disconnect Usercentrics

Open Usercentrics in Scripts & Pixels and choose Disconnect. Replo’s own banner stays off, so every script loads for all visitors after you publish. Turn on cookie consent first if you need it.

Next steps

Cookie Consent

See how consent works on a Replo site.

Adding Scripts

Add pixels and custom scripts.