Third Party Trackers

638 views
Skip to first unread message

Jason Owens

unread,
Jul 12, 2017, 5:17:23 PM7/12/17
to Google Web Designer beta
Hi,

I am creating ads using GWD and need to be able to implement click trackers, and third party impression trackers. Currently our ad ops team is doing some sort of hack to make it work in DFP, but it is hardly ideal. Is there a way to get these trackers in the ad before it goes off to QA and my ad-ops team? 

I am fairly new to the code side of things....I assume it may be able to go in there (The third party tag at least) and would adding the click tag as the Exit URL be the right thing to do?

Any help is very much appreciated. 

- Jason

San Khong

unread,
Jul 12, 2017, 7:08:29 PM7/12/17
to Google Web Designer beta
Hi Jason,

The support for third party tracking is provided by DoubleClick (DFP) so we are not familiar with it. You probably already saw this url.

Sorry I cannot offer more help.
San
Google Web Designer team

Dale Fenton

unread,
Jul 13, 2017, 9:04:37 AM7/13/17
to Google Web Designer beta
Hi Jason,

If you need to track clicks within an add you can tie a counter event to that action, then the "Metrics ID" you add to it will be the value that gets added to the report, and the "Is cumulative" checkbox will allow the counter to keep track of subsequent clicks if checked where it will only report a 1/0 (boolean) value if the box is not checked.

You can use the "Start timer" and "Stop timer" events in a similar way to track how long someone views a particular page or interacts with a certain item if that is reporting you need.

There is also the Pixel Loader custom component ( https://support.google.com/richmedia/answer/6308134?hl=en ) which can be used to load tracking pixels as well.

Hope that helps.
Screen Shot 2017-07-13 at 8.59.57 AM.png
Screen Shot 2017-07-13 at 9.00.17 AM.png

Jason Owens

unread,
Jul 13, 2017, 11:41:18 AM7/13/17
to Google Web Designer beta
Hey Dale,

I appreciate the response. I am aware of all of the custom tracking options however our clients don;t want our date, they want to collect their own. What I need to implement is an impression tracker so this pixel loader looks like it is what I need. Does this pixel loader have the option to track overall impressions as opposed to individual events?

We get our tracking pixel more ofthen than not wrapped up in something that looks like this:

In the URL box of the pixel loader properties, do I add one of the entire code sniuppets from above or only this portion...http://ad.doubleclick.net/ddm/ad/N6623.493337.CUEDIGITALMEDIA.COM/B8780313.118649073;sz=1x1;ord=[timestamp]?

Also, I had a hunch (screenshot attached) for loading an impression. I added an event that loads the tracking pixel from the document.body. WOuld that work at all? 

Sorry for all the questions! I am just trying to wrap my head around all this tagging stuff. I used to build and upload to AOL1 where I could simply add the trackers using a dropdown menu. 

Thank you Dale!
Screen Shot 2017-07-13 at 11.34.34 AM.png
Screen Shot 2017-07-13 at 11.34.16 AM.png

Dale Fenton

unread,
Jul 13, 2017, 12:41:56 PM7/13/17
to Google Web Designer beta
Hi Jason,

If you're just trying to track impressions you can set the event type to pageLoaded, if you need to track user interaction you can use interaction, etc.

The full list of events from the documentation are:

  • manual - trigger the event manually using the Load pixel action
  • exit
  • interaction
  • pageLoaded
  • orientation - load the pixel when the device orientation changes
  • auto - load the pixel as soon as the component loads

For expanding, non-fullscreen creative events:

  • expandStart
  • expandFinish
  • collapseStart
  • collapseFinish

For expanding, fullscreen creative events:

  • fullscreenSupport
  • fullscreenExpandStart
  • fullscreenExpandFinish
  • fullscreenCollapseStart
  • fullscreenCollapseFinish
You should be able to set the URL of the component to the URL in your tag there and I think it will just work, but you'll need to confirm with your tracking folks that the tag is firing correctly and being captured.
Reply all
Reply to author
Forward
0 new messages