Website User Consent Tool · powered by Relevant Consent
Configure and deploy branded consent banners for single rooftops, dealer groups, and the agencies behind them, from one workspace. Set categories by tier, install through Google Tag Manager or a script tag, and give shoppers a clear way to manage their preferences.
Walkthroughs are scheduled with our team. This is not a self-service signup.
Your privacy choices
Headline, copy, colors, and buttons are set per store.
The real-world problem
A dealer group might run a different website provider per brand, a different GTM container per store, and a different mix of analytics and ad pixels per market. The agency handling it all ends up managing consent one site at a time.
Some platforms do not even let the store add a standalone privacy page. Meanwhile, a banner on its own does not decide what fires. What matters is how consent is configured, where the script loads, and which tags respect it.
The Website User Consent Tool centralizes accounts and banner instances, gives each one configurable behavior, and hands you install code that fits the site.
How it works
Add each dealership, rooftop, or client site with its domain and contacts.
Basic, Ads, or Advanced sets the optional categories visitors can manage.
Match the banner to the store's brand, set controls and policy text, then review it.
Install via GTM on Consent Initialization – All Pages, or with a direct script tag.
Capabilities
Whether you run one store, twenty rooftops, or an agency book of dealer clients, each site keeps its own settings.
Keep each dealership or client account together: website domain, contact email, tracking tier, active status, tracking-control status, and audit notes. Create one or more banner instances per account.
Three defined tiers set which optional categories visitors can manage. Necessary storage stays on; visitors accept, reject, or customize the rest when those controls are enabled.
Adjust position, colors, font, corner radius, headline and explanatory copy, button labels, and category names. Choose whether to show Reject All, Customize, and a floating preferences button.
Show Privacy Policy and Terms & Conditions text in a popover straight from the banner, or keep using a Privacy Policy URL. Cookie Policy and Do Not Sell links point to existing URLs.
Every instance provides a direct script tag and a Google Tag Manager Custom HTML snippet, plus setup guidance. Preview the banner in the instance editor before you install.
Review per-instance consent logs, and on Ads and Advanced tiers, engagement summaries for the banner itself, filtered by date range.
Tracking tiers
Each account gets one tier. It defines which optional categories shoppers can accept, reject, or customize.
Necessary storage only.
For sites running only what the website needs to function.
Engagement analytics tab: not included
Necessary plus optional analytics, advertising, and personalization.
For stores running analytics and paid media through the site.
Engagement analytics tab: available
Everything in Ads, plus an identity-resolution category.
For setups that include identity-resolution tooling.
Engagement analytics tab: available
Deployment
Paste the Custom HTML snippet and fire it on the Consent Initialization – All Pages trigger so it runs before marketing tags.
For sites where GTM is not an option, add the script tag provided for that instance.
Choices last 180 days by default, configurable per instance. Shoppers may be re-prompted on expiry or after a configuration change.
Sets defaults
Google Consent Mode v2 values start as denied for optional categories.
Listens for a choice
Accept, reject, or saved custom preferences from the banner.
Updates consent
Consent Mode values are updated from the visitor's choice.
Pushes to the dataLayer
Consent details are pushed so configured tags can respond.
Vendor tags must be set up to respect Consent Mode or dataLayer signals. Built-in integrations with every vendor are not claimed.
Records & engagement
Each record holds the selected categories, timestamp, consent version, and website domain. IP address and user-agent are hashed before storage; raw values are not kept. Hashing is a safeguard, not an anonymity guarantee.
Ads and Advanced tiers add engagement analytics:
Policy popovers
Many dealer website platforms limit custom pages. Enter Privacy Policy and Terms & Conditions text in the instance settings and it opens in a popover from the banner. When popover text is supplied, the Privacy Policy link uses it; otherwise a Privacy Policy URL works.
Cookie Policy and Do Not Sell links point to existing URLs. The text shown is what you or your counsel provide; the tool does not write or validate it.
Straight talk
We would rather you know the limits up front.
Tell us about your websites, GTM setup, and tracking. We will walk through the workspace and talk honestly about what it can and cannot control on your sites.
Request a walkthroughA conversation with our team, not an instant signup.
