Dynamic Product Ads: Content View Implementation

Time for Completion: 10 minutes

 _____________________________________________________________________________

Instructions

Place both the LiveConnect Tag and the Content View page script in the header section of your webpage for the specific section.

Use the LiveConnect Tag provided by your account team, as it will contain a unique App_ID variable. The LiveConnect Tag below is an example (e.g. a-0045). The LiveConnect Tag below (above the Content View page script) is an example.

The below Content View page script includes placeholders (denoted in green) that represent where your specific website dynamic values should be placed. Please use the below Content View page script for implementation.

<script type="text/javascript" src="//b-code.liadm.com/a-xxxx.min.js" async="true"></script>

<script>
   window.liQ = window.liQ || [];
   window.liQ.push
      { event: "viewContent",
          email: "[USER_EMAIL]",
          contentType: "[CONTENT_TYPE]",
          name: "[CONTENT_NAME]",
          contentID: "[CONTENT_ID]"
       };
</script>

 

Parameter: Value

Requested Value Output

Value Format

Status

Notes

event: "viewContent"

"viewContent"

"viewContent"

Required

Pre-hardcoded, no change needed

email: "[USER_EMAIL]

Email address of logged in or known site visitor

String

Highly Recommended

Can be passed as a MD5 hash instead (emailHash: "[Email_Hash]")

contentType: "[CONTENT_TYPE]"

Page content type

String, Valid Values: "Product", "LandingPage", "Article", "Hotel", "Flight", "Destination"

Highly Recommended

 

name: "[CONTENT_NAME]"

Content name

String

Optional

 

contentID: "[CONTENT_ID]"

Quantity of product

String

Required

Needs to match Product IDs shared with the product feed.

Example Output:

<script>
   window.liQ = window.liQ || [];
   window.liQ.push
      { event: "viewContent",
          email: "ironman@liveintent.com",
          contentType: "Product",
          name: "ArcReactors",
          contentID: "34878dfdfd"
      };
</script>

 

 

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk