TCF vendor consent not honored
Even with a TCF-compliant banner, individual ad-tech vendors may not respect the signals transmitted through the framework. Each vendor integration needs to be tested independently.
Sourcepoint is built for publishers and enterprises that need fine-grained control over consent across multiple ad technology vendors and regulatory frameworks. The Transparency and Consent Framework (TCF) and CCPA/CPRA opt-out flows both require regular network-level testing to confirm that vendor signals are honored in practice.
Consent Platforms
Sourcepoint is an enterprise consent management platform focused on publisher use cases, supporting GDPR, TCF, CCPA/CPRA, and GPC across complex ad-tech stacks with vendor management and preference center capabilities.
Trademark
Sourcepoint is a trademark of Sourcepoint Technologies, Inc.. Lokker is not affiliated with or endorsed by Sourcepoint Technologies, Inc..
Risk and failure modes
Publishers run more third-party vendors than most sites. Each vendor integration adds a new consent path to validate and a new place for signals to be ignored.
Even with a TCF-compliant banner, individual ad-tech vendors may not respect the signals transmitted through the framework. Each vendor integration needs to be tested independently.
Prebid and header bidding stacks sometimes initialize before the Sourcepoint consent decision is made, sharing bid request data with demand partners without a valid legal basis.
Privacy policy updates and new vendor additions require re-consent. If re-consent campaigns are not validated, visitors may be operating under an outdated consent decision.
Consent and configuration
Sourcepoint can transmit the correct TCF consent string. Whether each ad-tech vendor honors it is not guaranteed by the framework. Network inspection is the only reliable way to confirm vendor behavior.
Each demand partner in a publisher ad stack needs to be tested to confirm it stops collecting data when the visitor declines.
GPC signals in a TCF context require a specific handling path that is separate from explicit consent rejection.
Consent sync between mobile and desktop properties introduces additional complexity that configuration alone cannot resolve.
Regional compliance
Sourcepoint serves both European GDPR opt-in traffic and US CCPA/CPRA opt-out traffic from the same platform. Publishers with California audiences face obligations around opt-out of sale and sharing, and GPC recognition, that need to be validated independently from GDPR opt-in paths.
How Lokker helps
Lokker provides network-layer evidence that Sourcepoint-managed consent decisions are reflected in actual ad-tech and analytics behavior, producing outputs that privacy teams and counsel can use.
Consent Validator runs each consent path on live pages and reports what vendor requests fire under each state, including GPC, giving publishers evidence for regulatory response.
Explore Consent ValidatorPrivacy Edge maintains a full inventory of outbound requests across your publisher properties, including ad-tech vendors that may be operating outside the Sourcepoint TCF scope.
Explore Privacy EdgeExplore Lokker
Each product links to its full details so you can explore features, view a demo, and understand how it applies to your Sourcepoint deployment.
Validation
Tests TCF consent paths and GPC handling at the network layer for each publisher property.
Explore Consent ValidatorIntelligence
Inventories all third-party requests including ad-tech vendors outside the TCF scope.
Explore Privacy EdgeNext step
Lokker runs automated browser-level consent flows and scans the network layer to confirm whether Sourcepoint fires in states where it should not.