---
url: https://docs.dataflair.ai/marketplace/revive.md
description: >-
  Connect a self-hosted or managed Revive Adserver instance to DataFlair
  Marketplace with its base URL and a dedicated API user.
---

# Connect your Revive Adserver to DataFlair

This is a short guide for publishers who run [Revive Adserver](https://www.revive-adserver.com/), self-hosted or on a managed hosted plan (for example [revive-adserver.net](https://www.revive-adserver.net/), or a third-party host of the same open-source software). Unlike Google Ad Manager, there is no shared DataFlair account here. Each publisher connects their own Revive instance with their own API credentials.

## What you need

* Your Revive instance's **base URL**. It must start with `https://`.
* An **API user** on that instance: a username and password with API access. Revive does not support scoped or read-only API keys. Use a dedicated user, not a personal admin login, if you want to be able to revoke access on its own later.

If you are on a managed hosted plan, confirm two things with your hosting provider before you connect:

* That XML-RPC API access is included on your plan. It is not guaranteed on every tier.
* The correct host to use as your `base_url`. Some hosted setups split the admin console and ad delivery onto separate domains, and the API lives on the admin or console domain.

## Connect

1. In DataFlair Marketplace, go to **Settings → Ad server** and choose **Revive Adserver**.
2. Enter your instance's base URL and your API user's username and password.
3. Click **Connect & verify**. DataFlair runs a read-only check. It looks up your agency and publisher records to confirm the credentials work. Nothing is created or changed in your Revive instance at this step.

Once connected, an admin on the DataFlair side maps your ad slots (Zones) to Marketplace placements before any campaign can traffic to them.

## What DataFlair does and does not do

* **DataFlair creates campaigns and banners as inactive, unlinked objects first.** When an advertiser's reservation is approved, DataFlair creates the campaign and banner records in your Revive instance. It leaves them inactive and not linked to a zone. Nothing serves yet.
* **DataFlair does not activate or link a banner.** Go-live happens entirely outside DataFlair, inside your own Revive admin panel, by your own ad-ops person. DataFlair has no code path that can activate a Revive banner. Once a banner is created, it is up to you to link it to a zone and switch it on.
* **DataFlair touches only what it created.** It manages only the campaigns and banners it created through this integration. It does not create or change a zone link at all. That is entirely your Revive admin's responsibility.
* **DataFlair stores only your API credentials and the data your instance returns.** Your username and password are stored encrypted, and they are not displayed back to you after you save them.

## Troubleshooting

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| "Authentication failed" on connect | Wrong username or password | Re-check your API user's credentials |
| "Unreachable" on connect | Wrong base URL, the instance is down, or the URL does not start with `https://` | Confirm the URL is reachable in a browser and starts with `https://` |
| "No agency access" on connect | The API user has no agency assigned | Give the API user access to at least one agency in Revive's admin |
| A booked cell is not trafficking | The placement is not mapped to a Zone yet, or there is no approved creative for that booking | Ask your DataFlair contact to confirm the zone mapping, and check that a creative has been approved |
| A banner was created but is not serving | It has been trafficked but not yet linked to a zone | This is expected. Link and activate the banner inside your own Revive admin panel |