DPDP cookie consent banner setup
A banner with real blocking: no trackers before a yes, separate choices, Accept and Reject at equal weight, and an easy way to withdraw.
- Part of Implementation, from ₹39,999
- Connected to Google Tag Manager
Written by Shuruthi Sellamuthu. Last reviewed .
What does DPDP cookie banner setup include?
DPDP cookie banner setup includes a consent platform with equal-weight Accept and Reject buttons, analytics and marketing chosen separately, nothing but strictly necessary cookies switched on at the start, Google Tag Manager tags held back until a yes, a footer link that reopens the choices, and a four-state test of the result.
Does the DPDP Act require a cookie banner at all? We answer that in the website guide to the DPDP Act. The sections cited on this page are from the Digital Personal Data Protection Act, 2023.
The three layers of the banner
Every visitor meets the first. The other two are there for anyone who wants more control, or changes their mind.
First layer: Accept and Reject
Both buttons are the same size and colour, side by side. Saying no takes one click, the same as saying yes. The text is in plain language.Act Section 6(1)Preferences: separate choices
Analytics and marketing are chosen separately and start switched off. Only strictly necessary cookies are on by default.Act Section 6(1)Reopen link in the footer
The footer of every page carries a link that brings the choices back. A visitor who moves from Accept to Reject sees the tags stop.Act Section 6(4)Illustrations of the three layers, not screenshots of a client website. Your banner is built in your brand style.
What we see in practice
On banner work we keep meeting the same three situations. One: the site has no banner. Two: a banner is there, yet it was never wired to Google Tag Manager, so analytics and marketing tags have already fired by the time the first layer appears. Three: the Reject button changes nothing, and a visitor who accepted and later rejects still has tags firing or cookies left in the browser.
How the banner connects to Google Tag Manager
A banner on its own only records a choice. Something has to act on it. That is Google Tag Manager.
- The banner records the visitor's choice.
- Google Tag Manager picks that choice up. Each tag is given a consent type, and every type starts as denied.
- A tag without a matching yes stays silent. If the visitor changes the choice later, the tags change with it.
- Hard-coded scripts are moved into Google Tag Manager, and Google Consent Mode v2 is connected.
More detail: Consent Mode v2 and tag gating.
| Tag | Consent type | Before a choice | After Accept | After Reject |
|---|---|---|---|---|
| Google Analytics | Analytics | Waits | Fires | Waits |
| Heatmaps | Analytics | Waits | Fires | Waits |
| Google Ads | Marketing | Waits | Fires | Waits |
| Meta Pixel | Marketing | Waits | Fires | Waits |
| Marketing | Waits | Fires | Waits |
Example mapping. Yours is written from your own tag list and handed over as a consent mapping sheet.
The four-state test
Clicking Accept once proves very little. Each of the four states is tested from a fresh visit, and we write down which tags fired.
No choice
We open the site as a new visitor and leave the banner alone.
No analytics or marketing tag loads.
Accept
We accept, then check which tags fire and under which consent type.
Only the tags the visitor agreed to fire.
Reject
We reject, move between pages and come back later.
Tags stay off, on every page and on return visits.
Accept, then Reject
We accept, reopen the choices from the footer link and switch to Reject.
The tags stop. We test this on every tag.
The fourth state is the one we most often find untested. If tags keep firing after a visitor changes their mind, the website is still collecting data without consent.
See how we test a websiteWhat you get
- A three-layer banner styled to your brand, in a consent platform account registered to your company
- Your Google Tag Manager container updated, with a note on each version
- A sheet that maps each tag to its consent type
- A footer link that reopens the banner choices
- A test record for all four states, with before and after evidence
Which consent platform?
CookieYes is the platform we set up most often. If you already have another one and it can block tags properly, we keep it.
- The account is in your name
- You pay the licence directly to the platform
- The consent records stay with you if you ever change vendor
Access needed for banner work: your consent platform, Google Tag Manager and the website CMS. Your CRM is never part of it.
What banner setup costs
The banner is part of our Implementation. There is no banner-only price, because a banner without tag gating and testing only looks right.
The same fee covers form consent and the privacy policy and cookie policy drafts.
DPDPWeb works on websites only: cookie banners, form consent, and privacy and cookie policy pages. We are not a DPO service and not a law firm. Nothing on this site is legal advice.
Cookie banner questions
Which consent platform do you use?
CookieYes is our usual choice for the banner, though we do not insist on it. If the banner tool you already run can hold tags back until a visitor chooses, we configure that one instead. Either way the account sits in your company's name and the platform bills the licence to you.
We already have a banner. Do you replace it?
Not always. If your platform can block tags properly, we keep it and fix the setup around it. A Website Audit shows which it is.
Can we buy only the banner?
No. The banner is part of the Implementation, from ₹39,999, together with tag gating, form consent, the policy drafts and testing.
Will our Google Analytics data drop?
Reported visits usually fall once the banner holds analytics back until a yes. How far depends on how many of your visitors accept, so it differs from site to site. Whether you run Basic or Advanced mode also matters, and that is decided with your legal contact. Both modes are compared on the Consent Mode v2 and tag gating page.
Do you need developer time from us?
Often not for the banner itself. The three layers are configured inside the consent platform, and the tags are tied to consent types in Google Tag Manager. A developer is needed only where a tracking script was pasted straight into the site code and has to be moved.
Can the banner show in more than one language?
Yes. Starter includes 1 language and Growth includes 2. Each extra language is ₹5,000. You supply or approve the translation.
Does the banner cover EU and US visitors too?
Yes. One banner can follow a different rule set for each region, so visitors in India, the EU and the US each get the right one. Consent setups for GDPR and CCPA are work we have done before. Region rules come with the Growth plan.
What happens after the banner is live?
Support runs for 30 days from launch. From then on, new tags and plugins are what usually breaks a banner, and a monthly DPDP Care Plan rescans the site and retests it.
See what your site loads before a visitor chooses
Send us your URL and we check the homepage: whether a banner shows, whether Reject sits beside Accept, and what loads before a choice. The one-page summary reaches you by email within two working days, with no call required.