clickTag on Generic Banner?

[sarah...@gmail.com]

My team is making the transition to HTML5, and I'm testing out the possibility of using Google Web Designer for our team. However, I'm stuck on how to apply a clickTag to Generic Banners.

If creating for DoubleClick, Metrics ID for a Tap Area is available as described here:
https://support.google.com/webdesigner/answer/3263494?hl=en

However, there doesn't seem to be a simple way to do this with Generic Banners without editing the code.

Any suggestions?

If not, what is the best way to manipulate the code to make this work?

[trentjon...@gmail.com]

ditto

[Jaz]

Hi,

You can use the Tap Area component on Generic/Non Google Ads as well, are you saying that once you use the Tap Area, then add an event for exit it isn't working?

If you have a sample file we can take a look at, that may help.

thx!
jaz
Program Manager, GWD

[trentjon...@gmail.com]

Hi Jaz!

Thanks for the quick reply.

Here is my problem — I’ve created a DoubleClick ad in GWD and included a tap area component with an ad exit on my Call to Action graphic. I cannot save the action without a URL. The media tracking group is requesting that the CTA URL to be removed, I guess they want to switch it out depending on publisher for tracking purposes. Since I cannot save the exit action without the URL, I removed it in the HTML with an editor, leaving empty quotes for the URL.

"<gwd-exit metric="clickTag" url=""></gwd-exit>"

Somewhere, the GWD javascript is replacing my empty URL with the URL still in the Design View > Events when I publish the GWD file and view it in my browser.

It seems the media group has the verification from DCM support that the file now works for them, even though the URL is still active somewhere.

Is there some way to make this more intuitive, or add a help page to the knowledge base? It's very confusing for a first time creative developer.

Thank you!

[micsun-al]

I'm running in to the same issue with Enhanced Banners.  I'll give manually editing the html a try!

[micsun-al]

This worked apparently.  Either GWD should support exit targets set to a blank string, or DoubleClick/DCM Enhanced Banners should support GWD exits better.

Side note- I don't have access to DCM to test on so I think I was lucky to come across this thread when trying to figure out the issue.  Thanks trentjon!

[trentjon...@gmail.com]

Happy to have helped micsun-al.

For anyone else that is running into the same issues, here is my step-by-step process in solving the problem below.

Setup: I'm developing HTML5 DoubleClick ads in Google Web Designer. The ads need an exit to a URL address when clicking/tapping my call-to-action button. The media tracking company my client hired is using DoubleClick Campaign Manager to track the ads and switch call-to-action URLs based on their marketing data. I do not have a DCM account, so I was unable to test or see errors myself, but I do have a Studio account to upload ads.

Problem: The media group requested the touch/tap component, exit event action URL to be removed in the code so they can insert their URLs with tracking codes dynamically. I have the URL hardcoded in the action event currently for testing. GWD will not save the exit action event without a URL specified. The media group was reporting errors with the URL left in.

Solution: Setup a Tap Area Component with a Touch/Click event for an exit out of your ad as outlined in the GWD help pages. Go ahead and add the "clickTag" metrics ID and URL needed to save the event.

Publish the ad locally, or wherever you can edit the index.html file.

Open the index.html in your favorite code editor. You can do this in GWD Code View before you publish. I used an editor after publishing to make sure my edit wasn't overwritten.

Scroll down to the HTML portion of the index file, below the CSS. My component layer was at the bottom.

Find the gwd-exit tag code, and delete the URL in between the quotes. It will look like this when finished:

"<gwd-exit metric="clickTag" url=""></gwd-exit>"

Save the file. When you test in a browser, you may still get an active call-to-action link. I did. Zip the file and assets, and distribute.

All seemed to work on the DCM end.