> 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/attribution-and-affiliate/northbeam.md).

# Northbeam

Northbeam is a marketing attribution and analytics platform that offers multi-touch attribution and media mix modeling. Chord reports to Northbeam from the browser and from the server, so Northbeam can credit each order to the channels that drove it.

## What each version does

* [**Northbeam Pixel**](/activate/event-streaming/destinations/attribution-and-affiliate/northbeam/northbeam-pixel.md) loads Northbeam's JavaScript tag in the shopper's browser. It sends page views, identity and ecommerce events, including custom goals for product views, add to cart and checkout started.
* [**Northbeam server**](/activate/event-streaming/destinations/attribution-and-affiliate/northbeam/northbeam-server.md) runs on Chord's servers and sends orders and refunds to Northbeam's Orders API. In the destination catalog in Chord, you add it as **Northbeam**.

## Why use both

The browser version catches on-page behavior, such as page views and the steps before checkout. The server version survives ad blockers and closed tabs. It is also the only version that reports refunds. The browser version skips `Order Refunded` events.

## How they deduplicate

Both versions send purchases to Northbeam. Northbeam deduplicates purchases by order ID, so running both should not double-count orders.

{% hint style="warning" %}
The two versions read the order ID differently. The browser version uses `cart_id` when an `Order Completed` event carries both a cart ID and an order ID. The server version uses only `order_id`. In that case the two versions send different IDs for the same order.
{% endhint %}

## Set up

* [Northbeam Pixel](/activate/event-streaming/destinations/attribution-and-affiliate/northbeam/northbeam-pixel.md)
* [Northbeam server](/activate/event-streaming/destinations/attribution-and-affiliate/northbeam/northbeam-server.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/attribution-and-affiliate/northbeam.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.