> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/rokt.md).

# Rokt

Rokt is an advertising and offer-placement network. Chord sends your conversions and page views to Rokt from the browser and from the server, so Rokt can attribute a purchase or sign-up to the campaign that drove it and build retargeting audiences.

## What each version does

* [**Rokt Pixel**](/activate/event-streaming/destinations/advertising/rokt/rokt-pixel.md) loads Rokt's Web SDK in the shopper's browser. It sets up the browser session Rokt uses for retargeting and captures the Rokt Click ID.
* [**Rokt Events API**](/activate/event-streaming/destinations/advertising/rokt/rokt-events-api.md) runs on Chord's servers. It survives ad blockers and browser tracking limits, and it reports conversions that never touch a browser, such as a subscription renewal or an order placed by support.

## Why use both

The browser version catches on-page behavior and the browser session. The server version survives ad blockers and closed tabs. Running both is supported and is the more reliable setup.

## How they deduplicate

Rokt deduplicates on `confirmationref`. Chord sends the cart ID there when the event has one, and otherwise the order ID. If the event has neither, Chord looks for a `transaction_id` or `transactionId` property. For conversions with none of these, such as a sign-up, Chord sends the event's message ID instead. Both versions derive it the same way, so Rokt sees one conversion.

Use the same Custom Event Mapping on both destinations. It is the one setting where a difference changes what Rokt records.

## Set up

* [Rokt Pixel](/activate/event-streaming/destinations/advertising/rokt/rokt-pixel.md)
* [Rokt Events API](/activate/event-streaming/destinations/advertising/rokt/rokt-events-api.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/destinations/advertising/rokt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.