Programmatic

Troubleshooting DV360 TCF v2.2 Consent Loss & Bid Drops

November 2, 2026

If your Display & Video 360 (DV360) line items suddenly stopped spending across European inventory, an IAB Transparency and Consent Framework (TCF) v2.2 misconfiguration is likely suppressing your bids. DV360 drops bid requests immediately when the inbound TC String lacks explicit consent for Google (Vendor 755) or fails to clear mandatory data processing purposes like Purpose 1, 3, or 4. Resolving this requires validating your publisher CMP strings, checking exchange pass-through signals, and auditing your line-item privacy settings.

Key Takeaways

  • Google is Vendor 755: If a publisher’s Consent Management Platform (CMP) omits Google (Vendor ID 755) from its Global Vendor List (GVL), DV360 will silently reject 100% of bid requests.
  • No Legitimate Interest for Personalization: Under TCF v2.2, Purpose 3 (create personalized ads profile) and Purpose 4 (select personalized ads) strictly require explicit consent; legitimate interest is no longer valid.
  • Purpose 1 is Non-Negotiable: Without Purpose 1 (store/access device data), DV360 cannot access third-party cookies or mobile advertising IDs (MAIDs), leading to an immediate bid drop for targeted lines.
  • PMP Deals Suffer Silently: Private Marketplace (PMP) and Programmatic Guaranteed (PG) deals bypass standard auction rules, but they cannot bypass TCF compliance checks inside Google’s bidder.

What Changed in IAB TCF v2.2 and Why Does DV360 Reject Your Bids?

Privacy regulations do not move slowly, but technical implementations can feel like hitting a brick wall. When the IAB Europe launched TCF v2.2, it changed how supply partners, platforms, and buyers handle consent. The biggest shift focused on removing ambiguity. Legitimate interest was completely removed as an acceptable legal basis for Purpose 3 (creating personalized ad profiles) and Purpose 4 (selecting personalized ads). You now need explicit user consent for those actions. Period.

Google enforces these rules ruthlessly inside DV360. When an ad request hits Google’s buying backend from an Supply-Side Platform (SSP), DV360 inspects the regs.ext.gdpr flag and the user.ext.consent string. If the user is located in the European Economic Area (EEA) or the UK, DV360 evaluates the string against its internal policy rules before running your line item's bid valuation.

If the user withheld consent for Purpose 1, DV360 cannot drop or read cookies, nor can it process device identifiers. If the CMP failed to register Google’s Global Vendor List ID (Vendor 755), DV360 acts as if the request has zero valid consent signals. Rather than risk regulatory fines under GDPR, DV360 simply refuses to bid. Your line item loses impressions, your pacing drops off a cliff, and your reporting dashboard shows a massive spike in bid loss attributed to policy or missing consent signals.

Diagnosing the Root Cause: Step-by-Step Ad Ops Audit

Fixing bid drops requires methodical isolation. You need to know whether the signal is breaking at the publisher CMP, the exchange translation layer, or inside your DV360 line-item settings.

Step 1: Inspect Inbound Bid Requests and TC Strings

To inspect what the CMP sends to the programmatic pipeline, load the publisher page in your browser with Developer Tools open. Open the Console tab and query the CMP directly using the standard IAB API command:

__tcfapi('getTCData', 2, (tcData, success) => { console.log(tcData); });

Look at the returned object carefully. You are searching for three specific objects within the payload:

  • purpose.consents: Ensure keys 1 (device access), 3 (profile creation), and 4 (ad selection) are set to true.
  • vendor.consents: Verify that key 755 (Google Advertising Products) is set to true.
  • tcString: Copy the base64-encoded string and paste it into an open-source IAB TC String Decoder. Confirm that the GVL version reflects version 3.0 (TCF v2.2 standard).

If Vendor 755 is missing or set to false, the CMP setup is flawed. The publisher must update their vendor list inside their CMP administrative console.

Step 2: Trace the Signal Across the SSP Layer

Even if the publisher CMP outputs a perfect string, SSPs often strip or truncate consent data when translating OpenRTB requests. Check your network request log in DevTools (filtering for outgoing requests to Rubicon, Index Exchange, PubMatic, or AppNexus).

Look inside the OpenRTB payload for the following structure:

"regs": { "ext": { "gdpr": 1 } }, "user": { "ext": { "consent": "CP123456789..." } }

If user.ext.consent is missing, empty, or malformed, your line item in DV360 will never see the consent signal. The impression opportunity dies at the exchange boundary before DV360 even evaluates your bid valuation algorithms.

Step 3: Analyze DV360 Impression Health Reporting

Head over to your DV360 partner or advertiser dashboard. Generate an Instant Report or pull custom reporting metrics grouped by Basic Category Loss Reasons and Detailed Loss Reasons.

Look for these specific indicators:

  • Filtered Bid Rate - GDPR / Privacy Policy: High percentages here mean DV360 actively threw out bid opportunities because the incoming string failed policy validation.
  • Missing Vendor Consent (ID 755): The string reached DV360, but Google was not authorized by the user.
  • Missing Purpose 1 Consent: The user opted out of storage access, neutralizing frequency capping, retargeting, and deterministic attribution.

If you suspect broader issues with custom configurations or platform blocking, compare these trends with your general brand safety rules by checking our guide on troubleshooting high IAS and DV block rates in DV360.

TCF v2.2 Consent Signal Requirements vs. DV360 Bidding Behavior

Different missing signals yield distinct responses from the DSP. The table below outlines how DV360 treats incoming inventory based on the exact state of the decoded IAB TCF v2.2 TC String.

Consent Scenario TC String State DV360 DSP Action Pacing & Delivery Impact
Full Compliance Purposes 1, 3, 4 = True; Vendor 755 = True Evaluates bid normally. Full personalization, audience targeting, and frequency capping active. 100% normal pacing. Full access to open marketplace and deal inventory.
Missing Vendor 755 Purposes 1, 3, 4 = True; Vendor 755 = False/Missing Immediate bid drop. Google bidder exits auction prior to processing line item logic. Severe drop-off. 0% spend on inventory managed by non-compliant CMP setups.
Missing Purpose 1 Purposes 3, 4 = True; Purpose 1 = False Rejects bids for personalized line items. May bid on pure contextual if non-personalized fallback is enabled. Massive under-pacing on audience-targeted campaigns; retargeting lists completely stop working.
Legitimate Interest Used for P3/P4 Purpose 3/4 set to Legitimate Interest instead of Consent TCF v2.2 policy violation. DV360 treats missing explicit consent as an absolute opt-out. Silent delivery collapse across publishers who failed to update CMP legal bases after the TCF v2.2 deadline.
Google Additional Consent (AC) Mode Standard TC String + addtl_consent parameter populated Accepts bid if vendor is listed in Google’s Ad Tech Provider (ATP) list, even if outside GVL. Restores delivery on legacy publishers using Google's AC string framework alongside TCF v2.2.

Step-by-Step Fixes for Common TCF v2.2 Bid Drop-Off Scenarios

Scenario A: Vendor 755 Missing from Publisher CMP

This is the single most common cause of complete spend failure across EU campaigns. If your target publisher uses an off-the-shelf CMP, they may have configured their vendor list using a static subset of AdTech companies, forgetting to add Google’s primary DSP vendor ID.

  1. Notify the Publisher / Exchange Representative: Send them the exact string decoded from their site. Ask them to verify that "Google Advertising Products" (GVL ID 755) is enabled under their Global Vendor List within their CMP settings.
  2. Verify Additional Consent (AC) Implementation: If the publisher uses Google AC Mode to complement TCF v2.2, ensure their CMP appends the addtl_consent string correctly (e.g., 1~7.12.35...). DV360 can read this supplementary payload for vendors registered directly with Google.
  3. Apply Temporary Pre-bid Target Filters: While the supply side fixes the string, exclude non-compliant domain clusters in DV360 so your budget reallocates cleanly to functional supply paths without inflating your bid loss rate.

Scenario B: PMP and Programmatic Guaranteed Deal Delivery Failure

Traders often assume Private Marketplace (PMP) deals and Programmatic Guaranteed (PG) contracts bypass privacy checks because contractual agreements exist between buyer and seller. They do not. DV360 enforces TCF compliance uniformly at the DSP engine level, irrespective of transaction type.

If your deal is under-pacing, check whether missing Purpose 1 or Purpose 3 consent is killing the deal's bid request rate. If you are experiencing deal pacing issues related to privacy or exchange negotiation mismatches, step through our operational checklist for fixing DV360 PMP deals that are not spending.

To resolve TCF-related PMP deal drops:

  1. Request Deal-Level Diagnostics from the Publisher SSP: Ask the publisher’s ad ops team to pull a breakdown of deal bid requests filtered by TCF status. They can see how many deal invitations were passed to DV360 without Vendor 755 or Purpose 1 consent.
  2. Enable Non-Personalized Ads (NPA) Fallback (If Applicable): If your client permits contextual targeting without tracking, adjust your DV360 Partner/Advertiser privacy options to allow non-personalized bidding when Purpose 1 is absent. Keep in mind that frequency capping and device targeting will be disabled for those impressions.
  3. Renegotiate Deal Criteria: If the publisher's user base heavily opts out of tracking, switch the line item strategy from targeted user segments to publisher-declared contextual segments built directly into the deal ID.

Scenario C: Misconfigured Legitimate Interest Signals

Before TCF v2.2, publishers frequently relied on "Legitimate Interest" to process data for Purpose 3 and Purpose 4. TCF v2.2 completely invalidated this practice. If a publisher's CMP still passes legal basis signals under Legitimate Interest for these purposes, DV360 interprets this as a missing consent signal and drops the bid.

Here is how you fix this inside your campaign workflows:

  1. Run a domain-level performance audit inside DV360. Sort your domain delivery by win-rate percentage drops over the past 30 to 60 days.
  2. Cross-reference domains showing sudden 90%+ drops against their CMP vendor list settings.
  3. Reach out to SSP account representatives to block inventory coming from publishers who haven't updated their CMP software to TCF v2.2 specifications.

Advanced Validation: Log-Level Data and SSP Verification

Surface-level UI reporting only tells part of the story. When troubleshooting complex consent drops across tens of millions of impressions, log-level analytics give you definitive answers.

If your team has configured log-level data integration, you can write custom queries to inspect consent response flags down to the auction ID level. By analyzing log tables, you can isolate exact CMP vendors, SSP identifiers, and geographic regions that fail TCF compliance checks.

For ad ops teams ready to run detailed log analytics on bid filtering, check out our technical setup guide for querying DV360 log-level data in Ads Data Hub. Pulling raw log files allows you to quantify exactly how much revenue or inventory reach is being lost due to malformed TC strings versus genuine user opt-outs.

Frequently Asked Questions

Why does DV360 drop bids even when the user clicked "Accept All" on a CMP banner?

Even if a user clicks "Accept All," the bid will drop if the CMP is improperly configured. This happens when the publisher omits Google's Global Vendor List ID (Vendor 755) from the CMP back-end, uses an outdated TCF schema version, or fails to correctly encode the string before appending it to the OpenRTB request sent to the DSP.

Can DV360 bid on inventory without Purpose 1 consent?

DV360 can only bid on inventory lacking Purpose 1 consent if the campaign allows non-personalized ads (NPA) and does not rely on device identifiers, retargeting lists, custom audiences, or frequency capping. If your line item explicitly mandates audience targeting or user-level capping, DV360 automatically drops the bid.

What is Google Vendor ID 755, and why is it mandatory for DV360 buying?

Google Vendor ID 755 represents "Google Advertising Products" within the IAB Europe Global Vendor List. Because DV360 processes user data as a vendor under GDPR rules, the CMP must explicitly register consent for Vendor 755 in the TC string for DV360 to legally buy the impression opportunity.

How can I verify if an incoming TC string is valid for TCF v2.2?

You can inspect the string using browser developer tools by executing the CMP API command __tcfapi('getTCData'). Copy the encoded tcString parameter into a free online IAB TC String Decoder and confirm that the GVL schema version is set to 3.0 or higher and that Purposes 1, 3, and 4 are marked as active consent.