Rokt

Datafly Signal delivers conversions to Rokt server-to-server using the Rokt Conversions API. This gives Rokt Ads reliable, closed-loop attribution that is not affected by ad blockers or browser tracking prevention.

Prerequisites

Before configuring Rokt in Signal, you need an active Rokt Ads advertiser account and an API key pair.

Step 1: Get your Rokt Account ID

Your Account ID identifies your advertiser account on every Conversions API request. If you don’t know it, ask your Rokt account manager.

Step 2: Request an API key and secret

The Conversions API uses HTTP Basic authentication with a key pair issued by Rokt:

1. Contact your Rokt account manager and request API credentials for the Conversions API.
2. Rokt provides a public key (begins with rpub-) and a secret key (begins with rsec-).
3. Store both securely. The secret key is shown to you by Rokt and is used as the Basic-auth password.

Step 3: Capture the Rokt Click ID (recommended)

Rokt attributes a conversion to a click most accurately when you pass the Rokt Click ID (rclid). When a visitor arrives from a Rokt placement, Rokt appends rclid to the landing-page URL. Signal captures this automatically and forwards it on every conversion, so no manual work is required as long as your landing pages preserve query parameters.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://api.rokt.com/v1/conversions

Authentication is HTTP Basic: Authorization: Basic base64(rpub-…:rsec-…). Conversions are sent as a JSON object with an accountId and an events array. Signal batches multiple conversions into a single request.

Identity Signals

Rokt matches each conversion to a click using one or more identifiers. The more you provide, the higher the match rate. Signal supplies these automatically where the data is available.

How to Send User Data

Call datafly.identify() when a user logs in, registers, or completes checkout:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  phone: "+44 7700 900123"
});

Signal normalises and hashes these fields automatically before sending to Rokt.

Event Mapping

Default preset

Retail preset

All other events are dropped. To customise, edit the integration’s Field Mappings in the Management UI.

Example: Purchase Event

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-789012",
  revenue: 99.99,
  currency: "USD"
});

Rokt Conversions API payload sent by Signal:

{
  "accountId": "12345",
  "events": [
    {
      "conversionType": "purchase",
      "conversionId": "ORD-789012",
      "eventTime": "2026-06-06T10:00:00Z",
      "confirmationRef": "ORD-789012",
      "value": 99.99,
      "currency": "USD",
      "rclid": "550e8400e29b41d4a716446655440001",
      "emailsha256": "d8a928b2043db77e340b523547bf16cb4aa483f0645fe0a290ed1f20aab76257",
      "ipAddress": "203.0.113.50",
      "userAgent": "Mozilla/5.0 ..."
    }
  ]
}

Testing Your Integration

Deduplication

If you run Rokt’s client-side conversion tag and Signal server-side delivery during a migration, deduplicate to avoid double-counting. Rokt deduplicates conversions that share the same conversionType and confirmationRef, so send identical values for both across the two integrations. Signal maps confirmationRef from your order_id by default, giving you a stable dedup key.

Troubleshooting