Amazon Ads data extractor
Import a new customer’s Amazon Ads data — attribution report performance adgroup, attribution report performance campaign, attribution report performance creative, and attribution report products, and 50 more object types — into your product as normalised, relational tables. Vern handles Amazon Ads’s auth, pagination and rate limits, so onboarding a customer off Amazon Ads doesn’t mean building and maintaining that plumbing yourself.
- Objects extracted
- 54
- Incremental
- 30
- Authentication
- OAuth
Every queryable object type
Re-runs pull only what changed
Stored encrypted, never in the transcript
Export coverage
What Vern pulls from Amazon Ads
Know exactly what comes across before you migrate. Every object below is normalised into typed tables with referential keys preserved, so the relationships between a customer's records survive the import.
- Attribution report performance adgroup
- Attribution report performance campaign
- Attribution report performance creative
- Attribution report products
- Portfolios
- Profiles
- Sponsored brands ad groups
- Sponsored brands adgroups report
- Sponsored brands adgroups report stream daily
- Sponsored brands campaigns
- Sponsored brands campaigns report
- Sponsored brands campaigns report stream daily
- Sponsored brands keywords
- Sponsored brands v3 report
- Sponsored brands v3 report stream daily
- Sponsored display ad groups
- Sponsored display adgroups report
- Sponsored display adgroups report stream daily
- Sponsored display asins report
- Sponsored display asins report stream daily
- Sponsored display budget rules
- Sponsored display campaigns
- Sponsored display campaigns report
- Sponsored display campaigns report stream daily
- Sponsored display creatives
- Sponsored display product ads
- Sponsored display productads report
- Sponsored display productads report stream daily
- Sponsored display targetings
- Sponsored display targets report
- Sponsored display targets report stream daily
- Sponsored product ad group bid recommendations
- Sponsored product ad group suggested keywords
- Sponsored product ad groups
- Sponsored product ads
- Sponsored product campaign negative keywords
- Sponsored product campaigns
- Sponsored product keywords
- Sponsored product negative keywords
- Sponsored product targetings
- Sponsored products adgroups report
- Sponsored products adgroups report stream daily
- Sponsored products asins keywords report
- Sponsored products asins keywords report stream daily
- Sponsored products asins targets report
- Sponsored products asins targets report stream daily
- Sponsored products campaigns report
- Sponsored products campaigns report stream daily
- Sponsored products keywords report
- Sponsored products keywords report stream daily
- Sponsored products productads report
- Sponsored products productads report stream daily
- Sponsored products targets report
- Sponsored products targets report stream daily
Managed by Vern
The parts you'd otherwise build yourself
Authentication
Your customer authorises Vern once through the vendor’s consent screen. Vern stores the resulting tokens encrypted, refreshes them, and attaches them to every request — you never handle the raw credential.
Pagination
Vern detects and handles Amazon Ads's paging model — cursor, page number or offset — internally, and returns one consistent, de-duplicated result set. You import a customer's complete data without ever managing a page token.
Rate limits
API sources rarely publish their real rate ceiling until you hit a 429 mid-import, and many silently cap page size. Vern queues and throttles requests to stay under the limit, so a partial pull never lands a customer in your product with missing data.
Output shape
Normalised JSON per object with referential keys preserved and timestamps in ISO 8601. Delivered as JSON or CSV, pushed to your API or webhook, or loaded straight into your application database.
Schema drift
If Amazon Ads changes what it returns between migrations, the agent notices the difference against what it recorded last time and raises it, rather than importing a customer with a column quietly missing.
What it learns
Everything Vern works out about Amazon Ads's quirks — field formats, enum values, ID and date patterns — is written down against the source and applied automatically to every customer you migrate off it afterwards.
What your customer provides
- Client ID
- Client Secret
Collected once, stored encrypted in a vault, and attached to every request. Credentials are never written into the agent transcript.
API quickstart
Run a Amazon Ads migration from your own product
Create the migration, let the agent extract and map, then pull the result out — without your customer ever seeing a Vern dashboard.
API=https://app.vern.so/api/v1
KEY="x-api-key: $VERN_API_KEY"
JSON="Content-Type: application/json"
# 1 — create a migration against Amazon Ads
ID=$(curl -sX POST $API/migrations -H "$KEY" -H "$JSON" \
-d '{"name":"Acme onboarding","source":"Amazon Ads"}' \
| jq -r .migration.id)
# 2 — hand over the customer's credentials for this run
curl -X POST $API/migrations/$ID/source-connection -H "$KEY" -H "$JSON" \
-d '{"credentials": { ... }}'
# 3 — the agent extracts, maps and previews, stopping before it writes
curl -X POST $API/migrations/$ID/runs -H "$KEY" -H "$JSON" \
-d '{"kind":"generate"}'
curl $API/migrations/$ID/preview -H "$KEY"
# 4 — approve, then pull the normalised rows back out
curl -X POST $API/migrations/$ID/runs -H "$KEY" -H "$JSON" \
-d '{"kind":"execute"}'
curl -X POST $API/migrations/$ID/exports -H "$KEY" -H "$JSON" \
-d '{"slugs":["customers","invoices"]}'The Migration API runs the whole lifecycle over HTTP with an organisation-scoped key. The agent conversation can be streamed into your own UI, and the preview lets you check exactly what an import will produce before a single row is written.
Read the API referenceAmazon Ads references
Related
Other Advertising sources
Onboarding a customer off Amazon Ads?
Bring a real Amazon Ads export and we'll show you what lands in your product.