Skip to main content

Rokt Tracking ID

As an alternative to integrating customer email or phone number as an identifier, you can use Rokt Tracking ID as an identifier for conversion attribution. For each accepted offer, Rokt generates a unique Rokt Tracking ID that you can use as a dynamic field in the destination URL (UTM parameter). Your attribution system should maintain the Rokt Tracking ID so that you can return it to Rokt when the customer converts. We support Rokt Tracking ID as part of SDK or Event API integrations.

note

View our guide on setting up the Rokt Tracking ID in Google Tag Manager.

Enabling the Rokt Tracking ID#

You need to work with your attribution system to set up the Rokt Tracking ID.

  1. Provide Rokt with a destination URL that contains a field for Rokt to populate with the Rokt Tracking ID. Most attribution providers support this functionality.
  • Example: http://www.tracker.com/?clientid=12345&trackingid={rokt tracking id}
  • Note: These URLs differ based on the measurement system in use. Rokt has prebuilt integrations with several providers.
  1. When a customer opts in to a Rokt offer and lands on your site, the Rokt Tracking ID must be maintained for as long as possible, or until conversion.
  • Note: The exact method for storing this ID (first-party cookie, local storage, etc.) depends on the measurement system in use.
  1. When the customer converts, include the Rokt Tracking ID as part of the reporting data. The attribute name for the tracking ID should be passbackconversiontrackingid. If you need to provide a different attribute name, work with your account manager.
  • When using the Event API, add this attribute to the body of the API call.
  • When using the Wed SDK, add this attribute along with any other attributes that are part of your Rokt integration.

Flow diagram#

Event/App Install Conversion Tracking

The Rokt operations team will work with you throughout this process to ensure the flow is set up correctly

Was this article helpful?