← Back to Getting Started with Consent
Getting Started

Requirements before you install

You need a Trusted Site plan, a Configuration ID, permission to edit the site head or GTM, and a decision about how Google tags will load.

Account and plan

SiteTrust Consent is included on Trusted Site plans: Disclose, Verify, and Audit. You install it from the Client Trust Center after the site is on a plan. A free scan can show you the pre-consent problem. It does not give you a Configuration ID or a live banner.

  • Disclose includes the consent-first banner and consent records.
  • Verify and Audit add deeper evidence and are the plans we position for regional geo defaults.
  • One website is included on the plan. Additional sites are extra. See pricing.

What you must be able to edit

Pick one install path. Do not use both.

  • Head install. You can paste a script as the first child of <head> on every page: theme file, header plugin, Code Injection, Custom Code, or root layout.
  • Google Tag Manager. You can create Custom HTML tags and use the Consent Initialization trigger. If GTM already loads in the head, use the GTM guide and do not also put consent-widget.js in the head.

If the platform blocks header scripts, SiteTrust cannot run. Google Sites is the usual example. Move the site to a host that allows a first-in-head script.

Configuration ID

Every banner belongs to one configuration. The ID is a UUID from Banner Setup → Installation, in the field above the Header snippet. The snippet looks like this:

<script src="https://www.sitetrust.com/consent-widget.js"
  data-configuration-id="YOUR_CONFIGURATION_ID">
</script>

Without a real ID the widget cannot load your title, colors, tracker list, or AI disclosure. Do not invent an ID. Do not reuse another company's ID.

Google tags and other trackers

List every analytics, ads, chat, and pixel tool on the site before you install. After install:

  • SiteTrust Consent must load before GTM, GA4, Google Ads, Meta Pixel, Hotjar, Clarity, HubSpot, LinkedIn, TikTok, Intercom, and similar tags.
  • In GTM, GA4 and Google Ads should use the Built-in Consent Check so they wait for the consent update.
  • Do not load the same consent-widget.js in the head and in GTM.
  • Third-party embeds that secretly load pixels (LeadConnector forms, booking iframes, some chat widgets) must stay out of the first paint.

Pages the scan and badge also expect

Consent can run without these pages. The Trust Badge will not display, and Legal Pages will fail, until they exist and are reachable without login:

  • Privacy Policy
  • Terms and Conditions
  • AI Policy (SiteTrust can generate and host this in the dashboard)
  • Copyright notice and a DMCA path (required for Legal Pages on the scan, not for the live badge seal)

What you should have ready to test

  • A published site URL, not only a staging preview that strips scripts.
  • A clean browser or an Incognito window with no leftover sitetrust_consent value.
  • DevTools access (Console and Network).
  • Dashboard access to Banner Setup and Site Audit.

Next

Copy the ID from Find your Configuration ID, then follow How to install.

← Previous

What SiteTrust Consent is

Next →

Find your Configuration ID

Need help?

Email wecare@sitetrust.com with your site URL and platform. One business day response, Monday through Friday.