Consent Management

Cookie Consent

You can pass cookie consent from your Consent Management Provider in the payload or as query string parameter. We can also capture the cookie consent information from a cookie if that is set as first party cookie available to our subdomain. The FunnelConnect pipeline provides regex data capture configuration capabilities to get the information required.

For example using OneTrust’s OptanonConsent cookie:

CODE

isGpcEnabled=0&datestamp=Mon+Feb+24+2025+11%3A53%3A18+GMT%2B0000+(Greenwich+Mean+Time)&version=202501.1.0&browserGpcFlag=0&isIABGlobal=false&hosts=&consentId=f5e5e436-ddf4-44dc-8e65-9fc262013ff1&interactionCount=1&isAnonUser=1&landingPath=NotLandingPage&groups=1%3A1%2C2%3A1%2C3%3A1%2C4%3A1&intType=1&geolocation=GB%3BENG&AwaitingReconsent=false;

We extract the required information from groups=1%3A1%2C2%3A1%2C3%3A1%2C4%3A1 (decoded: 1:1,2:1,3:1,4:1), which is then mapped to our consent rules.

The cookie consent information can be stored in the user profile and the events data, and used for consent compliance checks before capturing, processing, inlining, or activating data.

If you are setting the consent cookie under domain .www.yourDomain.com we won’t be able to see it with http://fc.yourDomain.com. You should therefore set it under .yourDomain.com.