Bring Your Demand

If you run your own Google Ad Manager network, BRNDTS can serve that demand on your BRNDTS placements while keeping full analytics on every fill. Here is how it works and what BRNDTS needs from you to set it up.

What this is

BRNDTS ships with a fully managed demand stack. If you already have your own Google Ad Manager network, BRNDTS can serve your demand instead of, or alongside, its own.

BRNDTS does this by calling your GAM network directly, on a dedicated ad unit you create for BRNDTS inventory. Your network runs its auction and returns the winning creative; BRNDTS renders it in the placement and records its own impression, viewability, and click analytics on every fill.

How it works

Every fill follows the same path, from placement to render.

Placement detected

The SDK reaches an AI-identified moment in the video and opens an ad slot.
BRNDTS calls your GAM unit

The SDK requests your dedicated ad unit directly (GPT), sized to the placement.
Your network runs its auction

Your demand competes inside your network as it normally does. The highest-value ad wins.
Creative renders in the placement

BRNDTS renders the winning creative in the video scene and records impression, viewability, and click analytics - regardless of which demand filled.

What we need from you

Share these with your BRNDTS contact to set up the integration.

What	Value	Note
GAM network code	e.g. `12345678`	Your GAM network
Dedicated ad unit	Full path, e.g. `/12345678/YourSite/BRNDTS`	One ad unit for BRNDTS inventory, so demand and reporting are cleanly scoped to us
Ad unit sizes	The BRNDTS-supported sizes	The unit must accept the sizes BRNDTS serves - see Ad sizing
Demand on the unit	Your live demand	Confirm the unit is targeted by your real demand, not gated to house or affiliate-only line items
Seller authorization	Your `ads.txt` sellers	The page domain must authorize the demand partners serving on this unit
Reporting access	GAM read access, or a scheduled report scoped to the unit	So BRNDTS can reconcile GAM-native numbers - see Reporting

Configure the ad unit to accept the sizes BRNDTS serves - the full list is under Ad sizing. A superset (for example your full display size list) is fine; BRNDTS only requests the sizes valid for a given placement, and any supported size the unit does not accept will not fill from your demand.

Reporting

Because your network serves the winning ad, the authoritative GAM numbers - revenue, eCPM, clicks - live in your GAM console, not the BRNDTS one. Give BRNDTS either read access to reporting, or a scheduled report scoped to the dedicated ad unit, covering:

Ad requests
Fill rate
Impressions
Unfilled impressions
Viewable impressions
Unviewable impressions
% viewable impressions (Active View)
Clicks
CTR
Revenue
eCPM

Broken down by day, ad size, and demand channel or advertiser - so BRNDTS can attribute which source filled and reconcile revenue against its own delivery.

BRNDTS independently records impressions, viewability, and clicks on every fill in its own dashboards, so you still get BRNDTS-side reporting without any access. The GAM report is what reconciles revenue and gives you Google's Active View viewability figure alongside it.

Other demand sources

This guide covers Google Ad Manager, the most common case. If your demand lives elsewhere - a different ad server, your own header-bidding setup, or direct SSP integrations - BRNDTS can usually accommodate it too. Raise it with your BRNDTS contact and we will work out the best way to connect it.