Skip to main content

Rokt Event API for Tealium

API Information#

This connector uses the following API:

API information
API NameRokt API
API Version2020-05-21
API Endpoint
DocumentationROKT Event API

Batch Limits#

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three thresholds is met:

Request parameterThreshold
Max number of requests100
Max time since oldest request10 minutes
Max size of requests1 MB

Connector Actions#

Send Conversion

Adding the connection to Rokt#

  1. Log in to Tealium Customer Data Hub and click Event Stream > Event Connectors.
  2. Click Add Connector. Tealium_add_event_connector
  3. Search for and select the Rokt connector. Tealium_marketplace_rokt
  4. Click Continue. Tealium_events_continue
  5. The Data Source and Event Feed are automatically selected for you. Click Continue.
  6. Click Add Connector.
  7. Completee the following:
    • Name: Give the commector a name.
    • Notes: Make any notes as needed.
    • Client ID: Enter your App ID. Click for information on how to Generate your App ID and Secret.
    • Client Secret: Enter your App Secret.
    • Account ID - Enter the Rokt Account ID provided by your account manager.
  8. Click Done.
  9. Click Continue.
  10. Enter a name for the action and then select the action type from the drop-down menu.

Action — Send Conversion#

Event Type(Required) Type of event.
Event IDAn identifier used to uniquely identify an event.
Event TimeTime of the event in UTC.
EmailEmail passed as plain text, lowercase and without trailing spaces.
Email - emailsha256 (already SHA256 hashed)SHA-256 hash of email address, already hashed.
Email - emailsha256 (apply SHA256 hash)SHA-256 hash of email address. Tealium will hash.
Rokt Tracking IDA Rokt-generated ID used to match conversion events to the originating click.
Conversion AmountTransaction amount.
Currency CodeCurrency code.
QuantityThe quantity (integer) of item within the specific conversion.
Conversion TypeUsed to differentiate between different conversion events.
Product NamesThe name of the product(s) purchased.
Product SKUsThe identifier of the product purchased (Note: Only accepts one SKU).
Payment TypeThe payment method used during the transaction.
Credit Сard BINCredit card BIN of converting payment.
MarginProfit margin of conversion.
Transaction IDTransaction ID, used to identify a unique transaction.
Confirmation Reference IDConfirmation reference ID.
Customer First NameCustomer's first name.
Customer First Name (already SHA256 hashed)SHA-256 hash of first name, already hashed.
Customer First Name (apply SHA256 hash)SHA-256 hash of first name. Tealium to hash.
Customer Last NameCustomer's last name.
Customer Last Name (already SHA256 hashed)SHA-256 hash of last name, already hashed.
Customer Last Name (apply SHA256 hash)SHA-256 hash of last name. Tealium to hash.
Mobile Phone NumberMobile phone number of converting customer.
Mobile Phone Number (already SHA256 hashed)SHA-256 hash of phone number, already hashed.
Mobile Phone Number (apply SHA256 hash)SHA-256 hash of phone number. Tealium to hash.
Customer IP AddressCustomer's IP address.
Customer IP Address (already SHA256 hashed)SHA-256 hash of customer's IP address, already hashed.
Customer IP Address (apply SHA256 hash)SHA-256 hash of customer's IP address. Tealium to hash.
User AgentBrowser user agent of converting customer.
Device TypeType of device.
Device Operating SystemDevice operating system.
OS VersionOperating system version.
Browser VersionBrowser version.
Customer TitleTitle of the customer.
Customer GenderGender of the customer.
Customer Date of BirthIn the format yyyymmdd.
Customer AgeAge of the customer.
LanguageLanguage associated with the purchase.
Unit NumberUnit number associated with address.
Address 1First line of street address.
Address 2Second line of street address.
Customer Postal CodeCustomer postal code.
Customer CityCustomer city.
Customer StateCustomer state.
Customer CountryCustomer country.
Meta DataNon-business critical information about the event.
  1. Complete Conversion Data and Meta Data sections as required. See POST Events for further information.
  2. Click Finish.
  3. Click Save and Publish.
  4. Give your Connector a Title and Description.
  5. Click OK.
Was this article helpful?