Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Netherlands based header bidding analytics and yield optimization platform for digital publishers, with log level reporting and prebid auction insights.
Assertive Yield is a Netherlands based yield optimization and analytics platform for digital publishers, founded in 2020 and headquartered in Amsterdam. It is implemented as a prebid wrapper and JavaScript analytics tag that hooks into the header bidding auction lifecycle, capturing bid requests, bid responses, win and timeout events at log level. Publishers use it for header bidding analytics, A/B testing of ad stacks, revenue attribution, and forensic investigation of auction performance.
The tag collects auction telemetry such as ad unit, bidder, bid amount, currency, latency, render outcome and viewport characteristics. It reads the IAB TCF consent string (euconsent-v2) and sets first party cookies including ay_session for session correlation and ay_user as a pseudonymous client identifier. Device, browser, country (from IP) and referrer information are derived. No directly identifying customer data is required; identifiers are pseudonymous and bound to the publisher domain.
Although Assertive Yield itself is primarily an analytics layer, it operates inside the header bidding chain that distributes user signals to SSPs and DSPs. ePrivacy Article 5(3) and the German TDDDG Section 25 require prior consent before non essential cookies or device access. In practice the controller is the publisher, and Assertive Yield acts as a processor under a data processing agreement. Joint controllership analysis may be needed with bidders downstream.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Consent under Art. 6(1)(a) GDPR is the appropriate legal basis because the service is part of advertising measurement and selection. The CMP must collect consent for IAB TCF purposes 7 (ad performance), 8 (content performance), 9 (market research) and 10 (product development) and pass a valid TC string to prebid. Assertive Yield should be configured to suppress identifier setting when the relevant purposes are refused, and to ingest only aggregated data in that case.
Primary processing happens in the EU on AWS Frankfurt and Ireland, but auxiliary services (Google Cloud, Cloudflare, monitoring vendors) may involve US transfers under Standard Contractual Clauses and the EU US Data Privacy Framework. Sign the DPA, list Assertive Yield in your record of processing and cookie policy, configure the CMP to gate the prebid wrapper, set realistic retention on raw logs (90 to 180 days typical), and verify that aggregated reporting honors consent withdrawal.
Websites using Assertive Yield must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is recommended when Assertive Yield is combined with extensive bidder integrations or first party identifiers. Document the categories of auction data collected, retention windows, joint controller relationships with SSPs and bidders, and the consent signalling chain from CMP to prebid to Assertive Yield.
Sample consent text
We use Assertive Yield to analyse and optimise the advertising auctions on this site. This involves processing auction events, device and connection signals, and a pseudonymous identifier in cookies. Do you consent to this analytics and advertising measurement?
Third-party domains contacted
assertiveyield.comcdn.assertiveyield.comay.assertive.runprebid-cdn.assertiveyield.comanalytics.assertiveyield.comapi.assertiveyield.comlogs.assertiveyield.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| ay_session | first_party | Session | Session correlation for matching auction events to a single page view |
| ay_user | first_party | 1 year | Pseudonymous client identifier used for revenue attribution and A/B testing of ad stacks |
| euconsent-v2 | first_party | 6 to 13 months | IAB TCF consent string read by Assertive Yield to determine permitted purposes (set by the CMP, not Assertive Yield itself) |
| ay_ab | first_party | 30 days | A/B test bucket assignment so the same user sees a consistent ad stack variant during an experiment |
| ay_geo | first_party | 24 hours | Cached country and region derived from IP, used to apply region specific compliance rules without repeated lookups |
| ay_diag | first_party | 7 days | Diagnostic flag enabling verbose log forwarding for ad ops debugging; exact name depends on integration |
Assertive Yield places tracking cookies for advertising — comply with GDPR using FlowConsent.
Assertive Yield typically sets first party cookies ay_session (session correlation) and ay_user (pseudonymous client identifier) on the publisher domain, and reads the IAB TCF consent string euconsent-v2. Exact cookie names can vary by integration. No cross site third party tracking cookies are required.
Yes. Because Assertive Yield is part of the advertising auction chain and sets identifier cookies, prior consent is required under ePrivacy Article 5(3) and the German TDDDG. The CMP must collect consent for the relevant IAB TCF purposes before the prebid wrapper and Assertive Yield tag fire.
Consent under Art. 6(1)(a) GDPR, mapped to IAB TCF purposes 7 (ad performance), 8 (content performance), 9 (market research) and 10 (product development). Legitimate interest is not appropriate for cookie based advertising measurement of this kind.
Primarily no. Core processing runs on AWS Frankfurt and Ireland. Some auxiliary services (Google Cloud, Cloudflare, monitoring vendors) may involve transfers to the US under Standard Contractual Clauses and the EU US Data Privacy Framework. Document this in your transfer impact assessment.
A DPIA is recommended when Assertive Yield is combined with extensive bidder integrations, first party identifiers, or large scale audience profiling. For a standalone analytics integration with consent gating, a documented LIA and ROPA entry may suffice.
Place the prebid wrapper and analytics tag behind your CMP so they only fire after consent for IAB TCF purposes 7 to 10. Sign the DPA, configure realistic log retention (90 to 180 days), list Assertive Yield in your cookie policy and ROPA, and test that withdrawal stops new identifier writes.
Yes. Comparable tools include Sincera, Adomik, STAQ, Burt Intelligence, AdStream, Salesforce Audience Manager, and the EU based Permutive. Evaluate them on EU hosting, IAB TCF integration, log level reporting, and prebid compatibility.
Add an entry naming Assertive Yield as a yield optimization and analytics processor, list the ay_session and ay_user cookies with their purpose and lifetime, note that it reads the IAB TCF consent string, and link to the Assertive Yield privacy notice and DPA reference.