Block MFA Inventory in DV360: Ad Ops Config Guide
To completely block Made-for-Advertising (MFA) inventory in Google Display & Video 360 (DV360), programmatic traders must deploy a multi-layered exclusion strategy combining DSP-native settings, third-party verification wrappers, dynamic blocklists, and custom bidding algorithms. Relying on a single toggle is insufficient because MFA domains constantly rotate URLs and manipulate ad refresh rates to evade standard filters. This guide outlines the exact, technical steps required to audit, identify, and systematically exclude MFA domains from your programmatic campaigns.
Key Takeaways
- Multi-layered Protection: Combining DV360's native brand safety filters with third-party pre-bid avoidance (IAS or DoubleVerify) reduces MFA waste by up to 90% compared to using native tools alone.
- SDF Bulk Management: Applying broad domain exclusion lists across complex multi-advertiser accounts requires bulk uploading via Structured Data Files (SDFs) to avoid human error and ensure consistency.
- Active Log Analysis: Standard reporting hides MFA behind clean top-level domain names; analyzing Log-Level Data (LLD) or using custom attention metrics is critical for identifying stealth arbitrage sites.
The Anatomy of MFA in the Programmatic Bidstream
Made-for-Advertising sites are built solely to monetize cheap programmatic traffic. They do not exist to inform or entertain; they exist to capture bids. These domains are characterized by extreme ad density (often exceeding 30% of the viewport), low-quality syndicated content, and aggressive ad auto-refresh triggers that fire every 10 to 15 seconds.
Most importantly, MFA sites rely on paid traffic arbitrage. Rather than cultivating organic search or direct traffic, these operators buy cheap clicks from native content recommendation widgets (such as Taboola or Outbrain) or sensationalized social media ads. The arbitrage loop is simple: they buy a visitor for $0.02 and serve them 15 programmatic ads via high-density placements, generating $0.05 in ad revenue before the user bounces. Because these sites generate high viewability and CTR metrics through placement manipulation, standard programmatic optimization algorithms mistakenly reward them with higher bid allocations unless explicitly blocked.
Step 1: Configuring Native DV360 Brand Safety and Content Controls
DV360 provides native brand safety features that act as your first line of defense. These should be set at the Partner or Advertiser level to inherit down to all Insertion Orders (IOs) and Line Items (LIs).
Digital Content Labels and Sensitive Categories
Navigate to Advertiser Settings > Brand Safety. Under the digital content labels section, exclude DL-MA (Mature audiences) and DL-T (Teen). While not all MFA sites carry these labels, a significant portion of arbitrage clickbait operates on the fringes of acceptable content taxonomies. Next, go to Sensitive Categories and exclude options such as Sensational & shocking and Profanity & rough language. MFA operators rely on shocking headlines to drive traffic, and these exclusions preemptively restrict your bids from serving alongside their landing pages.
The Native Google MFA Classifier
In mid-2024, Google integrated a machine-learning classifier into DV360 designed to detect and block MFA inventory automatically. In your Brand Safety targeting panel, ensure that the Made-for-Advertising (MFA) exclusion toggle is enabled. Google’s classifier evaluates sites based on ad-to-content ratios, ad refresh rates, and traffic source distribution. However, because Google operates under strict scale requirements, this classifier is relatively conservative. It targets the most egregious offenders but often misses sophisticated arbitrage sites that maintain a superficial appearance of editorial legitimacy.
Step 2: Deploying IAS and DoubleVerify Pre-Bid Avoidance
To catch the inventory that slips past native filters, you must deploy third-party verification wrappers. There is a critical financial difference between pre-bid avoidance and post-bid blocking. Pre-bid avoidance stops your DSP from bidding on the impression in the first place, saving your media budget and tech fees. Post-bid blocking allows the impression to win, but blocks the creative from rendering, meaning you still pay for the media and the verification wrapper fee.
To configure pre-bid avoidance, navigate to Advertiser Settings > Third-Party Verification. If you use DoubleVerify (DV), select Custom Contextual and link your DV profile ID. Within your DoubleVerify IQ platform portal, ensure that the MFA Avoidance profile is active. DoubleVerify categorizes MFA into tiered risk levels (High, Medium, and Low) based on ad-to-content ratios and paid traffic reliance. For strict brand-safety compliance, set your profile to block both High and Medium tiers.
If you are utilizing Integral Ad Science (IAS), select the IAS pre-bid brand safety settings within DV360 and choose MFA Protection. IAS uses proprietary AI models to score domains on a rolling basis. If you configure these third-party profiles too aggressively, you may see a sudden drop in delivery. Before making adjustments, consult our guide on troubleshooting high IAS & DoubleVerify block rates in DV360 to ensure your pre-bid settings are balanced correctly.
Step 3: Implementing Global Blocklists and Scaling via SDFs
Because third-party vendors and Google have a natural lag in updating their taxonomies, maintaining an active, manual channel blocklist is a necessity. You can source domain lists from industry groups like Jounce Media, or extract them manually from your campaign performance reports by filtering for domains with high CTR (e.g., >5% on standard display banners) and low post-click engagement.
Creating and Assigning Global Channels
Go to Partner Settings > Channels and create a new channel named "Global MFA Exclusion List". Populate this list with your identified MFA domains. By applying this channel as an exclusion at the Partner level, you ensure that every advertiser under your partner ID automatically inherits the blocklist.
Using SDFs for Bulk Exclusions
If you manage a large-scale account with legacy structures where settings are not cleanly inherited, manual UI updates are highly inefficient. Instead, you should utilize bulk editing DV360 line items using Structured Data Files (SDFs).
To do this:
- Navigate to your campaign or advertiser and click Offline Uploads > Export SDFs.
- Export your Line Items and Targeting Options.
- Open the Line Item SDF file in a spreadsheet editor. Locate the column titled
Web Site Targeting - Exclude. - Append the unique Channel ID of your "Global MFA Exclusion List" to this column across all active Line Items. Use comma separation if other channel exclusions are already present.
- Save the file as a CSV and upload it back into the DV360 UI under Offline Uploads > Upload SDFs. This process ensures absolute consistency across hundreds of line items in minutes.
Step 4: Supply-Path Optimization and Private Marketplace Redirection
The open exchange is the primary vector for MFA inventory because it operates on a highly fragmented multi-hop supply chain. MFA sites use unauthorized SSP resellers and complex ads.txt setups to inject their inventory into open auctions. To structurally eliminate this risk, you should transition your media spend toward curated Supply-Path Optimization (SPO) strategies and Private Marketplaces (PMPs).
Work directly with premium Supply-Side Platforms (SSPs) like Index Exchange, Magnite, or PubMatic to establish curated marketplaces. These SSPs offer pre-cleansed PMP deals that guarantee the exclusion of MFA sites at the seller level. By targeting these curated deals in your DV360 Line Items, you bypass the open market entirely. If you shift your budget to these deals and experience a drop in spend, you will need to diagnose the root cause. Refer to our guide on how to diagnose why PMP deals are not spending to verify deal IDs, floor prices, and targeting conflicts that could be hindering your delivery.
Step 5: Log-Level Data Audit and Custom Bidding
Advanced programmatic traders use Google Cloud Storage and Ads Data Hub (ADH) to ingest DV360 Log-Level Data (LLD). This allows you to analyze placement performance beyond the basic UI reports. When auditing your logs, look for the following red flags:
- Extreme Session Depth: Sites where a single user session triggers dozens of ad requests in a very short window. This indicates aggressive auto-refresh scripts.
- Abnormal CTR to Conversion Ratio: Domains showing CTRs above 3% but zero post-click conversions or site engagement. This points to accidental clicks caused by shifting layouts and overlapping ad containers.
- Sellers.json Discrepancies: Bid requests passing through intermediary entities that do not match the domain owner, indicating ad-arbitrage shell networks.
Once identified, you can write a Custom Bidding script in DV360 to systematically deprioritize these placements. Instead of bidding a flat CPM, you can write a script that evaluates the historical attention score of a domain. By reducing your bids on placements with high refresh rates or low attention metrics (using integrations with measurement platforms like Adelaide or Playground XYZ), you starve MFA domains of profitable bid volume, forcing your spend toward high-quality, human-centric inventory.
Frequently Asked Questions
How does Google's native MFA filter differ from third-party solutions?
Google's native MFA filter is built directly into the DV360 bidding engine and uses machine learning to analyze ad density and traffic sources on a global scale. Third-party solutions, like those from IAS or DoubleVerify, rely on their own proprietary crawler networks and contextual analysis, often offering more customizable risk-tolerance tiers (e.g., High, Medium, Low) that can be tailored to specific brand guidelines.
Will blocking MFA inventory cause a significant drop in my campaign reach?
While you may see a drop in raw impressions, your effective reach and business outcomes will improve. MFA impressions are low-quality, high-clutter placements that rarely drive genuine user engagement or conversions, meaning any reduction in scale is simply cutting out wasted spend.
How do I identify MFA domains in my DV360 basic reports?
Run a Basic Report grouped by App/Site and filter for placements showing extremely high CTR (often above 3-5% on standard display banners) paired with exceptionally low conversion rates or near-zero time-on-site. If a domain is delivering thousands of impressions but zero post-click engagement, it is highly likely to be an arbitrage or MFA site.
Can I use custom bidding scripts to automate MFA avoidance?
Yes, by writing a custom bidding script that incorporates attention metrics or historical session depth data, you can dynamically lower your bid price on domains that exhibit MFA characteristics. This approach reduces your bid value to a fraction of the floor price, effectively preventing your line items from winning impressions on those low-quality domains.