Consent Banner and Analytics Data Quality Review
Check how consent choices affect your measurement.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review consent and data. Banner behaviour and options: [BANNER_BEHAVIOUR]. Traffic and conversion figures before and after changes: [TRAFFIC_COMPARISON]. Tools that load before or after consent: [TOOL_LIST]. Check that non-essential tools load only after consent where required, that rejecting is as easy as accepting, that choices are remembered, and what share of traffic is lost to measurement. Explain how to report results honestly given the gap. Return a table and a note for stakeholders. Legal requirements must be checked with a qualified adviser [VERIFY] for [JURISDICTION]. Add a worked data-quality picture with invented numbers. Before the new banner 10,000 sessions were measured; after, 6,500 are measured, a fall of 35 percent, because 35 percent decline analytics cookies. Conversions recorded fell from 300 to 190, a fall of 36.7 percent, but actual orders in the shop system stayed at 310, so the analytics tool now sees about 61 percent of orders. Reporting approach: compare against shop-system totals, state the observed share, and avoid comparing pre- and post-banner periods without a note. Check behaviour: Reject all is as prominent as Accept all, choices persist, tags do not fire before consent where required, and a footer link lets users change their mind. Check that analytics settings do not collect identifiers for people who declined. Suggest privacy-friendly measurement options that do not require consent where the law allows, to be confirmed with an adviser [VERIFY]. Provide a note for stakeholders: Our analytics now captures about 60 percent of visits. Trends are reliable, absolute numbers are understated, and order numbers come from the shop system. Add a test script for three browsers and a log. Legal requirements vary between regions and change, so a qualified adviser must confirm the set-up. Add a closing step: review the banner whenever tools or regional rules change, and keep a dated record of the configuration and the legal advice taken.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.
See an example result (fictional data)
Invented. Before the new banner: 10,000 sessions measured. After: 6,500, a fall of 35 percent (3,500 / 10,000). Conversions recorded fell from 300 to 190, minus 36.7 percent. Shop system shows 310 orders, so analytics now sees 190 / 310 = 61 percent. Reporting: use the shop system for totals, state the observed share, avoid comparing before and after without a note. Check: Reject is as easy as Accept; tags do not fire before consent where required [VERIFY]. Note for stakeholders: trends are reliable, absolute counts are understated, and orders come from the shop system.
Illustrative only, made-up data. Your results will differ and must be reviewed.