LiveConnect Event Tags

LiveConnect Event Tags

In this article, we’ll cover how to implement and track different events on your site using the LiveConnect tag.

 

Background

LiveIntent’s LiveConnect technology consists of two parts – a base tag and event tags (which include conversion tags). The LiveConnect base tag offers many benefits: it improves campaign performance, uses people-based marketing to increase conversion from your own emails, offers advanced reporting, and allows you to dynamically retarget various audiences. Event tags can be used to track events and optimize to conversions on your site (for example, a product purchase or form fill).

When you create an event tag, you will also create a Dynamic Website Audience that is populated based on website visitors that have taken the action specified (i.e. a form fill). The Audience will inherit the name of the event tag and the Member Lifetime will be set to 30 days. For example, if you add a View Content event tag to a page for a purple sweater, then visitors to the page will be added to a Dynamic Website Audience also named View Content. You may edit your Audience details at any time.

LiveConnect Tag Implementation

Please follow the instructions in LiveConnect Implementation Guide to learn how to install the base LiveConnect tag. You will need to install the base tag before you can set up tracking for individual events.

If you use a tag manager, check out our implementation guides for Google Tag Manager, Tealium, or Shopify.

Event Tag Implementation

Add your event tag to the page on which you would like to track an event (i.e. a purchase confirmation page, ‘thank you for signing up’ page, etc.). Both the LiveConnect tag and event tag must be present on this page in order to properly track events and conversions. Just like the LiveConnect base tag, all event tags should be placed inside of the <head> section — the LiveConnect tag should be placed first and the event tag should be placed below the LiveConnect tag, before the end bracket.

Event Types

You can use predefined events to track audience and optimize to user intent on your site, or create a custom event (your account team will be able to provide you with the necessary code). Please note: you must install the event tag on specific pages of your website where the events will happen.

The available Event Types are as follows: 

Event Name Event Description

Product Purchase*

When an item has been purchased

Email Sign Up

Submitting email for newsletter subscription

Download

Downloading an app or white paper

Form Fill

Filling a form with information besides an email submission for a newsletter

Add To Cart

When a product is added to the shopping cart, e.g. click on add to cart button

View Search Result

When a search is made, e.g. when a product search query is made

View Content*

When a key page is viewed such as a product page, e.g. landing on a product detail page

View Category

When a category page is viewed

Custom Event

An event that falls outside of the types listed above. 

* Denotes the event types required to run Dynamic Product Ads. 

Each event includes parameters that pull in data related to the specific event. These parameters can be unique to your environment, so please make sure that you work with your account team to ensure that the macros you use will pass back data. You can see the list of events and parameters below. 

Product Purchase

The following parameters are included when selecting ‘Product Purchase’ as your event type. Optional fields are marked as ‘OPTIONAL’:

Event – This field will auto-populate and is static

Conversion Name – This field will auto-populate and is static

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

Conversion ID – For e-commerce products this value must match your orderID for other type of inventory such as flights, travel destinations, automobile, this value must match your transaction ID or reservation ID.

Purchase Amount – Total purchase amount (should match the amount you are using to calculate ROAS). This should not include commas.

Currency – The currency parameter must use a standard 3-letter ISO currency code. Currency Type (for example: USD)

OPTIONAL: Basket Info (Item) – Include all parameters to complete the basket

ID – The ID parameter is a freeform field. If you’re using Dynamic Product Ads, the ID must match the ID in your catalog. Needs to have a consistent case (upper or lower case).

Price – Add a price variable or static price. The price sent ust be a decimal number greater than or equal to zero. It may not include letters, special characters, currency symbols, or commas.

Quantity – Add a quantity variable or static quantity. The quantity sent must be an integer greater than or equal to zero. It may not include letters, special characters, currency symbols or commas.

Currency – The currency parameter must use a standard 3-letter ISO currency code. Currency Type (for example: USD)

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your product purchase success page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "conversion",
"name": "product_purchase",
"email": "[USER_EMAIL]",
"conversionId": "[CONVERSION_ID]",
"amount": "[PURCHASE_AMOUNT]",
"currency": "[CURRENCY_TYPE]",
"items": [
{
"id": "[PRODUCT_ID]",
"price": "[ITEM_PRICE]",
"quantity": "[QUANTITY]",
"currency": "[CURRENCY_TYPE]"
}
]
});
</script>

Email Sign Up

The following parameters are included when selecting ‘Email Sign Up’ as your event type:

Event – This field will auto-populate and is static

Conversion Name – This field will auto-populate and is static

Email or Email Hash – This email can be hashed (md5, sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your email sign up page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "conversion",
"name": "email_signup",
"emailHash": "[MD5 OR SHA1 OR SHA2]"
});
</script>

Download

The following parameters are included when selecting ‘Download’ as your event type:

Event – This field will auto-populate and is static

Conversion Name – This field will auto-populate and is static.

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your download page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "conversion",
"name": "download",
"email": "[USER_EMAIL]"
});
</script>

Form Fill

The following parameters are included when selecting ‘Form Fill’ as your event type:

Event – This field will auto-populate and is static

Conversion Name – This field will auto-populate and is static

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution. 

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your form fill page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "conversion",
"name": "form_fill",
"emailHash": "[MD5 OR SHA1 OR SHA2]"
});
</script>

Add To Cart

The following parameters are included when selecting ‘Add To Cart’ as your event type:

Event – This field will auto-populate and is static

Custom Name – Enter your custom name field.

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

OPTIONAL: Basket Info (Item) – Include all parameters to complete the basket

ID – The ID parameter is a freeform field. If you’re using Dynamic Product Ads, the ID must match the ID in your catalog. Needs to have a consistent case (upper or lower case).

Price – Add a price variable or static price. The price sent ust be a decimal number greater than or equal to zero. It may not include letters, special characters, currency symbols, or commas.

Quantity – Add a quantity variable or static quantity. The quantity sent must be an integer greater than or equal to zero. It may not include letters, special characters, currency symbols or commas.

Currency – The currency parameter must use a standard 3-letter ISO currency code. Currency Type (for example: USD)

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your add to cart page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "addToCart",
"email": "[USER_EMAIL]",
"items": [
{
"id": "[PRODUCT_ID]",
"price": "[ITEM_PRICE]",
"quantity": "[QUANTITY]",
"currency": "[CURRENCY_TYPE]"
}
]
});
</script>

View Search Result

Select the following parameters from your website that you’d like to send with this event:

Event – This field will auto-populate and is static

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

Search Term – The search string parameter is a freeform field

Item IDs – The item ID parameter is a freeform field that accepts one or more values. If you’re using Dynamic Ads, the item ID must be added for every item present on the page and must match the IDs of items in your catalog.

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your view search results page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "viewSearchResults"
});
</script>

View Content

The following parameters are included when selecting ‘View Content’ as your event type:

Event – This field will auto-populate and is static

Custom Name – This is an optional field to enter the name of your event. If you don’t populate this field, the event will not have a name.

Content Type – Page content type. For example: “Product”, “LandingPage”, “Article”, “Hotel”, “Flight”, “Destination”. Please note that this value must match the product_group from your product data feed. For other types of inventory use: ‘flight’ for flights, ‘hotel’ for hotels and rooms, ‘destination’ for travel destinations, ‘vehicle’ for autos, ‘home_listing’ for real estate and rental accommodations.

Email or Email Hash – This email can be hashed (md5, Sha1 & Sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

Content ID – The content ID parameter is a freeform field that accepts one or more values. If you’re using Dynamic Ads, the Content ID must be added for every item present on the page and match the IDs of items in your catalog.

View Product Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your view content page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "viewContent",
"contentType": "Product",
"email": "[USER_EMAIL]",
"contentId": "[CONTENT_ID]"
});
</script>

View Article Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your view content page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "viewContent",
"contentType": "viewArticle",
"name": "Health",
"email": "[USER_EMAIL]",
"contentId": "[CONTENT_ID]"
});
</script>

View Category

The following parameters are included when selecting ‘View Category’ as your event type:

Custom Name – This is an optional field to enter the name of your event. If you don’t populate this field, the event will not have a name.

OPTIONAL: Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

OPTIONAL: Item IDs – The item ID parameter is a freeform field that accepts one or more values. If you’re using Dynamic Ads, the item ID must be added for every item present on the page and must match the IDs of items in your catalog.

OPTIONAL: Current Page – The page number of the category page viewed.

Ex:

<!-- LiveConnect Tag -->
<!-- Please implement this tag on your view category page. -->
<script type="text/javascript">
window.liQ = window.liQ || [];
window.liQ.push({
"event": "viewCategory"
});
</script>

Custom Conversion

The following parameters will automatically populate when selecting ‘Custom Conversion’ as your event type:

Email or Email Hash – This email can be hashed (md5,sha1 & sha256) or a normal user email and sent to us (We will never receive clear text emails) to enhance campaign optimization and audience resolution.

OPTIONAL: Conversion ID – The content ID parameter is a freeform field that accepts one or more values. If you’re using Dynamic Ads, the Content ID must be added for every item present on the page and match the IDs of items in your catalog.

OPTIONAL: Purchase Amount – Total purchase amount (should match the amount you are using to calculate ROAS).

OPTIONAL: Currency – The currency parameter must use a standard 3-letter ISO currency code. Currency Type (for example: USD)

OPTIONAL: Basket Info (Item) – Include all parameters to complete the basket

ID – The ID parameter is a freeform field. If you’re using Dynamic Product Ads, the ID must match the ID in your catalog. Needs to have a consistent case (upper or lower case).

Price – Add a price variable or static price. The price sent ust be a decimal number greater than or equal to zero. It may not include letters, special characters, currency symbols, or commas.

Quantity – Add a quantity variable or static quantity. The quantity sent must be an integer greater than or equal to zero. It may not include letters, special characters, currency symbols or commas.

Currency – The currency parameter must use a standard 3-letter ISO currency code. Currency Type (for example: USD)

 

 

Back to top