What a consent setup is
A consent setup is one banner plus its preference center: the consent model, the categories visitors can switch on and off, the wording, the look, and the cookie list. Each setup belongs to one property. A site loads it with a one-line install snippet.
Every setup has two published versions:
| Version | Changes when | Who sees it |
|---|---|---|
| Preview | Every time you click Save & Publish Preview | Only people who open the hosted preview link |
| Live | Only when you click Publish Live on the Consent list | Every site that carries the install snippet |
Saving never changes what visitors on your site see. That is deliberate: you can edit and review as often as you like, then decide when the change goes out.
Before you start
- Know the domain your site uses, for example
example.com. - If you want a link to a privacy request form in the preference center, publish a Shield intake form first and copy its URL.
- If you want consent decisions sent to Echo, create an Echo source first.
Create the setup
- Open Shield > Consent from the sidebar and click New Consent Setup (or Create First Setup on an empty list).
- In General, enter a Title. Visitors never see it; it only names the setup in TagPipes.
- Optional: fill in Company Display Name (shown in the preference center header) and Company Logo URL.
- Enter the Consent Cookie Domain as a bare domain such as
example.com, with nohttps://and no path. The decision is stored on this domain, so it carries across its subdomains. Leave it blank to auto-detect. This domain is also what the cookie scanner crawls. - If the same banner runs on other domains that should share one decision, list them in Linked Domains (Cross-Domain Consent), one per line. Install the same setup on every listed domain.
- Pick the Consent Model: Automatic by location, Always opt-in or Always opt-out. See Consent Setup Settings for what each does.
- Set the Theme: Banner layout, Corner radius (px) and the Accent (buttons), Background and Text colors. The Live Banner Preview on the right updates as you type; switch between Opt-out view and Opt-in view to see both banners.
- Review Consent Categories. A new setup starts with four: Strictly Necessary (locked), Analytics, Marketing and Functional. Rename, reorder, add or remove categories, and pick the Google Signals each one grants. At least one category must stay locked.
- Edit Banner Messages, Preference Center Text and Links if you want your own wording. Blank preference center fields use the built-in text shown as the placeholder.
- Click Save & Publish Preview. You are taken back to the Consent list while the preview builds.
Review the preview
On the Consent list the Preview column shows Preparing preview... for a minute or two, then Open preview. The hosted preview is fully interactive: switch regions and languages, test the Global Privacy Control signal and watch the consent signals change. Nothing on your site changes while you do this.
The Status column shows where the setup stands:
| Status | Meaning |
|---|---|
| Never Published | Saved, but no preview has been built yet |
| Queued / Publishing | A preview or live publish is in progress. The page refreshes the status on its own |
| Preview Ready | The preview is built. The setup has never been published live |
| Published | The preview is built and the setup has been published live at least once |
| Failed | The build failed. The error is shown on the edit page under Publish Status. Save again to retry |
The Last Published column shows when the setup last went live, with a Draft changes badge when you have saved edits that live sites have not received yet, or Not live if it has never been published.
Publish live
- On Shield > Consent, click the upload icon (Publish Live) in the setup's Actions column.
- Confirm in the dialog.
Sites with the install snippet receive the new configuration within minutes. The publish is recorded in Change History with your name. Then install the banner if you have not already.
Other actions on the list
| Icon | Opens |
|---|---|
| Cookies & Storage | The cookie declaration for this setup |
| Change History | Every recorded change to the setup |
| Analytics | Consent Analytics for this setup |
| Edit | The setup editor |
| Delete | Deletes the setup and removes its hosted preview and configuration. This cannot be undone |
Check it worked
- The Preview column shows Open preview, and the preview shows your wording and colors.
- After Publish Live, the Last Published column shows the time and no Draft changes badge.
- On the edit page, the Config JSON (SDK contract) link under Publish Status opens without an error. It returns an error until the first Publish Live.
Troubleshooting
| Message or symptom | Cause and fix |
|---|---|
| "Title is required." | Enter a Title in General |
| "Cookie domain must be a bare domain like ..." | Remove https:// and any path; enter only the domain, such as example.com |
| "Linked domain '...' must be a bare domain ..." | Same rule for each line of Linked Domains |
| "At least one locked (always active) category is required ..." | Tick Locked on one category, usually Strictly Necessary |
| "Region rule ... references unknown category ..." | A Lock or Unlock cell names a category key that does not exist. Use the keys from Consent Categories |
| "Select an Echo source to send consent_changed events to, or turn the Echo toggle off." | Pick an Echo source for consent events, or turn off Send consent_changed events to Echo |
| "Custom CSS must not contain HTML tags." | Custom CSS accepts CSS only, up to 20,000 characters |
| Preview failed - re-save to retry | Open the setup and click Save & Publish Preview again |
| Edits saved but the site still shows the old banner | Saving updates the preview only. Click Publish Live on the Consent list |
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Confirm any regulatory interpretation with your counsel.