Cookie Consent

Cookie consent asks each visitor whether your tracking scripts are allowed to run, and holds those scripts back until they answer. It lives in Site settings, under the Scripts & Pixels tab, and covers the pixels and analytics you add there. Turn it on when you sell into regions with privacy laws like GDPR (EU) or CCPA (California), where firing tracking cookies before a visitor agrees can put you out of compliance. Replo has its own consent banner and category system, so you do not need a separate consent tool for the pixels you manage in Scripts & Pixels. If your store already runs one, you can connect it instead.

​

How it works

When cookie consent is on, Replo does not load your tracking scripts on the first page view. Instead a banner asks the visitor to accept or reject tracking. The script tags only enter the page once the visitor grants the matching category, so nothing fires beforehand. This is stricter than tag managers that load a script and then ask it to hold back: with Replo, the script is never added to the page until consent allows it. Each managed script is tied to one or more consent categories. A script loads only after the visitor grants all of the categories it needs. With Replo’s own banner, the choice is remembered in a replo_consent cookie so returning visitors are not asked again until it expires. With a third-party consent tool connected, that tool stores the choice instead.

​

Consent modes

The Cookie consent control at the top of the Scripts & Pixels tab has three modes:

• Off: no banner, and every managed script loads immediately for every visitor. This is the default and matches how a site with no consent layer behaves.
• Simple: shows a banner with Accept all and Reject all. The visitor makes one choice that covers every category at once.
• Per category: shows the same banner plus a Customize option, where the visitor can grant some categories and deny others (for example, allow analytics but not marketing).

​

What consent gates

With consent on, these load only after the visitor agrees:

• Pixels: Google Analytics 4, Google Tag Manager, Meta Pixel, TikTok Pixel, Pinterest Tag, Reddit Pixel, Snapchat Pixel, and X Pixel.
• Behavior analytics: Hotjar and Microsoft Clarity.
• Attribution and data: Triple Whale, Segment, and Northbeam.
• Custom scripts you add in Scripts & Pixels, gated by the categories you pick.
• Replo’s own analytics, which power Insights, gated on the analytics category.

Each built-in pixel maps to a sensible category by default: analytics tools (GA4, Hotjar, Clarity) require the analytics category, and ad pixels (Meta, TikTok, Pinterest, Reddit, Snapchat, X) require marketing. Google Tag Manager requires both, since it can load either kind of tag.

​

Consent categories

Replo groups scripts into these categories, matching the standard ones used across ecommerce privacy tools:

• Necessary: always on, and never shown as a choice. These are the scripts your site needs to function.
• Analytics: measurement and traffic tools.
• Marketing: ad pixels and retargeting.
• Preferences: scripts that remember visitor settings.
• Sale of data: tracking that shares data with third parties, the category CCPA’s “Do Not Sell” rules apply to.

In Simple mode, accepting grants every category and rejecting denies all of them. In Per category mode, the visitor decides category by category.

​

Turn on cookie consent

​

Custom scripts and consent

When you add a custom script in Scripts & Pixels, and consent is on, Replo asks which consent categories it needs. The script loads only after the visitor grants every category you selected, so pick the narrowest set that fits (for example, marketing for an ad pixel, analytics for a measurement tool). You can also ask Replo in chat to add a script and tell it which category to gate on.

​

Scripts that bypass consent

Consent only covers scripts Replo manages. A script pasted straight into your site’s code, outside of Scripts & Pixels, loads for every visitor no matter what they choose. Replo flags these under Unmanaged scripts with a warning so you can spot them, and offers Convert to managed to bring them under consent. If you use tracking that you added outside Scripts & Pixels, convert it so your consent banner actually governs it.

​

Customizing the banner

The banner Replo installs has default copy (“We value your privacy”), an Accept all and Reject all button, a Customize flow in Per category mode, and a link to your privacy policy. You can ask Replo to restyle it, reword it, or point the privacy policy link at your own page. Keep the banner in place while consent is on, since it is what collects the visitor’s choice.

​

Use a third-party consent tool

If your store already runs a consent tool, connect it in the Scripts & Pixels tab, under Cookie consent, and it replaces Replo’s banner on this site: Whichever you connect:

• Its banner collects the visitor’s choice. Replo’s Cookie consent control turns Off automatically, so visitors see one banner, and the tab warns you if you turn it back on.
• Every managed script that needs consent stays off until the visitor gives it, and so does Replo’s own analytics.
• Scripts pasted directly into your site bypass the tool and load regardless of consent. The tab flags them, and Convert to managed brings each one under the tool’s control.
• If you already pasted the tool’s script into your site, remove it. Two copies fight over consent, and the tab flags this for you.
• A site uses one consent tool at a time, so connecting one replaces any other.

Other tools that block scripts one at a time, such as Termly or CookieYes, can be connected by asking Replo in chat. Replo sets up the tool’s script and script labels from its documentation. Check that its banner appears and your scripts wait for consent.

​

FAQ

​

Next steps