> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/equativ.md).

# Equativ

Send audiences to Equativ for its curation platform and its SSP/adserver.

The Equativ connector sends your audiences to Equativ, for use in two products: **EBC** (Equativ Buyer Connect, the curation platform) and the **SSP / adserver**.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &#x26; ad servers</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Cookies, MAIDs, Account IDs, ID5 IDs, IP addresses</td></tr><tr><td><strong>Authentication</strong></td><td>Credentials from your account manager, plus rights granted in Equativ</td></tr></tbody></table>

## Description

### What is Equativ?

Equativ, formerly SmartAdServer, operates an SSP and ad server, and a curation platform called Equativ Buyer Connect. This connector serves both.

### What you can do with this connector

* Make a mediarithmics segment available for curation in Equativ Buyer Connect.
* Target the same audience through the Equativ SSP and ad server.
* Send an audience into an Equativ segment that already exists, instead of creating a new one.

### Which identifiers are sent

* **Cookies**
* **MAIDs**
* **Account IDs**
* **ID5 IDs**
* **IP addresses**

## Connector setup

### Prerequisites

* Give your mediarithmics account manager your **Segment Provider ID**.
* Ask Equativ for two rights on your account:
  * segment creation;
  * segment listing, and adding new users to a segment.

{% hint style="warning" %}
If you intend to send **cookies**, cookie matching must be activated on your organisation. Contact your account manager to confirm.
{% endhint %}

### Authentication

Your account manager returns a **Credentials Name** after you supply the Segment Provider ID. That is what the feed references.

### Setup steps

{% stepper %}
{% step %}
**Send your Segment Provider ID to your mediarithmics account manager.**
{% endstep %}

{% step %}
**Ask Equativ to grant the segment creation and segment listing rights.**
{% endstep %}

{% step %}
**Select the Equativ connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="260">Field</th><th></th></tr></thead><tbody><tr><td><strong>Credentials Name</strong></td><td>The value your account manager gave you.</td></tr><tr><td><strong>Equativ ID</strong></td><td>Fill in only to send the segment to an existing Equativ segment.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

{% hint style="warning" %}
Following CNIL guidance on cookies and trackers, make sure that:

1. the partner is correctly named when you collect user consent for targeting purposes, or the equivalent;
2. the partner is named in your cookie policy - these partners may drop a cookie on your users' browsers from your websites.
   {% endhint %}

## FAQ

#### How do I set up Utiq on the Equativ side before sending that identifier?

Creating a connector with Equativ on a **new identifier basis** requires a **new seat** on the Equativ side - one seat per identifier. Ask your Equativ account manager to create it. This applies to Utiq specifically; disregard it for other identifiers.

#### Can I feed an Equativ segment that already exists?

Yes. Fill in the **Equativ ID** field with that segment.

## Partner documentation

Equativ documents its own platform at <https://help.equativ.com/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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.mediarithmics.io/connectors/destinations/equativ.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.