> 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/xtremepush.md).

# Xtremepush

Send segments to Xtremepush as user lists, so an audience built in the CDP can be engaged from Xtremepush.

The Xtremepush connector sends your segments to Xtremepush as user lists, so an audience built in mediarithmics can be engaged from your Xtremepush project.

<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="https://docs.mediarithmics.io/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>User account IDs</td></tr><tr><td><strong>Authentication</strong></td><td>Xtremepush App Token, shared with your Account Manager</td></tr></tbody></table>

{% hint style="info" %}
Setting up this connection involves work on the mediarithmics side. Contact your Account Manager to have your Xtremepush App Token registered.
{% endhint %}

## Description

### What is Xtremepush?

Xtremepush is a customer engagement platform. It reaches known customers across channels such as email, SMS, web and mobile push, and in-app messaging. Its API is hosted in two regions, **EU** and **US**.

### What you can do with this connector

* Create an Xtremepush user list from a mediarithmics segment.
* Enrich a user list that already exists in Xtremepush instead of creating a new one.
* Keep the list in step with the segment as users enter and leave it.

### Which identifiers are sent

When you share a segment through this connector, mediarithmics sends:

* **User account IDs**

## Connector setup

### Prerequisites

* Access to your **Xtremepush** dashboard and to the project that will receive the lists.
* The **App Token** of that project.
* The **region** your Xtremepush project is hosted in: EU or US.

### Authentication

The connector authenticates to Xtremepush with the **App Token** of an Xtremepush project. You retrieve it from your Xtremepush dashboard, under **Settings > Integrations > API Integration** of the relevant project.

Share the App Token with your Account Manager **in a secure way**, together with the region of your project. The App Token is registered on the mediarithmics side.

An App Token belongs to one Xtremepush project. To send segments to several projects, share one App Token per project.

### Set up the Xtremepush connector

{% stepper %}
{% step %}
**Retrieve your App Token in Xtremepush.**

Open the relevant project in your Xtremepush dashboard, then go to **Settings > Integrations > API Integration**. Note the endpoint shown with the token: it tells you the region of your project.
{% endstep %}

{% step %}
**Send the App Token to your Account Manager.**

Share it securely, together with the region of your project. The App Token is registered on the mediarithmics side.
{% endstep %}

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

<table data-search="false"><thead><tr><th width="220">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies this feed inside mediarithmics.</td></tr><tr><td><strong>Xtremepush Audience Name</strong> <em>(optional)</em></td><td>The name of the list created in Xtremepush. Left empty, the mediarithmics segment name is used.</td></tr><tr><td><strong>Xtremepush User List ID</strong> <em>(optional)</em></td><td>Fill it in to enrich an existing Xtremepush user list rather than create a new one.</td></tr><tr><td><strong>Identifying Resources</strong></td><td>The identifier to send. Select <strong>USER_ACCOUNT</strong>.</td></tr><tr><td><strong>Xtremepush API url zone</strong></td><td>The region of your Xtremepush project: <strong>EU</strong> or <strong>US</strong>.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in [Send your first-party data to a destination](https://docs.mediarithmics.io/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination/send-your-first-party-data-to-a-destination.md).

## Good to know

* **Volumes are not immediate.** Even after the initial loading completes, users can take from a few hours to a few days to appear in your Xtremepush list.
* **The region must match your project.** Xtremepush gives the App Token together with the endpoint of your project. Choose the **Xtremepush API url zone** that matches that endpoint.
* **Xtremepush is retiring App Tokens.** Xtremepush states in its [External API overview](https://docs.xtremepush.com/docs/external-api-overview) that App Tokens are not available on projects created after its June 2026 release.

## FAQ

#### Do I need my Account Manager to set this up?

Yes. Retrieve the App Token from Xtremepush and share it securely with your Account Manager, who has it registered on the mediarithmics side.

#### Can I send a segment to a list that already exists in Xtremepush?

Yes. Enter the list's ID in **Xtremepush User List ID** and the segment enriches that list instead of creating a new one.

#### What name does the list get in Xtremepush?

The value of **Xtremepush Audience Name**. Left empty, it falls back to the mediarithmics segment name.

#### Is one App Token enough for all my Xtremepush projects?

No. An App Token belongs to one project. Share one per project you want to send segments to.

## Partner documentation

Xtremepush documents its own platform at <https://docs.xtremepush.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.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>ESP &#x26; marketing automation</strong></td><td>What these platforms need from your CDP, and every mediarithmics connector that reaches one.</td><td><a href="https://docs.mediarithmics.io/connectors/partner-types/esp-and-marketing-automation.md">ESP &amp; marketing automation</a></td></tr><tr><td><strong>Getting started</strong></td><td>Every documented connector, by partner type and by name.</td><td><a href="https://docs.mediarithmics.io/connectors/readme.md">Getting started</a></td></tr></tbody></table>


---

# 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/xtremepush.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.
