Map Amazon DSP requirements
Share the Amazon DSP source, fields, and reporting questions your team needs to answer.
What you can do with Amazon DSP in Maven
Define the advertiser, campaign, creative, delivery, and conversion views your team needs before implementation. Maven will confirm the available Amazon DSP access path and field coverage so cross-channel reporting starts with clear definitions.
How it works
Plan Amazon DSP reporting before implementation
Confirm the source access, fields, governed definitions, validation criteria, and rollout scope before treating the connector as production-ready.
Define governed metric coverage
Maven documents how the approved Amazon DSP fields would map into governed metrics before implementation begins.
Approve the implementation path
Confirm access, scope, validation criteria, and rollout timing before the connector is enabled for production reporting.
What Maven syncs from Amazon DSP
DSP performance
Works well with
Report Amazon DSP alongside the rest of your stack
FAQ
Amazon DSP reporting questions
What Amazon DSP metrics can I report on in Maven?
Maven exposes 114 governed Amazon DSP metrics, including Total Ad Spend, Impressions, Clicks, Conversions, Ad Revenue and Conversion Events, each defined once so it means the same thing in every report.
What can I break Amazon DSP performance down by?
You can break Amazon DSP metrics down by Entity Level, Campaign, Ad group, Ad, Ad status, Objective, Commission Rate Percent and Media Budget Currency, and more.
Can I combine Amazon DSP with other data sources?
Yes. Amazon DSP reports alongside sources like Google Analytics 4, Shopify, Google Ads, Facebook Ads and HubSpot. Maven models every source into one governed layer, so you can blend them in a single dashboard, report, or question.
What should we define before adding Amazon DSP to Maven?
Start with the business questions, source fields, reporting grain, refresh cadence, and account access your team needs. Maven will confirm the implementation path and supported coverage before production use.
Is the Amazon DSP integration available today?
Availability depends on the source and workspace requirements. Maven can review the Amazon DSP reporting fields you need and confirm the current implementation path before you commit to a rollout.
How will Maven protect Amazon DSP data?
Any production implementation must use scoped credentials, encrypted secret storage, workspace-level access controls, and only the reporting data approved during implementation review.
Ready to make client reporting easier to run and defend?
Bring one client report or disputed metric. We'll map the workflow and where Maven fits.
One report, reviewed end to end
Clear roles across data, QA, and delivery
No pitch deck. No pressure. 20 minutes.
