Objective

This document describes how to check and confirm if the DoubleClick Floodlight SDK is loaded in the client, and if it is sending the anonymousId information correctly for users to be matched when sent from Engage Audiences via the DV360 destination.

Product

Twilio Segment

Environment

Segment Console

Procedure 

1. From the website where tracking is enabled, open the Network inspector. 
2. Confirm that outgoing requests to idsync.segment.com appear. This confirms the destination SDK is being loaded correctly through Segment.
3. To confirm if the anonymousID is sent correctly, in the browser console, go to the Application tab and look for your website in Local Storage. Grab the value for "ajs_anonymous_id".
4. Use a base64 encoder to obtain the base64 encoded anonymousId.
5. Back in the browser Network tab, search for requests sent to cm.g.doubleclick.net. These requests will have the form cm.g.doubleclick.net/pixel?google_nid={{ googleNetworkId }}&segment_write_key={{ segmentWriteKey }}&google_hm={{ partnerProvidedId }} where partnerProvidedId will be the base64 value for "ajs_anonymous_id".
6. If this request is successful, then you can confirm that the DoubleClick Floodlight destination is being loaded in the client and the anonymousId information is being sent as expected.
    

Additional Information 

For more information, please refer to the DoubleClick Floodlight destination and DV360 destination documentation.