Skip to main content

Set up attribution with Rokt ID

The Rokt ID can be used for conversion attribution in the event you'd like to track conversions without sharing customer data. Here's how it works:

  1. For each accepted offer, Rokt generates a unique Rokt ID that you'll use as a dynamic field in the destination URL (UTM parameter).
  2. Then, your attribution system maintains the Rokt ID.
  3. Finally, you return the Rokt ID to us when the customer converts. There are several options for returning the Rokt ID, which we've outlined below.

Generate the Rokt ID​

note

Please work with your account manager to complete the following steps.

To generate the unique Rokt ID, please ensure that the destination URL of your creative includes the following as a URL parameter: rtid={rokt.carbon.conversiontrackingid|}. Read more about building creatives.

rokt-id-CTA

In the Destination URL, you will need to add & or ? before rtid={rokt.carbon.conversiontrackingid|}. This is determined by the original traffic link. If the original traffic link contains a ?, add an & before the rtid.

Example: www.landingpage.com/?hello=world&rtid={rokt.carbon.conversiontrackingid|}

If the original traffic link does not contain a ?, add a ? before the rtid

Example: www.landingpage.com/?rtid={rokt.carbon.conversiontrackingid|}

Storing and returning the Rokt ID​

Once you've completed the above steps, a unique ID will be generated that allows conversion events to be tracked. When a customer converts, you'll return this ID back to Rokt for attribution. There are several methods to store and return this ID, which we've detailed below. Please reach out to your account manager if you have any questions.

Store and return the Rokt ID via the landing page tag​

You can use the landing page tag to store the Rokt ID so that you can return it to Rokt when a customer converts. Once you've added the Rokt ID on your landing page:

  1. Add the Rokt landing page tag (referral.js) on your landing page, listed below:

<script src="https://apps.rokt.com/integrations/referral-tag/referral-tag.js" async></script>

If you require assistance to add this tag to your landing page, please reach out to your account manager. The referral tag will automatically store the Rokt ID locally in your user's browser.

note

If you've decided to integrate the Rokt ID Tag with the Rokt Web SDK, please ensure that the landing and confirmation page have the same domain.

For example, if your landing page is mysite.com, your confirmation page should also be mysite.com/.... If your confirmation page is on a different subdomain, such as checkout.mysite.com, the integration will not function.

If the URL of your user conversion flow is dynamic, please reach out to your account manager before you add the Rokt landing page tag.

  1. Add the Rokt Web SDK on your conversion page. The Web SDK will automatically capture the Rokt ID from local storage and integrate during a conversion event. There are several options to integrate the Rokt Web SDK onto your conversion page, including through Google Tag Manager, Tealium, or installing the SDK directly on your landing page.

Store and return the Rokt ID via a custom solution​

If you have a method to store the Rokt ID so that you can return it to Rokt when the customer converts, you can simply integrate that storage method with either the Rokt Web SDK or Event API.

To return the Rokt ID, please add the Rokt Web SDK on your conversion page. The Web SDK will automatically capture the Rokt ID from local storage and integrate during a conversion event. There are several options to integrate the Rokt Web SDK onto your conversion page, including through Google Tag Manager, Tealium, or installing the SDK directly on your landing page.

Alternatively, you can also use the Event API to return the Rokt ID. For more information, please talk to your account manager.

Store and return the Rokt ID via a third-party measurement provider​

If you'd prefer to use a third-party management provider to integrate the Rokt ID for conversion attribution, please see our documentation here.