Website Retargeting: Tag Implementation for a Homepage

LiveIntent Website Retargeting for Advertisers captures shopper behavior on an advertiser’s website for the purpose of informing data-driven ads in LiveIntent inventory.  The insights collected include products views, shopping carts, and purchases.  These intent insights power dynamic ad creative for customers with products they have interacted with, or relevant up-sells and cross-sells. LiveIntent calculates the best product to display to each individual customer, with the goal of efficiently producing a conversion.

LiveIntent is able to accomplish this via our Website Retargeting Tag, in addition to the advertiser’s product feed.  The Website Retargeting Tag loads asynchronously and does not influence page load times or other aspects of the user experience of your website.

 

Time for Completion: 10 minutes

 _____________________________________________________________________________________

Instructions

The basic script is loaded asynchronously on the page and will not block the page from finishing its load. The link to the script connected to your account will be handed over by your account representative.

The script should be placed in the header section of your homepage.

 

Basic setup for Homepage view

<script type="text/javascript" src="//b-code.liadm.com/a-xxxx.min.js" async="true"></script>
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push(
 { event: "setEmail", email: "user@example.com"},
 { event: "viewHomePage" }
 
);
</script>

Required

Send the viewHomePage event

{ event: "viewHomePage" }

 

Optional

{ event: "setEmail", email: "user@example.com" }
{ event: "setHashedEmail", hashedEmail: "169003b1f9b7897147ddf7008e3ff649" }
  • You can send the setEmail or setHashedEmail event at any time. Not only on a page view, but also when a form is submitted. 
  • SetEmail is expecting an unencrypted email address. The tag makes sure that LiveIntent will only receive an encrypted email address as a hash. LiveIntent will never receive plain text email addresses.
  • SetHashedEmail is expecting to have a trimmed and all lower case email address before encrypted into a hash. If you don't lowercase and trim the email address before encryption, this will result in the inability to target the user or make them part of the targetable retargeting segment. For example: The encrypted hash of User@example.com results in a different hash value than user@example.com.
Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk