Connecting Amazon Ads to Qlik: the connector at a glance
In short: Qlik connects to the Amazon Ads API and replicates ad objects such as campaigns, ads, keywords and budget rules. That is the advertising account, not the pseudonymised signals from Amazon Marketing Cloud. If you need AMC data in Qlik, run the query in AMC and load the result through S3 or the download URL.
Which data the connector replicates
Qlik documents the Amazon Ads connector as a replication through the Amazon Ads API. It pulls objects from the advertising account, not from Amazon Marketing Cloud: the schema list in Qlik's documentation includes sponsored_products_campaigns, sponsored_products_ads, sponsored_products_keywords, sponsored_brands_campaigns and sponsored_display_campaigns. For every object Qlik names the primary key and the replication method.
| Object (example) | Primary key | Replication |
|---|---|---|
sponsored_products_campaigns | campaignId | CDC |
sponsored_products_ads | adId | CDC |
sponsored_products_keywords | keywordId | CDC |
sponsored_brands_campaigns | campaignId | CDC |
sponsored_brands_budget_rules | ruleId | CDC |
sponsored_display_campaigns | campaignId | CDC |
sponsored_display_creatives | creativeId | Full Table |
sponsored_brands_keywords | keywordId | Full Table |
CDC means "Change Data Capture": Qlik picks up ongoing changes through a replication key. Full Table means the table is read again in full on every run. Which objects an account actually delivers depends on which campaign types are active in it.
Why this is not an AMC connector
The difference decides everything about the analysis. The Amazon Ads API delivers the ad objects you control yourself: campaigns, keywords, budgets, IDs. Amazon Marketing Cloud delivers aggregated, pseudonymised signals about your customers, which you query with SQL. A connector that uses the Amazon Ads API cannot deliver an AMC table, because it never queries one.
- You see your own campaign structure — not your customers' buying behaviour.
- The row is a campaign object, not an AMC row carrying an event.
- For analyses on new-to-brand rate, path to purchase or conversion window you need AMC itself.
- Both routes combine: ad data from the connector, AMC result from the query.
What the connection needs on your side
Qlik describes the setup as Login with Amazon: you need an Amazon developer account, a client ID and client secret pair, and a security profile with read access to the tables you want to fetch. Qlik requests the credentials when the connection is created and verifies the authentication before the replication starts.
- An Amazon developer account with client ID and client secret.
- A security profile (LWA) with read access to the desired tables.
- A start date from which Qlik should replicate.
- Optionally a Data Movement Gateway if your Qlik tier does not support it.
Qlik points out that schemas and naming conventions can change between versions. So check the schema version your connector pulls before the first run.
The next step for AMC data
If your goal is an AMC analysis, the route runs through AMC itself: start a query as a workflow, retrieve the result through S3 or the download URL, and load the file into Qlik or any other BI tool. You do not need Qlik for that — it works with any tool that accepts CSV or a database connection. Plan the dimensions in the SELECT list, because what you do not group by there is no longer available in the result.
Step by step
- Create the Amazon access. Open the developer account, create a security profile (LWA) and grant the profile read access to the desired tables. Store the client ID and client secret securely.
- Create the connection in Qlik. Open the Amazon Ads connector, enter the credentials and the start date, and confirm the authentication. The status "Verified" shows that the connection is in place.
- Check what is replicated. In the schema list check which tables exist for your campaign type, and mind the replication method: CDC delivers changes, Full Table reads the table again in full.
- Get AMC data separately. For analyses on customer behaviour, start the query in AMC and load the result into Qlik through S3 or the download URL. Fix the dimensions in the SELECT list.
Frequently asked questions
Can I fetch AMC data with the Qlik connector?
No. Qlik documents the connector as a replication through the Amazon Ads API. It delivers ad objects from the advertising account, not AMC tables. For AMC data you need a query in AMC and the import of its result.
Which tables does the connector replicate?
Qlik names objects such as sponsored_products_campaigns, sponsored_products_ads, sponsored_products_keywords, sponsored_brands_campaigns and sponsored_display_campaigns in its schema list, each with a primary key and a replication method. Which of them your account delivers depends on the active campaign types.
Do I need an Amazon developer account for Qlik?
Yes. Qlik authenticates through Login with Amazon. You need a developer account, a client ID and client secret pair, and a security profile with read access to the tables you want to fetch.
Is the detour via Qlik worth it for AMC analyses?
Not for the analysis itself: the query is created in AMC, and the result arrives as a file from S3 or via the download URL into any BI tool. Qlik is one possible target surface there, not a prerequisite. The connector earns its place when you need advertising data directly in the dashboard for budget, keyword or campaign analyses.