Webtrekk Connector Setup Guide

Webtrekk Connector Setup Guide

by Community Manager 2 weeks ago - edited 2 weeks ago by (35 Views)

Leverage Tealium's Webtrekk integration to connect, analyze, and activate user and marketing data across all devices. This article describes how to set up the Webtrekk connector in your Universal Data Hub account.

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Send Pixel

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Track Domain: Required: Defined by Webtrekk (e.g. track.webtrekk.net)
  • Webtrekk Tracking ID: Required: Defined by Webtrekk (e.g. 111111111111111)

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Pixel

Parameters

Parameter Description
Client Time  
Color Depth  
Content ID  
Cookies Activated  
Java Activated  
Javascript Enabled  
Monitor Resolution  
Referrer URL  
Version  
Window Size  
Custom Ever-ID  
Ever-ID  
Referer  
User Agent  
User IP  
E-Commerce Product Parameters
  • Map array and list values to keys to be passed to Webtrekk.
  • All arrays and lists should be of equal length.
  • Single value attributes will be expanded to an array which is the same length as all other arrays, repeating the value.
  • For a list of parameters that can be sent to Webtrekk see: Which parameters can be sent to Webtrekk
Template Variables
  • Provide template variables for message data (see: Template Variables Guide)
  • Name nested template variables with the dot notation (Example: items.name)
  • Nested template variables are typically built from data layer list attributes
Templates
  • Optional: provide templates to be referenced in query parameters (see: Templates Guide)
  • Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}})