DV360 Install / Embed Floodlight Tag | OpsBlu Docs

DV360 Install / Embed Floodlight Tag

Deployment approach for installing Floodlight tags for Display & Video 360 conversion tracking.

Delivery Options

  • Floodlight Global Site Tag: Direct implementation on all pages
  • Google Tag Manager: Centralized tag management (recommended)
  • Campaign Manager 360: Generate and manage tags
  • Server-side tagging: Enhanced privacy and performance (advanced)

Setup Steps

  1. Obtain Floodlight configuration ID and advertiser ID from Campaign Manager 360
  2. Create Custom HTML tag in GTM for Global Site Tag
  3. Create separate Custom HTML tags for each conversion activity
  4. Configure triggers (page view, form submit, purchase complete, etc.)
  5. Set up custom variables for dynamic values (order value, product ID, etc.)
  6. Publish container and verify with GTM Preview mode

GTM Tag Configuration

Global Site Tag (place on all pages):

<!-- Global site tag -->
<script>
  gtag('event', 'conversion', {
    'allow_custom_scripts': true,
    'u1': '[custom_variable_1]',
    'u2': '[custom_variable_2]',
    'send_to': 'DC-XXXXXXXX/invmedia/[activity_group_tag_string]+[activity_tag_string]'
  });
</script>

Conversion Activity Tag Example:

<!-- Event snippet for [Conversion Name] conversion page -->
<script>
  gtag('event', 'conversion', {
    'allow_custom_scripts': true,
    'value': {{transactionTotal}},
    'transaction_id': {{transactionId}},
    'u1': {{customVariable1}},
    'send_to': 'DC-XXXXXXXX/invmedia/purchaseactivity+standard'
  });
</script>

Direct Embed (Legacy)

Global Site Tag (Required on All Pages)

<!-- Global site tag (gtag.js) - Floodlight -->
<script async src="https://www.googletagmanager.com/gtag/js?id=DC-XXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'DC-XXXXXXXX');
</script>

Activity-Specific Tag (Place on Conversion Pages)

<!-- Event snippet for Purchase conversion page -->
<script>
  gtag('event', 'conversion', {
    'allow_custom_scripts': true,
    'value': 99.99,
    'transaction_id': 'ORDER123',
    'send_to': 'DC-XXXXXXXX/invmedia/purchase0+standard'
  });
</script>

Image Pixel Fallback (No JavaScript)

For environments where JavaScript isn't supported:

<noscript>
  <img src="https://ad.doubleclick.net/ddm/activity/src=XXXXXXXX;type=invmedia;cat=purchase0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;ord=1?" width="1" height="1" alt=""/>
</noscript>

Campaign Manager 360 Tag Generation

  1. Navigate to Advertiser → Floodlight → Activities
  2. Select or create conversion activity
  3. Click Tag to generate tag code
  4. Copy Global Site Tag and Activity Tag
  5. Provide to development team or implement in GTM

Validation Checklist

Pre-Launch

  • Global Site Tag loads on all pages
  • Activity tags fire only on designated conversion pages
  • Custom variables populate correctly
  • GTM container published to production
  • No JavaScript errors in browser console

Post-Launch

  • Test conversions using Campaign Manager's Test Conversion tool
  • Verify tags fire using Chrome DevTools Network tab
  • Check Campaign Manager Floodlight Status Report within 24 hours
  • Confirm conversion data appears in DV360 reporting
  • Monitor for tag errors or missing data

Troubleshooting

Tag Not Firing

  • Check GTM trigger configuration
  • Verify tag is enabled and published
  • Look for JavaScript errors blocking execution
  • Confirm Floodlight configuration ID is correct

Conversions Not Recording

  • Verify activity tag string matches Campaign Manager configuration
  • Check attribution windows (conversions may be outside lookback period)
  • Ensure user has cookies enabled
  • Review privacy consent settings blocking tags

Best Practices

  • Always use GTM for easier maintenance and version control
  • Test in GTM Preview mode before publishing
  • Document all custom variables and their purposes
  • Set up tag monitoring alerts
  • Implement consent mode for privacy compliance
  • Use descriptive naming conventions for activities
  • Keep global site tag separate from activity-specific tags
Back to top