Skip to content
Reportkey
AmberData DMP
Third-party audiences in view

AmberData DMP report: segments and licenses

Reportkey reads your AmberData DMP account and shows which third-party audiences the client's advertising relies on: the size and refresh date of each segment, active licenses by ad platform, their cost and their expiry dates.

14 days free · no card required · all integrations
Sign up, sign in to AmberData on the integrations page and choose segments in a project. Your first report in 5 minutes.
  • Size of every segment and the date of its last recount.
  • Active licenses per platform with price and end date.
  • Segments and combined audience split by Yandex and VK Ads.
Sample Reportkey report with ad campaigns
Sample Reportkey report with ad campaigns
AmberData DMPAudience segments, size, and licenses
30+
integrations
5 min
setup
14 days
trial
TL;DR

AmberData DMP integration: sign in to AmberData via OAuth once on the integrations page, choose the segments and licenses in a project, and audience sizes plus license costs and terms for Yandex and VK Ads land in the report next to campaign statistics.

AmberData DMP in an advertising report

AmberData is a third-party data platform, a DMP, offering ready audience segments built on interests, intent and behaviour that agencies push into ad accounts. A segment is bought as a license for a specific platform and term, then used in campaign targeting. Clients rarely see this layer: the report shows spend and conversions but not which audiences the ads relied on or what they cost. Reportkey adds a section on AmberData segments and licenses next to campaign statistics.

Connecting AmberData via OAuth

Access to account data opens with an OAuth sign-in: from the Reportkey integrations page you go to AmberData, approve access, and the connection is saved for every project. If the AmberData account was created through eLama, use the eLama button on the sign-in page. In the client project, choose the relevant segments and licenses; an agency may hold many, and each client should see only theirs.

DMP audience segments: size and freshness

The first block lists segments. For each one you see its name and path in the AmberData taxonomy, the dataset it is built on, its current size and the date that size was last recalculated. The date matters: a segment that has not been recounted for a while can differ a lot from the real audience, which is worth raising before a launch rather than after.

Change versus the previous snapshot shows whether an audience is growing or shrinking. Narrow segments, such as people recently interested in a specific product category, can swing noticeably, and the report is the place to explain that next to campaign reach.

Segment licenses: cost and terms

The second block covers licenses. Each shows the segment, the ad platform it was delivered to, the cost and currency, start and end dates, and license state. A separate counter shows licenses ending soon. This is the most practical part of the section: the planner sees what to renew, and the client sees exactly what was paid for in the period.

Segments for Yandex Direct and VK Ads

The third block groups licenses by platform: how many segments run in Yandex via Audiences and Direct, how many in VK Ads and in Adfox, and their combined audience. The same report can show campaign results: Yandex Direct spend and conversions and VK Ads statistics. For display placements, add Adfox campaigns and Getintent programmatic.

Reading DMP data: audience estimate, not reach

A few caveats are worth sharing with the client up front. Segment size is the DMP’s estimate, not actual campaign reach; the platform matches users its own way and serves ads to only part of the segment. License cost is not ad spend; budgets and results live in the platform reports. And the API returns only current state, so size history builds up from Reportkey snapshots after connection.

Audiences next to advertising results

Third-party segments only make sense alongside campaign outcomes. Post-click behaviour is covered by Yandex Metrica visits and goals. All advertising sources are on the ad platform integrations page.

AI insights and branding are not on every plan. See the search agency demo report and plans with a 14-day free trial on the pricing page.

Metrics

What goes into the AmberData DMP report

These are the metrics that the AmberData DMP integration already brings into Reportkey reports.

Segments
Segment size
Active licenses
License cost
Expiring licenses
What this integration adds to the report
Audience segments, size, and licenses
Pricing

AmberData DMP reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect AmberData DMP to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from AmberData DMP in client reports.

Pain points
  • The client pays for third-party data segments but cannot see in the report which audiences were bought or where they run.
  • A segment license quietly expires and the Yandex Direct campaign keeps running against an empty audience.
  • Licensed segment sizes shift, yet there is nothing to compare with last month because the DMP account only shows the current value.
AmberData DMP
Search agency with display goals

The agency buys AmberData segments for a client and pushes them to Yandex and VK Ads. In the monthly report, a table of audiences used sits next to campaign spend and conversions: size, platform, license cost and end date.

AmberData DMP
Media planner renewing licenses

The license block with days left works as a reminder: a week before expiry you see which segments to renew or replace, and the decision is made before a campaign is left without an audience.

AmberData DMP
Brand marketer overseeing a contractor

The brand wants to know what data it pays for. The report lists segments with their taxonomy path, size and license cost, with no DMP account access and no questions to the agency.

Report preview

How AmberData DMP appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey report with ad campaigns
Sample Reportkey report with ad campaigns
AmberData DMP audiences in a report

Tiles for active licenses, their total cost and licenses ending within 14 days; a segment table with taxonomy path, size, change versus the previous snapshot, platform and license end date.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the AmberData DMP connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the AmberData DMP segments and licenses that should supply audience size and license data to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need to connect AmberData DMP?
An AmberData account. You connect by signing in via OAuth on the Reportkey integrations page; clients who use AmberData through eLama sign in with the eLama button. Then pick the segments and licenses to show the client in the project.
Is segment size the same as campaign reach?
No. Segment size is the DMP's audience estimate as of its last recount. How many of those people actually saw ads is reported by the platform: Yandex Direct or VK Ads count impressions and reach by their own rules and after their own filters.
Is license cost the same as ad spend?
They are different money. A license pays for the right to use a segment on a platform for a term, while campaign spend is charged in the ad account for impressions and clicks. Showing both side by side gives the full cost, but they should not be summed into one unlabelled line.
How often is data refreshed, and where does the size trend come from?
The AmberData API returns each segment's current state with the date its size was last recalculated. The DMP keeps no size history, so Reportkey stores a snapshot whenever it builds a report and the trend grows from the day you connect. The API allows several thousand requests per hour per user, which is plenty for reporting.
Why does the connection ask me to sign in again?
Accounts created through eLama need authorisation confirmed again roughly once a month. When access lapses, the connection shows a re-authentication status on the integrations page and the segments chosen in the project are kept. After a new sign-in the report builds as before.

AmberData DMP report: segments and licenses

Sign up, sign in to AmberData on the integrations page and choose segments in a project. Your first report in 5 minutes.

Start free