Overview

Rokt is an ad platform that partners with e-commerce sites to show ads on their post-checkout pages. With the Rokt integration, Everflow sends each conversion straight to Rokt's Events API from our servers. The advertiser does not need to place a Rokt pixel, and Everflow hashes the customer's personal details before they leave.

You set it up in two parts. First you add your Rokt API key and secret once, as an integration. Then you create a postback with Rokt as the Delivery Method and choose which fields to send.

How It Works

Here is what happens between a click on a Rokt ad and a conversion reaching Rokt:

The more customer fields you send, the better Rokt can match. Rokt asks for an email at minimum, and recommends name, mobile number and postal code when you have them.

Before You Start

Make sure you have the following:

Add the Rokt Click ID to Your Tracking Link

Rokt fills in its click ID through the {rokt.rclid|} macro. Add it to the Everflow tracking link you give Rokt, in a sub parameter you are not already using. Use & before it if the link already has a ?, otherwise use ?. This example uses sub2:

https://www.YOUR-TRACKING-DOMAIN.com/ABC123/DEF456/?sub2={rokt.rclid|}

Later, in the postback, you map the same sub parameter (here {sub2}) to the Rokt Click Id field. Any free sub parameter works, as long as the tracking link and the postback use the same one.

Rokt's own docs show the click ID as rtid={rokt.rclid|}. That parameter name is for Rokt's pixel. With Everflow, use a sub parameter instead so the click ID is saved on the click.

Pass the Customer's Email

The email works the same way as in other server-side integrations: it has to arrive with the conversion. When the advertiser sends the customer's email on the conversion, you map {email} to the User Email field in Step 2, and Everflow hashes it before it leaves.

If the advertiser sends the email in an advertiser parameter instead, such as adv1, map that parameter ({adv1}) to User Email. Advertiser parameters are hidden from partners by default, so turn on Macro Parameters Visibility for the Rokt partner first. See Managing Offer Visibility and Partner Access for how.

Step-by-Step Setup

Step 1: Add the Rokt Integration

The integration belongs to a partner, so you add it in the Partner Platform. You need a Rokt partner with at least one user first. As a network user, create the partner, add a user, then log in as that user by impersonating them. Media buyers running their own Rokt traffic follow the same steps.

Rokt now shows under Connected, and its button changes to View. Add one integration per Rokt account for each partner. A postback can only use an integration that belongs to its own partner.

Manage Your Rokt Integrations

Select View on the Rokt card to open Manage Rokt Integration. From there:

With Api Credentials set to Yes, the key and secret fields open again for new values:

Network users can also see every partner's Rokt integration in the Core Platform under Integrations → Media Buying → Rokt. The Manage page lists each partner, its Rokt integration and the event types it sends.

Step 2: Create the Rokt Postback

Next, create the postback in the Core Platform. Partners can also create it themselves in the Partner Platform, under Postbacks with + Postback.

Use a different Conversion Type for each postback, such as lead for the conversion and booking for an event. Rokt receives every postback as the same kind of event, so Conversion Type is the only thing that tells them apart.

Here is a finished Rokt postback with the email, click ID and customer ID mapped:

If the email is empty on a single conversion, Everflow leaves it out of that event and still sends the rest. Rokt is not available at the Global (Offer) level, so choose Global or Specific.

Step 3: Send Extra Data (Optional)

Select the + next to Rokt User Data or Rokt Custom Data to add more fields. Every field is optional and accepts macros. Pick the field in Data Field, then enter its Value. A blank field is left out of the event.

Rokt User Data

Fields with a HASHED badge are hashed by Everflow before they are sent.

Here is how Everflow sends each one:

Rokt Custom Data

These describe the conversion itself.

Rokt's own documentation lists Confirmation Ref as a required attribute, even though the Everflow form treats it as optional. Based on that recommendation, we suggest adding it to every Rokt postback.

An Event postback set to Specific needs an offer with at least one public event. If the offer has none, the form shows a warning and you cannot pick an event.

Step 4: Test the Postback

Before you go live, ask your Rokt account manager to set up testing on their side. Then fire a test and check both ends.

A Success status means Everflow delivered the event to Rokt. It does not mean Rokt matched the customer, which only Rokt can confirm.

How Everflow Handles Personal Data

Everflow hashes the email, first name, last name and mobile number with SHA-256 before they leave. A hash is a scrambled version of a value that Rokt can match but nobody can read. Everything else is sent as you entered it.

Two mistakes stop Rokt from matching the customer without causing any error. The postback still shows Success, because Everflow did deliver it.

The second one is about phone numbers.

What Everflow Sends Automatically

You do not need to map these:

For customers in the UK and EU, the IP address is hashed for privacy. Rokt does not need the IP address to match a conversion.

Conversions That Happen Offline

Conversions that happen off the web, such as a booking made by phone, can still reach Rokt. The advertiser sends Everflow the original transaction ID in a server postback when the booking happens, and Everflow fires the Rokt postback for the matching click. See Email Address Attribution if the advertiser only has the customer's email.

Quick Reference

The whole setup at a glance:

Troubleshooting

Select a problem to see what to check.

Limitations

Rokt works with Conversion and Event postbacks at the Global and Specific levels. It is not available for CPC postbacks, where the Delivery Method is always Postback, or at the Global (Offer) level. Everflow can confirm that it delivered an event to Rokt, but only Rokt can confirm that it matched the customer.

Keep reading: