Knowledge Base

Tealium In-App Implementation Instructions

Tealium In-App Implementation Instructions

This guide walks you through how to configure LiveIntent in your Tealium iQ account for in-app tracking. Once you configure your events, you will need to get any relevant conversion pixels from your LiveIntent account team. They can also set up audiences for you. Then, once you’ve implemented your pixels and LiveIntent has set up your audience segmentation, your account team will set up your campaign in our platform. Once these steps are completed, you can go live. 

Step 1: Tag Configuration

First, go to the Tealium Tag Marketplace and add the LiveIntent In-App tag to your profile.

After adding the tag, you’ll need to enter your App ID, which you get from your LiveIntent account team. 

Step 2: Load Rules

Load Rules will determine when and where to load a tag. The default Load Rule is “All Pages.” LiveIntent recommends that you do not change this and leave the Load Rule as All Pages. 

Step 3: Data Mappings

Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, check out Tealium’s page on data mappings.

You can find the destination variables for the LiveIntent tag in the Data Mapping tab. There are two main types of mappings -- standard mappings and event mappings -- as well as e-commerce mappings. All three types are outlined below, including the handful of required mappings for LiveIntent. 

Standard Mappings

DESTINATION NAME

DESCRIPTION

App ID (aid)

Map to this destination to override or dynamically set the App ID

App-specific User ID (app_uid)

The app specific user ID/customer ID

Apple Ad Id (idfa)

The customers apple device id- used for dynamic audiences and attribution (REQUIRED)

Android (aaid)

The customers android device id– used for dynamic audiences and attribution (REQUIRED)

Application Bundle ID (abid)

The users application Bundle ID

Email/Hashed User Email (e)

The customer's email address or email address as an MD5 hashed string (HIGHLY RECOMMENDED)

Event Name

(name)

Used to:

  • Give the type of conversion a name for the conversion event (REQUIRED)
  • Pass product name for a viewContent event
  • Pass the category name for a viewContent event
  • For the addToCart and viewContent events, if a name is not mapped then the E-Commerce List of Product Names is used by default.
  • For a viewCategory event, if a name is not mapped then the E-Commerce List of Product Categories is used by default.

Event Type (events_queue) [Array]

 

Content Type (content_type)

Content Type – LiveIntent supports the following content Types as a string value: "LandingPage", "Article",

   "Product", "Hotel", "Flight", "Destination"

Page Counter (page_counter)

The customer's email address in plain text

 Required Standard Data Mappings for LiveIntent:

  • Apple Ad Id (idfa)
  • Android (aaid)
  • Email/Hashed User Email (e)

 Event Mappings

Map to these destinations for triggering specific events on a page. To trigger an event:

  1. Select an event from the drop-down list.
  2. In the Trigger field, enter the value of the variable being mapped.
  3. To map more events, click the + button and repeat steps 1 and 2.
  4. Click Apply.

The event will trigger when the supplied value is found in the data layer.

DESTINATION NAME

DESCRIPTION

View Content

(content_view)

A view of any content page which requires tracking

View Category 

(category_view)

A view of a category page

View Search Results

(search)

A view of a search results page

conversion

  • A conversion tracking event will occur automatically if an order ID is mapped.
  • An additional name field is required for ALL conversion events if used for tracking on the liveintent platform.

Add Product to Cart

(cart_add)

Customer has added one or more items to the cart

Remove Product from Cart

(cart_remove)

Customer has removed one or more items from the cart

E-Commerce Mappings

Since the LiveIntent tag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manual mapping in this category is generally not needed unless:

  • You want to override any extension mappings
  • Your desired e-commerce variable is not offered in the extension

DESTINATION NAME

DESCRIPTION

Order ID (order_id)

Unique identifier for this order. Use this to override the default e-commerce value _corder.

Order Total

(order_total)

The total revenue for this order. Make sure to pass back the same value you currently use to measure Return on Ad Spend (ROAS). Use this to override the default e-commerce value _ctotal. 

Order Currency

(order_currency)

Use this to override the default e-commerce value _ccurrency.

List of Product IDs

(product_id)

The product ID for each line item. Use this to override the default e-commerce value _cprod.

List of Names (_cprodname)

Names of the product for each item. Use this to override the default e-commerce value _cprodname.

List of categories

(product_quantity)

Categories of page selected. Use this to override the default e-commerce value _ccat.

List of Quantities

(product_quantity)

Quantity of product for each line item. Use this to override the default e-commerce value _cquan.

List of Prices

(product_unit_price)

The price of each item at point of sale. Use this to override the default e-commerce value _cprice.

 

Step 4: Configure Conversion Trackers

App Install

There are no additional mappings required! A conversion tracking event will occur automatically for app installation events.

Other conversion events two separate data mappings:

  • Category: Event mapping
  • Category: Standard mapping
  1. Add your event as a data layer variable (if it doesn’t exist already). Enter the name of the variable exactly as it appears in your site's source code. Only letters, numbers, underscores, dollar signs, array brackets, periods are allowed.
    1. For instance, if you are looking to track event ‘product purchase’ make sure that you have a data variable that is set to trigger from your data layer e.g. confirmation.
  2. Navigate to your LiveIntent In-App tag and update your data mappings
  3. Choose your data layer variable (e.g. confirmation).
  4. Set your data layer variable to trigger an event ‘conversion.’ (Unless you are tracking conversions, plan to pass an Order ID to LiveIntent, and have your e-commerce extension configured. Then you can disregard this step.)
  5. Set your data layer variable to trigger standard event ‘event name.’
  6. Alternatively, you may create a standard data extension (set value as the type) and map your data layer events with popular LiveIntent conversion event names.
    1. Navigate to Extensions
    2. Select ‘set value’ under the ‘Standard Data’ tab
    3. Choose your data layer variable
    4. Set the text to one of the following popular LiveIntent events:
      1. product_purchase – as in a product purchase confirmation
      2. start_trial 
      3. subscription
      4. add_to_wishlist
      5. complete registration
      6. form_fill
      7. lead

Next Steps

Once completed, confirm your variables with your Customer Success Manager so they can check your tag activity and set up your conversion tracker in the LiveIntent platform accordingly.

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