Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
TCF v2.2 compliant Consent Management Platform from Snigel, paired with the Snigel AdEngine. It displays the cookie banner, stores the IAB TC string and shares the user consent with all registered vendors.
Snigel AdConsent is a Consent Management Platform built by the Irish advertising company Snigel. It is registered as an IAB Europe TCF v2.2 CMP and is mainly distributed to publishers that also run the Snigel AdEngine for header bidding and direct advertising. AdConsent displays the cookie banner, captures the user choice, encodes it into the IAB TC string and shares it with every vendor declared in the publisher configuration.
AdConsent writes a first party cookie called euconsent v2 that contains the TC string, plus an internal Snigel cookie that stores diagnostic information such as the CMP version, the configuration identifier and a timestamp. The CMP also logs the consent event server side for auditing, with the truncated IP address, the publisher domain and the list of vendors that were accepted or refused.
The cookies set by AdConsent are considered strictly necessary because they store the consent record itself, which is required by Article 7 GDPR and Article 5(3) of the ePrivacy Directive. As a result the CMP can run before the banner is shown, without prior consent. The publisher still needs to make sure the banner is compliant with EDPB Guidelines 03/2022 on dark patterns and with the Belgian APD decision on IAB Europe TCF.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The banner must offer accept, refuse and customise options on the first layer. Refusal must be as visible as acceptance and the legitimate interest toggles required by TCF v2.2 must be honoured. The publisher must expose a persistent link, often called Cookie settings, so visitors can review and withdraw their consent at any time. AdConsent provides a resurface API to reopen the banner programmatically.
Snigel is established in Dublin, Ireland, and operates the AdConsent infrastructure inside the European Union. The TC string itself is, however, shared with every vendor in the Global Vendor List that the publisher activates, and many of those vendors are based in the United States. Snigel relies on the EU US Data Privacy Framework or on standard contractual clauses, depending on each vendor status.
Curate the vendor list inside the AdConsent dashboard to keep only the partners actually used by the website, configure equal weight Accept and Reject buttons on the first layer, document the consent storage retention (Snigel uses thirteen months by default), audit the TC string with the IAB CMP Validator, and update the privacy policy with a section that explains AdConsent, the TC string mechanism and the right to withdraw consent.
Websites using Snigel AdConsent must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is generally not required for AdConsent itself because it stores the consent decision, which is required by the GDPR. A DPIA may become necessary when AdConsent is combined with Snigel AdEngine on websites with very large audiences, because the broader ad stack profiles users at scale.
Sample consent text
We use Snigel AdConsent to collect and store your cookie preferences. This sets a first party cookie containing your TC string so that all advertising vendors we work with respect your choice. You can change your decision at any time from the cookie settings link in the footer.
Third-party domains contacted
snigelweb.comcmp.snigelweb.comadn.snigelweb.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| euconsent-v2 | http_persistent | 13 months | First party cookie storing the IAB TCF v2.2 TC string that encodes the user consent for all registered ad vendors. |
| _snigelcmp | http_persistent | 13 months | Internal Snigel cookie storing diagnostic information about the AdConsent CMP version, configuration identifier and timestamp. |
| sn_consent | http_persistent | 13 months | Snigel specific consent cookie used to mirror the TC string for the Snigel AdEngine. |
Snigel AdConsent is an essential service, but transparency matters. Manage all your consent with FlowConsent.
AdConsent sets a first party cookie euconsent v2 that contains the IAB TC string and an internal Snigel cookie that stores diagnostic information about the CMP version, configuration identifier and timestamp. The consent event is also logged server side for auditing.
No. The cookies set by AdConsent are strictly necessary to store and prove the consent decision, which is required by Article 7 GDPR. The CMP can therefore run before the banner is shown. Consent is, however, required for any optional analytics that the publisher activates on top of AdConsent.
Legal obligation under Article 6(1)(c) GDPR for storing the consent record, since the GDPR requires the publisher to demonstrate consent. Consent under Article 6(1)(a) GDPR applies to all downstream vendors enabled through AdConsent.
The AdConsent infrastructure runs in the European Union, but the TC string is shared with every vendor of the IAB Global Vendor List that the publisher activates. Many of those vendors are based in the United States, in which case the EU US Data Privacy Framework or standard contractual clauses apply.
A DPIA for AdConsent on its own is generally not required. When AdConsent is combined with Snigel AdEngine on a high traffic website, a broader DPIA covering the full ad stack is recommended, focusing on profiling, the number of vendors and the retention of the TC string.
Configure equal weight Accept and Reject buttons on the first layer, expose a persistent Cookie settings link, keep the vendor list limited to the partners actually used, audit the resulting TC string with the IAB CMP Validator, and document the configuration changes in your records of processing.
Other TCF v2.2 certified CMPs include Didomi, OneTrust, Sourcepoint, Cookiebot, Quantcast Choice and Sirdata. Choosing a different CMP does not change the obligations under GDPR and the ePrivacy Directive.
Add a dedicated entry for Snigel AdConsent as the CMP, explain that the cookies euconsent v2 and Snigel diagnostics are strictly necessary, list the retention (thirteen months by default), describe the IAB TC string and provide the link to the AdConsent privacy notice.