Once an advertiser has set up a Floodlight activity on a webpage, you can use Chrome developer tools to confirm that everything is working correctly or to troubleshoot any problems.
Contact the web developer that implemented your Floodlights if you are unsure of where they are located. Generally, Floodlights are on a landing page or other page where a user action is being tracked.
Steps to check Floodlight implementation
- A call to
fls.doubleclick.net
(orad.doubleclick.net
if you're using image tags). The call should begin withhttp://
, orhttps://
if you're using a secure tag. - The correct values for
src=
,cat=
, andtype=
, matching the expected values for the tag that you're checking. Here's an example:<iframesrc="http://1234567.fls.doubleclick.net/activity;src=1234567;type=abc123;cat=fghij456;ord=[Random Number]?" width="1" height="1" frameborder="0" style="display:none"></iframe>
src=
: The value should be the advertiser ID that is the source of the Floodlight activity.type=
: The group tag string, which identifies the activity group with which the Floodlight activity is associated in Campaign Manager 360.cat=
: The activity tag string, which identifies the Floodlight activity.
- A random number within the Floodlight call, which changes each time you reload the page.
- For sales tags, any transaction information that belongs in the tag, such as revenue or quantity.
- Any dynamic tags that should be served along with the Floodlight tag. Make sure that you see the corresponding default tags in the list of URLs on the Media tab.
- How long it took to make the Floodlight call after the page began to load.
What did you find?
The Floodlight call is working correctly
There's no Floodlight call
The Floodlight tag is there, but takes too long to load
- In your browser, view the source code for the advertiser's webpage where the Floodlight tag is implemented:
Chrome: Choose View > Developer Tools > View Source.
Firefox: Choose Tools > Web Developer > Page Source. - In the source code, search for the activity tag string, which is the value of the
cat=
key-value in the Floodlight activity tag and serves as a unique identifier for the activity. You can find this value on the Floodlight Activity tab for the activity. - Check that the Floodlight tag is near the top of the page, just under the
<body>
tag.
Did you find the Floodlight tag in the source code?
Yes, just after the <body> tag
- If you find a difference, resend the tag to the advertiser with details about how to implement the tag correctly, without the error you found.
- If the tag is implemented correctly in the code, but doesn't show up in the HTTP tracer, go to step 3.
Yes, but far from the <body> tag
No
ord=
, num=
or qty=
key-values. These values can be found in the Floodlight tag when you run an HTTP tracer. If the Floodlight tag is long, you can copy it from your HTTP tracer and paste it into a text editor so that it's easier to read. Learn more about activity types and key-values.The counting method for an activity can be found on the activity's properties page in Trafficking.
Here are the values that you're looking for, depending on the activity type:
Activity type | ord= | num= | qty= | cost= |
Standard |
Random number |
None | None | None |
Per session | Session ID | None | None | None |
Unique | 1 | Random number | None | None |
Transactions | Order ID | None | 1 | Transaction cost |
Items sold | Order ID | None | Number of items sold | Transaction cost |
Are the key values working correctly?
Yes
No
- Confirm the counting method on the properties page for the activity.
- Ask the advertiser to implement the key values so that they receive the expected values.