Thursday, December 22, 2016

Floodlight tag and Google AdWords

Floodlight tags accept Google AdWords Conversion Tracking as part of their dynamic tags. There are just few things to bear in mind when implementing this:

1) Each AdWords Account will be linked to one DoubleClick Floodlight Tag.

2) You can choose to integrate the Full Javascript Tag or the 1x1 Pixel as either a "Publisher" tag or a "Default" tag. The Google code will only send a conversion signal if the user clicked on a Google ad within the account.

3) If you need to use more than one Google AdWords Account, please make note of the following exceptions:
- You/Your client will need to generate the AdWords Conversion Tracking code for each account that your advertiser wants to track conversion activity.
- You will need to use "Publisher" tags for each account and will be required to associate the "Publisher's Site" in the Floodlight interface with the "site" that is used in the DFA creative tag. These must be two separate publishers as the pixels cannot fire at the same time.


When deciding where to place your Google AdWords Conversion Tracking, you should consider the differences between the two types of dynamic tags:

- Default Section
The pixel will fire every single time someone hits the conversion page. The AdWords Conversion Tracking code will only record a conversion if it can detect that the user has a cookie that ties to the advertiser's AdWords campaign.

I.e.: If a user clicks on a Google ad, then goes to NY Times and clicks on the advertiser's ad as part of a direct buy with the NY Times, DoubleClick will credit the NY Times with the conversion but Google will count the conversion, too, because the user has a Google cookie tied to the campaign that came from the first click.

- Publisher Section
This method requires that the advertiser is using DCM click tracking or 3PAS tags. When they create the click trackers or 3PAS tags, they will assign the site of those tags to the 'Google Display Network'. In their publisher section, they will then implement our conversion pixel under the same site name of 'Google Display Network'. This lets the Floodlight code do the heavy lifting and it will detect that the user who just converted came from a click that was associated with one of the click or 3PAS tags that they have assigned to the 'Google Display Network' and will then fire the conversion code associated with that site. This might lead to more accurate conversion numbers as Google will only be asked to count a conversion when DoubleClick tells it to count a conversion (eliminating the discrepancy example above) but if there is a longer Look-back window than 30 days, they are not using DCM click/3pas tracking or if they do not have their tagging set up properly the values will be completely off.

3 comments:

  1. I have read a few of the articles on your website now, and I really like your style of blogging. I added it to my favorites blog site list and will be checking back soon. Please check out my site as well and let me know what you think.
    role of digital marketing

    ReplyDelete
  2. This step to step information has helped me bring my business website on top in the search engine result pages that I can’t thank enough to you and Adwords Management for the help they have given. Keep posting such edifying and interesting posts that are useful as well.

    ReplyDelete
  3. It’s my first time to commenting anyplace, when I got this post I thought I might also make comment due to the present wise post.
    Dave Keys SEO Experty

    ReplyDelete

What to do when you have click discrepancies

 Verify the discrepancy by pulling a CM Report from report builder. Do the publisher and CM report dates match? Are the reports for the same...