DV360 Troubleshooting & Debugging | Blue Frog Docs

DV360 Troubleshooting & Debugging

Troubleshooting playbook for Floodlight tags, attribution issues, and DV360 campaign debugging.

Symptom Library

  • Floodlight tags not firing or conversions missing
  • Attribution discrepancies between DV360 and GA4
  • Campaign spending issues (underspending or overspending)
  • Creative approval delays or rejections
  • Audience list sync failures
  • Inventory availability constraints
  • Frequency capping not working as expected
  • Cross-device attribution gaps

Investigation Workflow

Floodlight Issues

  1. Check Floodlight tag status in Campaign Manager 360
  2. Use Chrome Developer Tools Network tab to verify tag fires
  3. Review Floodlight configuration for correct advertiser ID and activity tags
  4. Verify GTM container deployment if using Tag Manager
  5. Check attribution windows and conversion counting methodology
  6. Confirm user consent settings aren't blocking tags

Attribution Discrepancies

  1. Compare attribution models between DV360 and GA4
  2. Review lookback windows (DV360 default: 30-day click, 1-day impression)
  3. Check for timezone mismatches in reporting
  4. Verify conversion counting methodology (unique vs. many-per-click)
  5. Examine cross-device attribution settings
  6. Review data sampling in GA4 vs. unsampled DV360 data

Campaign Performance Issues

  1. Check line item pacing settings and flight dates
  2. Review bid strategy and performance goals
  3. Verify targeting isn't too narrow (audience, geo, inventory)
  4. Check inventory availability and bid competitiveness
  5. Review brand safety and contextual targeting exclusions
  6. Confirm creative assets are approved and serving

Tools & Logs

  • Campaign Manager 360 Floodlight Status Report
  • Chrome DevTools Network tab for tag debugging
  • GTM Preview mode for tag validation
  • DV360 Audit Log for campaign change history
  • Floodlight Test Conversion tool
  • Google Tag Assistant Chrome extension
  • Network Debugger for API troubleshooting

Common Error Messages

"Floodlight activity not found"

  • Verify Floodlight configuration is linked to correct advertiser
  • Check activity tag string matches exactly
  • Confirm activity hasn't been archived or deleted

"Insufficient inventory available"

  • Broaden targeting parameters
  • Increase bid amounts
  • Review inventory source settings
  • Check deal ID availability

"Creative rejected"

  • Review creative specifications and file size limits
  • Check for policy violations (malware, prohibited content)
  • Verify landing page is accessible and matches advertiser domain
  • Ensure SSL certificate is valid

Escalation & Communication

  • DV360 Support via Google Marketing Platform Help Center
  • Campaign Manager 360 support for Floodlight-specific issues
  • Partner account manager for platform-wide problems
  • Technical Account Manager (TAM) for enterprise accounts
  • Document error codes, screenshots, and timestamps for support tickets

Preventive Maintenance

  • Weekly Floodlight health checks using CM360 reports
  • Monthly audit of conversion tracking configuration
  • Regular review of attribution settings and lookback windows
  • Quarterly access audit for partner and advertiser users
  • Monitor API usage and rate limits
  • Test Floodlight tags in staging before production deployment
  • Set up automated alerts for campaign underspending or overspending
// SYS.FOOTER