Who Owns Your Audiences and Reports in a Managed Amazon DSP Account?

A managed Amazon DSP account can give a brand programmatic access without building an internal trading team. It can also create a quiet dependency. The advertiser may pay for the media and supply the customer data, but still rely on the provider for account access, audience activation, report exports and historical records.

The problem usually appears when someone asks for a new analyst login, a raw cost report or a partner transition. “The client owns the data” sounds reassuring, but it does not explain who can export it, how long it remains available or which assets can move.

Quick answer: Paying for a managed Amazon DSP campaign does not automatically give the advertiser control of every account asset. The contract should separately define source-data rights, audience use, platform permissions, report access, cost visibility, retention and exit support. Require named admins, recurring exports and a tested handover package before launch.

Naming note: Amazon now describes the combined ads console and Amazon DSP buying surface as Amazon Ads Agent. This article uses “Amazon DSP” because it remains the established programmatic product term and the target search language. Confirm the current account structure, user controls and reporting workflow for the advertiser's market and seat.

This is an operational governance guide, not legal advice. Data protection roles, ownership language and regulatory duties depend on the contract, data and jurisdictions. Ask qualified counsel to review final terms.

Amazon DSP data ownership is not one right

Ownership is a bundle of legal and operational rights. A useful agreement separates at least 6 layers.

One sentence saying “all client data belongs to the client” is not enough. It may cover legal title to a CRM file while saying nothing about platform-generated audiences, Amazon Marketing Cloud queries, cost fields or campaign history.

What assets exist in a managed Amazon DSP relationship?

Who owns advertiser first-party data?

The advertiser should retain control of the source data it supplies. The managed provider should receive only the rights needed to perform the agreed service. Put the permitted purpose, environment, market, security controls, retention and deletion process in writing.

For every audience feed, document:

• the source system and business owner;

• the inclusion, exclusion and suppression rules;

• the approved advertising purpose and markets;

• the refresh cadence and expiry window;

• the identifiers and transfer method;

• the provider's permitted actions;

• the deletion and confirmation process;

• the treatment of opt-outs and revoked permissions.

Do not give a provider a general right to reuse client data for another advertiser, internal benchmarking or unrelated product development unless that use is understood, lawful and explicitly approved. Review Amazon's current privacy notice and applicable policy terms alongside the provider agreement.

Who owns audiences created inside Amazon DSP?

Separate 3 audience families.

Advertiser Audiences

These audiences originate from the advertiser's eligible data or events. The advertiser should control the business rules and approved use. Operational access still depends on the account, permissions and onboarding route. Ask whether the segment can remain active, be recreated or be deleted if the provider changes.

Amazon audiences

Amazon audience segments are platform capabilities. Buying access does not turn them into an advertiser-owned customer file. The advertiser can use eligible segments under current platform terms, but should not expect to download the underlying people or signals.

Amazon Marketing Cloud audiences

An AMC audience combines query logic, eligible Amazon signals and, where permitted, advertiser inputs. Governance needs to cover both the logic and the environment. Ask who administers the AMC instance, stores the SQL or template, approves changes, schedules refreshes and links the audience to activation.

Amazon has documented custom audience creation and activation from AMC. That capability does not answer the commercial ownership question between an advertiser and its provider. The contract still needs to define access and continuity.

The Amazon DSP audience strategy guide explains how these audience layers support prospecting, suppression and retention. This article focuses on who controls them.

Can a managed provider keep your audience logic?

The answer depends on what the contract says and how the work was created. A provider may bring pre-existing templates, taxonomies or methods. The advertiser may bring customer rules, product definitions and proprietary segments. Campaign-specific work can combine both.

Use 3 labels in the statement of work:

• Advertiser materials: source data, customer definitions, brand files and business rules supplied by the client.

• Provider background materials: reusable tools, generic templates and methods created before the engagement.

• Engagement outputs: audience maps, queries, exclusion logic, reports and documentation created for the account.

Then state which engagement outputs the advertiser can keep, export or receive in readable form. Avoid discovering at exit that the provider considers every query and taxonomy confidential.

Who controls reports in a managed Amazon DSP account?

A dashboard is a presentation layer. It is not the same as direct account visibility, scheduled platform reports, API access or AMC outputs.

Ask for a sample report before signing. Check whether it includes campaign and line-item names, dates, inventory, device, geography, audience, creative, reach, frequency, conversions and cost fields needed for independent analysis.

Raw data, aggregated data and dashboards are not interchangeable

“Full reporting” can mean a monthly PDF with 10 numbers. Define the level of detail.

• Aggregated dashboard: useful for decisions, but limited for audit and migration.

• Scheduled report: repeatable rows and columns that can be stored outside the provider's dashboard.

• API or data feed: automated access for internal reporting, subject to current permissions and technical support.

• AMC output: privacy-safe aggregate results from approved queries, not a list of identifiable Amazon users.

Amazon has introduced AMC API access and other reporting capabilities over time. Availability does not guarantee that the advertiser receives credentials or provider support. Name the required route in the agreement.

Who can see media cost and fees?

Ownership questions often hide a commercial question: can the advertiser see what entered the auction and what was added as platform, data or service cost?

Require a report and invoice example that separates:

• working media or supply cost;

• platform or technology cost;

• audience and data charges;

• verification and ad-serving costs;

• creative or measurement costs;

• agency management fee or markup;

• tax, currency and payment terms.

The Amazon DSP pricing guide explains the full cost stack. The governance point is simple: the advertiser should know which fields it can inspect, which values appear only on an invoice and who can reconcile them.

Account permissions: visibility is not control

A provider may say the advertiser has access while retaining every administrative right. Ask for a permission matrix by named user, not a general promise.

Amazon has published controls to manage third-party applications with account access. Review connected tools regularly. Remove unused integrations and credentials when staff or vendors change.

The contract checklist before launch

1. Name the account structure. Record the contracting entity, advertiser entity, market and administrator.

2. Define platform access. List each advertiser user, role, visible fields and approval right.

3. Classify every audience. Separate advertiser data, Amazon segments, AMC audiences and provider materials.

4. Limit permitted use. State purpose, market, service, retention and deletion duties.

5. Specify reporting. List required reports, dimensions, metrics, attribution windows, cadence and formats.

6. Expose the cost stack. Define media, platform, data, measurement, creative and management charges.

7. Assign measurement assets. Name owners for events, tags, offline files, AMC instances and queries.

8. Set change authority. Document who can change budgets, targeting, audiences, integrations and attribution rules.

9. Protect continuity. Require recurring exports and off-platform storage during the engagement.

10. Write the exit clause. State notice, handover scope, formats, deadlines, assistance and deletion confirmation.

20 questions to ask a managed Amazon DSP provider

1. Which legal entity contracts for the platform and media?

2. Where will our advertiser sit, and can our team log in?

3. Who controls administrator permissions?

4. Which platform, cost and billing fields can we see?

5. Can we export campaign and line-item settings?

6. Which reports arrive automatically, in what format and how often?

7. How much historical reporting remains available after termination?

8. Where are recurring exports stored outside the provider dashboard?

9. Who owns the source data we supply?

10. Can the provider reuse our data or audience logic for another client?

11. Who can create, edit, share, activate and delete Advertiser Audiences?

12. Who administers the AMC instance and stores query logic?

13. Can we receive engagement-specific AMC queries and documentation?

14. Who owns conversion definitions, tags and offline-event processes?

15. Which connected applications and third parties receive access?

16. Who approves new vendors, data flows and audience uses?

17. Which creative files, platform objects and deal IDs can transfer?

18. What exactly is delivered during a partner transition?

19. How quickly must the provider complete the handover?

20. How is deletion confirmed after the retention period?

What should be in an Amazon DSP exit package?

Do not wait for termination to design the archive. Build it throughout the relationship.

• Account, advertiser and user-permission map.

• Campaign, line-item, targeting, budget, bid and frequency settings.

• Creative register, master files, approvals and destination URLs.

• Audience register with source, logic, exclusions, lookback and refresh schedule.

• Conversion-event dictionary, tag details and attribution settings.

• Recurring performance, supply, reach, frequency, conversion and cost exports.

• AMC instance details, engagement-specific queries and saved output definitions.

• Publisher deal register, contact owners and transfer constraints.

• Change log, optimization history and open issues.

• Final invoice reconciliation and deletion confirmation.

Some platform assets may need to be recreated rather than transferred. The exit package should say which, who will rebuild them, what dependencies apply and how continuity will be tested.

Governance should continue after the contract is signed

Run a quarterly governance review alongside performance reporting.

The Amazon DSP campaign audit checklist covers delivery and setup controls. Add this governance review so performance does not hide account risk.

Red flags in a managed Amazon DSP proposal

• “Full ownership” appears with no asset list or permission matrix.

• The advertiser cannot receive a direct login or tested report export.

• Only an all-in CPM is shown, with no media and fee separation.

• The provider refuses to share audience definitions or conversion logic.

• AMC access is promised without naming the instance, admins or query rights.

• Reporting ends when the provider dashboard is disabled.

• The contract gives the provider broad reuse rights over client data.

• No one owns deletion, user removal or third-party application cleanup.

• The exit clause says “reasonable assistance” with no timeline or deliverables.

• Historical exports begin only after notice is given.

How Ad Geeks structures managed Amazon DSP governance

Ad Geeks can combine managed activation with a documented control model. The setup can include an account map, named permissions, audience register, measurement dictionary, recurring report exports, cost reconciliation and an exit-ready asset inventory.

The goal is simple: the advertiser should understand what it supplied, what the platform generated, what the managed team built and what remains available if the operating model changes.

Review the account before you sign.

Request Access

Review the account before you sign.

Request Access

We can audit the proposed structure, reporting, audiences, permissions and handover terms.

Frequently asked questions

Official sources

1. Amazon Ads privacy notice

2. Amazon Ads - AMC custom audience creation and activation

3. Amazon Ads - AMC API availability

4. Amazon Ads - Manage third-party applications with account access