How the Consentics install works

Every platform guide in this pack points back to this page for the parts that never change: what you're pasting, where to get it, and what happens after.

Consentics installs as a single script tag. It carries one identifier, your site key, and nothing else:

(Illustration only: yours will differ. See "Get your snippet" below.)

That one tag does three things: it shows the consent banner to your visitors, it records what they agree to, and it starts sending analytics for anyone who consents. There's nothing else to wire up.

The snippet shown in each guide is there to illustrate the shape, not to be filled in and pasted. Your real snippet has a site key unique to your account, and copying a placeholder key will not work.

Always copy your exact snippet from your Consentics install page (Account → Properties → your site → Install). It's ready to paste as-is: no editing required.

1. The banner appears. Once the snippet is live on your published site, visitors see your consent banner on their next page load.
2. Consentics checks for your first event. Your install page shows a waiting-for-first-event check that turns green the moment Consentics receives data from your site. If it's still waiting after a few minutes, the most common cause is a page that was saved but not published, or a caching layer serving an old version of the page. Republish, then clear any cache in front of your site.
3. Your dashboard starts reporting. Sessions, traffic sources, and trends begin populating automatically. No separate setup step, no configuration file to write.

This is the part every platform guide skips, because there's nothing to do: the banner's appearance, its consent categories, and its copy are all configured in Consentics, not on your platform. Change them once in your Consentics dashboard and every visitor sees the update immediately, without you touching the platform or re-pasting anything.

This is also why the snippet is so short. Older cookie-consent tools ask you to hand-configure banner text and category lists inside a long code block. Consentics fetches that configuration at the moment the banner loads, so the platform-side snippet only ever needs to say which site it belongs to.

• You need to be able to edit your platform's site-wide header or custom-code area. On most platforms this requires an admin or owner-level account, and on some it requires a paid plan (noted per platform).
• If your platform ships its own cookie or privacy banner, check the caveat in that platform's guide. Running two consent banners at once confuses visitors and can produce conflicting consent records: in most cases you should turn the platform's native banner off and let Consentics handle consent for the whole site.
• Changes to header or custom-code areas usually need a manual republish or save-and-publish step before they go live. Each guide notes this where the platform requires it.