This document describes how to send data to the Customer Data Hub using the HTTP API for events. This article provides the specification for the direct HTTP endpoint, which can be used in any application that can send HTTP requests.

In this article:

Table of Contents Placeholder

Request Format

Tealium Collect is an HTTP endpoint that supports GET and POST methods.

Root URL

Tealium Collect is located at the following root URL:

https://collect.tealiumiq.com/event

Standard Parameters

Tealium Collect supports the following standard parameters in each request:

Custom Event Parameters

Visitor Identifiers

If you are using AudienceStream you must pass a known visitor identifier attribute (secondary ID) with each tracking call (e.g. email_address or login_id). If the events do not contain a visitor identifier each event will generate a new visit and visitor and stitching will not be possible. This is especially important if using the Collect API on a web platform where you might be tracking anonymous users.

A visitor identifier is also needed if you are using EventStream and need to provide an ID to a vendor connector.

Primary Visitor ID

The tealium_visitor_id attribute is an anonymous identifier used by AudienceStream to associate a visitor between events and visits. Depending on your usage of the Collect API, you can use one of the following approaches:

Known Visitors (Recommended)When tracking events for a known visitor (when a value exists for a Visitor ID attribute such as email_address), include a concatenation of the accout, profile and the known visitor ID attribute ID and value, and a hash of that concatentated value in the tealium_visitor_id parameter.

Anonymous VisitorsWhen tracking events for an anonymous visitor from a website (without a known identifier), then the value of the tealium_visitor_id will need to match the value in the utag_main_v_id cookie. (Learn more about the built-in variables from utag.js.)

AudienceStream

EventStream

Required

N/A

POST Method

The POST method supports JSON payloads where the request header must be set to Content-Type: application/json and the payload must be formatted as a valid JSON string.

JavaScript

Tealium Collect supports cross-domain requests, so you can send a POST from your website to our domain. The Response Headers will include the following: Access-Control-Allow-Origin: http://your_domain.com