Keep GA4 and Google Ads modeling conversions in India while honoring DPDP Act 2023 consent. Our embeddable banner emits Consent Mode v2 signals automatically — denied by default until the visitor agrees. No manual gtag plumbing.
No credit card required · One-line install
Speaks Google's consent language natively
How it works
The banner turns a visitor's consent choice into the exact signals Google's tags read — as a default before anything fires, and an update the moment they decide.
On load, the banner emits a Consent Mode default that denies ad and analytics storage before any Google tag can fire — only security_storage stays granted. Nothing is stored until the visitor chooses.
Flip one switch — “Enable Google Consent Mode v2” — in your banner settings. The widget pushes the canonical consent commands to the dataLayer itself, so you never hand-write a single gtag('consent', …) call.
Because the signals are the ones Google's own tags read, GA4 keeps pinging without cookies while consent is denied, and Google Ads can model the conversions it can no longer directly observe.
Accept-all grants every storage signal; reject-all stays denied; a custom choice maps each consented purpose to the exact signals it covers — analytics_storage, ad_user_data, and the rest.
The signals
Google defines seven consent signals. The banner sets each one from the purposes your visitor actually consented to — anything they didn't grant stays denied.
Advertising cookies & identifiers
User data sent to Google Ads
Remarketing & personalized ads
Google Analytics 4 storage
Site functionality preferences
On-site personalization
Fraud prevention — always granted
DPDP Section 6
India's DPDP Act 2023 requires free, specific, informed consent before you process personal data. The same banner that records that consent for Section 6 also drives Consent Mode — one event, both obligations met.
FAQ
Consent Mode v2 is Google's framework for passing a visitor's consent choices to Google's tags. Your site declares granted or denied states for storage signals such as analytics_storage, ad_storage, ad_user_data and ad_personalization; Google's tags read those states and adjust their behaviour — for example, GA4 stops setting cookies when analytics_storage is denied.
Yes. The embeddable consent banner emits Consent Mode v2 signals — the seven consent signals Google defines, including the ad_user_data and ad_personalization signals introduced in v2 — as both a default (before any tag fires) and an update (after the visitor chooses).
No manual consent plumbing. Enable “Google Consent Mode v2” on your banner and the widget pushes the canonical consent commands to the dataLayer itself. This works whether you load Google tags directly through gtag.js or through Google Tag Manager's built-in Consent Mode template — you don't hand-write any gtag('consent', …) calls.
Yes. Because the signals are exactly the ones Google's own tags read, GA4 and Google Ads both respond to them. While consent is denied GA4 pings without storing cookies, and Google Ads can model conversions it can't directly measure — so measurement and bidding keep functioning.
Consent Mode is the delivery mechanism; DPDP is the obligation. The banner records the visitor's purpose-level consent under Section 6 of India's DPDP Act 2023, then translates that same choice into Consent Mode signals — denied until the visitor agrees. You honour the law and keep your Google marketing stack running on the same consent event.
Add the DPDP Comply banner, enable Consent Mode v2, and let a single consent event power both your Google marketing stack and your DPDP obligations.
Get Started — It's FreeNo credit card required · Setup in under 10 minutes