The tables explain how CMP consent affects cookie setting and action tracking. Publishers send consent signals; if consent is given and cookies are allowed, cookies are set; otherwise, no cookies are set. Advertisers track user actions based on consent and cookie presence. With consent and cookies, actions are tracked; without cookies, actions are not tracked. Future behavior may block cookie reading without consent.
S2S-TRK info allows tracking regardless of consent.
Publisher
| CMP from Publisher sends ... | AdSpirit attempts ... | If the browser ... | Result |
| No consent | DO NOT set cookie | (not applicable) | - no cookie - |
| Consent | Set cookie | Allows cookies | - cookie - |
| Set cookie | Does not allow cookies/deletes cookies | - no cookie - |
Advertiser
User arrives with ...
| CMP from Advertiser sends ... | AdSpirit | Result |
| Click cookie | Consent and fires action pixel with consent string attached | reads the cookie | Action tracked |
| Without cookies | Consent and fires action pixel | finds no cookie | Not tracked |
| Click cookie | Rejection and fires action pixel with consent string attached | reads (currently still!) the cookie, in the future: no cookie READING without consent | Action tracked, in the future: Not tracked |
| Without cookies | Rejection and fires action pixel | finds no cookie | Not tracked |
| S2S-TRK info parameter | Acceptance or rejection and fires action pixel WITH TRK info | reads data from TRK info | Action tracked |