Friday, January 29, 2021

IMG Vs HREF portion of the tag

 What the 1x1 Tag Will Look Like

1x1 Pixels are served by a standard ad tag.

<A HREF="http://ad.doubleclick.net/jump/N963.sdtestsitesix.com/B1898482; sz=1x1;ord=[timestamp]?">

<IMG SRC="http://ad.doubleclick.net/ad/N963.sdtestsitesix.com/B1898482;sz=1x1;ord=[timestamp]?" BORDER=0 WIDTH=1 HEIGHT=1 ALT="Click Here"></A>

NOTE: You only need to send the image portion of the tag to the publisher.

HREF Portion of the 1x1 Tag

A HREF portion of the tag includes an HTML anchor and hyperlink reference tag that tells a user's browser to call a web address when a user clicks on the image.

This isn’t necessary and should not be sent to the publisher when trafficking a 1x1 pixel. Think about it: someone can’t click on an invisible image.

What to do: remove the HREF portion before sending to the publisher.

The reasons for using a standard click command and striping out the“Jump” portion of the standard image tag is as follows:

1) Because the site is serving the creative, they would usually take the standard tag (jump and image portion) and separate the image portion from the jump potion on their page. They would then forget to generate the same ord value in both potions of the tag. In order for tag to work properly, the same ord value needs to be generated in both the image and click portion of the tag. To avoid this, we recommend removing the jump portion and creating a static click command – which doesn’t need an identical ord value.

2) Because of the way ad serving technology works, the image portion of a tag must be called first before the jump portion of the tag can work.

In the event the image portion of the 1x1 standard tag isn’t called before the user clicks on the associated creative, this will cause complications with the server.

To avoid the complications, the jump portion of the 1x1 standard tag is removed, and a static click command is created to serve along with the 1x1 image source.





No comments:

Post a Comment

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...