CMOs: Protect Budgets From Ad Fraud in 2026

Digital ad fraud remains a persistent threat, siphoning billions from marketing budgets annually, making effective measurement and digital ad fraud protection non-negotiable for CMOs. The question isn’t if you’ll encounter it, but how effectively you detect and mitigate it to safeguard your investments.

As a marketing operations lead for over a decade, I’ve seen firsthand how quickly ad fraud tactics evolve. What worked last year won’t necessarily cut it today. We’re not just talking about simple click farms anymore; sophisticated botnets mimic human behavior with alarming precision. That’s why I insist on a robust ad verification strategy, particularly using platforms like Integral Ad Science (IAS) Signal. It’s a battle, frankly, and you need the right intelligence.

Setting Up Your Ad Verification Platform for Optimal Fraud Detection

The first step in protecting your precious advertising budget is to get your ad verification platform configured correctly. This isn’t a “set it and forget it” situation. You need to be meticulous.

Integrating with Your Demand-Side Platform (DSP)

This is where the magic starts. Your ad verification platform needs to “talk” to your DSP to apply pre-bid blocking and collect post-bid data.

1. Access DSP Settings: Log into your primary Google Ad Manager 360 account. From the left-hand navigation, click on Admin, then navigate to Companies.
2. Add Verification Vendor: Locate your ad verification partner (e.g., IAS Signal or DoubleVerify) in the list of existing companies. If they’re not there, click New Company and select “Ad Verification Provider” as the type, then input their details.
3. Enable Integration: Once the vendor is selected, click on its entry. You’ll see an option for “Integration Settings.” Here, you’ll typically need to paste an API key or an integration token provided by your ad verification platform. For IAS Signal, this is usually found under Account Settings > Integrations within their platform.
4. Define Blocking Tiers: Within your DSP, you can often set up pre-bid blocking rules. Navigate to Inventory > Brand Safety & Fraud Settings. Here, you’ll be able to choose the desired blocking tier provided by your verification partner (e.g., “Standard Blocking,” “Aggressive Blocking,” or “Custom”). I always recommend starting with “Standard” and monitoring performance before moving to “Aggressive” to avoid over-blocking legitimate impressions.

Pro Tip: Don’t just enable the integration; test it. Run a small pilot campaign with strict blocking and compare the IVT rates reported by your DSP versus your verification platform. Discrepancies often point to misconfigurations. I had a client last year whose integration was only partially active, leading to significant invalid traffic still slipping through for weeks before we caught it during a routine audit.

Configuring Campaign-Level Verification Settings

Once the global integration is done, you need to apply these settings to individual campaigns.

1. Create/Edit Campaign: In your DSP, go to Campaigns and either create a new one or select an existing campaign you wish to protect.
2. Locate Verification Module: Within the campaign setup, look for a section typically labeled “Brand Safety,” “Ad Verification,” or “Fraud Prevention.” This is usually found alongside targeting and bidding options.
3. Select Measurement & Blocking: Here, you’ll specify which metrics your verification partner should track (e.g., viewability, invalid traffic, brand safety) and apply the pre-bid blocking rules defined earlier. You might see options like “Apply Account-Level Settings” or “Override with Custom Settings.” If you have specific needs for a particular campaign (say, a highly sensitive brand safety campaign), choose “Override” and select more stringent blocking.
4. Implement Post-Bid Tags: For deeper analysis, your ad verification platform will provide post-bid measurement tags. These are usually VAST/VPAID wrappers for video or JavaScript tags for display. In Google Ad Manager, you’d typically apply these under Creatives > Creative Settings > Third-party tracking URLs. Make sure you’re using the correct “Impression” and “Viewability” trackers.

Common Mistake: Forgetting to apply post-bid tags. Pre-bid blocking is excellent, but post-bid data gives you the granular insights needed to understand what kind of fraud is being blocked and what’s still getting through. Without it, you’re flying blind on true performance.

Analyzing Ad Verification Reports: Uncovering Fraud Patterns

Setting up is half the battle; the other half is reading and reacting to the data. This is where your CMO really sees the value.

Understanding Key Metrics in IAS Signal Reports

Log into your IAS Signal dashboard. Go to Reports > Campaign Performance. I spend most of my time here.

1. Invalid Traffic (IVT) Rate: This is your primary indicator of fraud. Look at both “General Invalid Traffic (GIVT)” and “Sophisticated Invalid Traffic (SIVT).” GIVT is easier to detect (e.g., known bot lists), but SIVT is the real problem, often mimicking human behavior. If your SIVT rate is consistently above 2-3% on display or 5% on video, you have a problem.
2. Viewability Rate: While not directly fraud, low viewability (below 50% for display, 65% for video) can indicate poor placement or even hidden ads, which fraudsters love. Look for trends.
3. Brand Safety Violations: This shows if your ads appeared next to undesirable content. While not fraud, it’s critical for brand reputation. IAS Signal categorizes these, so you can see if it’s “Adult Content,” “Hate Speech,” etc.
4. Time-on-Page and Engagement Metrics: Cross-reference these with your analytics platform. If your ad verification shows low IVT but your site analytics show zero time-on-page for those clicks, something is amiss. Bots are getting smarter, sometimes even simulating basic engagement.

Expected Outcome: By regularly reviewing these metrics, you should see a clear picture of your campaign quality. A healthy campaign will have low IVT, high viewability, and minimal brand safety incidents. If a specific publisher consistently shows high IVT, it’s time to put them on your exclusion list.

Identifying and Blocking Fraudulent Sources

This is where you turn insights into action. We ran into this exact issue at my previous firm where a seemingly high-performing placement was actually delivering 15% SIVT. It looked great on paper until we dug into the IAS data.

1. Publisher/Site Analysis: In IAS Signal, navigate to Reports > Publisher Quality. Sort by “Invalid Traffic Rate (SIVT).” Any site consistently above your acceptable threshold (I recommend 3% for SIVT as a hard limit) needs immediate attention.
2. Exclusion List Management: Take the domains identified as fraudulent and add them to your DSP’s exclusion list. In Google Ad Manager 360, this is under Admin > Inventory > Exclusions. You can create a master exclusion list to apply across all campaigns.
3. Geography and Device Analysis: Fraud isn’t always site-specific. Look at IVT by geography or device type in your IAS reports. If you’re seeing abnormally high IVT from specific countries you’re not targeting, or from older Android devices, adjust your DSP targeting to exclude those segments.
4. Pre-Bid Blocking Refinement: Based on ongoing SIVT reports, you might need to adjust your pre-bid blocking rules within your DSP. If “Standard Blocking” isn’t cutting it, consider moving to “Aggressive” for specific problematic inventory or campaigns. Just be wary of over-blocking. It’s a balance.

Editorial Aside: Many vendors will tell you their built-in fraud detection is enough. It’s not. Trust me on this. While they’ve improved, dedicated third-party verification platforms catch things internal systems often miss because their entire business model is built around fraud detection. It’s like asking a fox to guard the hen house, and then asking the fox to report on how many hens are missing.

Integrating Ad Fraud Data into Attribution Models

Protecting your budget isn’t just about blocking bad traffic; it’s about making sure your performance metrics are accurate. Fraudulent impressions and clicks can completely skew your attribution models, leading to misinformed budget allocation.

Adjusting Conversions for Invalid Traffic

Your attribution model is only as good as the data you feed it. If 10% of your clicks are fraudulent, then 10% of the conversions attributed to those clicks are also suspect.

1. Export IVT Data: From your ad verification platform, export daily or weekly reports showing invalid traffic by campaign, ad group, or even creative. IAS Signal allows granular exports under Reports > Data Export.
2. Match with Conversion Data: Import this data into your analytics platform (e.g., Google Analytics 4) or your data warehouse. You’ll need to match the invalid traffic data with your conversion data using common identifiers like campaign ID, ad ID, or even timestamp where possible.
3. Apply an “Invalidation Factor”: For each campaign or segment, calculate an “invalidation factor” based on the IVT rate. For example, if a campaign has a 5% SIVT rate, you might discount its attributed conversions by 5%. This isn’t perfect, but it’s a far more accurate representation than ignoring fraud entirely.
4. Recalculate ROI: Rerun your attribution models with these adjusted conversion numbers. You’ll likely find that the ROI for certain channels or campaigns is lower than initially perceived, which is a good thing; it means you’re seeing the truth.

Pro Tip: Don’t just apply a blanket invalidation factor. Analyze the type of fraud. If it’s mostly bot traffic that never reaches your site, you might adjust impression-based attribution more heavily. If it’s click fraud that hits your landing page but leaves immediately, focus on adjusting last-click attribution. This nuance matters.

Refining Budget Allocation Based on True Performance

This is the ultimate goal: putting your money where it genuinely works.

1. Compare “Gross” vs. “Net” Performance: Create reports that show campaign performance (conversions, CPA, ROAS) both before and after adjusting for invalid traffic. The difference can be stark, especially on programmatic campaigns.
2. Shift Budget from High-Fraud Channels: If a channel, publisher, or even a specific ad format consistently shows high invalid traffic and a significantly lower “net” ROI, reduce your investment there. It’s hard to cut what looks like a performer, but if it’s riddled with bots, it’s a money pit.
3. Reinvest in Low-Fraud, High-Performing Channels: Conversely, channels that maintain strong performance even after fraud adjustments are your true winners. Increase budget allocation to these areas. This iterative process is how you continuously improve efficiency.
4. Quarterly Review Cycles: Make this a quarterly exercise. Fraudsters don’t sit still, and neither should your protective measures. New attack vectors emerge, and your budget allocation should reflect the current threat landscape.

By diligently measuring digital ad fraud and integrating those insights into your attribution and budget allocation, CMOs can ensure every dollar spent works harder. This isn’t just about preventing loss; it’s about optimizing for genuine growth.