---
url: https://docs.dataflair.ai/marketplace/ad-server-paths.md
description: >-
  Four ways to serve Marketplace campaigns on your websites and apps. Ad tags
  only, Google Ad Manager, Revive Adserver or your own ad server.
---

# Choosing your ad server path

There are four ways to serve Marketplace campaigns on your websites and apps. Social bookings are not served by an ad server. You post the content yourself.

You choose **one path per organization** in **Settings → Ad server**. You can switch later.

## Path 1. No ad server: paste our ad tag

You do not need an ad server at all. Every approved campaign gives you one tag. Paste it once where the ad should appear and you are serving. The tag keeps itself up to date, so a creative change does not need a new paste.

Delivery is reported monthly from your dashboard, with a screenshot or an analytics export attached as evidence.

This suits you if you sell direct and do not run ad-serving infrastructure.

**See:** [Ad tags and tracking](/marketplace/ad-tags/)

## Path 2. Google Ad Manager

Enter your **network code** and grant access inside GAM. You do not type any credentials. Once connected:

* Delivery numbers import automatically, ready for one-click confirmation.
* Campaigns arrive in GAM as **draft orders that your ad-ops team activates**.
* DataFlair does not serve ads, does not activate anything and does not change your targeting.

**See:** [Google Ad Manager](/marketplace/google-ad-manager/)

## Path 3. Revive Adserver

Connect your self-hosted or managed Revive instance with its address and a dedicated login you create for DataFlair. Campaigns arrive as inactive campaigns and banners for you to activate in Revive. Delivery imports for one-click confirmation.

Revive has no forecasting. Availability is not pre-checked when an advertiser books.

**See:** [Revive Adserver](/marketplace/revive/)

## Path 4. Your own ad server

If you run in-house ad serving, your engineers implement DataFlair's small integration API. You connect it with an address and a key you issue. From there it works like the other connected paths: availability checks, draft bookings your team activates, and automatic delivery reporting.

**See:** [Ad Server API](/marketplace/ad-server-api/overview). The overview says which calls are live today.

## Side by side

| Path | You provide | Availability | Monthly delivery |
| --- | --- | --- | --- |
| **Ad tags only** | Nothing: paste one tag per placement | Your listed numbers | Manual report and evidence |
| **Google Ad Manager** | Network code and an access grant | Live forecast | Imported, one-click confirm |
| **Revive Adserver** | Address and an API user | Your listed numbers | Imported, one-click confirm |
| **Your own ad server** | A small API and a key you issue | Live forecast | Imported |

## Switching later

An organization has one ad server. Switching disconnects the current provider first. Then you connect the new one. Your choice here only changes how ads get served and how delivery numbers reach DataFlair. Booking, payments, creative review and settlement are identical on every path.