Amazon Advertising FAQs

Amazon advertising FAQs

Applicable Connectors

  1. Amazon Sponsored Products

  2. Amazon Sponsored Brands

  3. Amazon Sponsored Display

FAQs

  1. Are click attribution metrics updated by Amazon replicated by Daton?Yes. You can configure the look back window (Attribution Offset) from the UI and Daton will repeat the data after the selected number of days.

  2. What attribution options are available? Look back Until: Repeat data until selected number of days. You can select up to 31 days to replicate changes up to 30 days. Look back After: Repeat data after selected number of days. Multiple days can be selected up to 31 days.

  3. Which attribution offset is better for me? Look back Until: When you consume Amazon reports every day for your business insights. Look back After: When you consume your reports on a weekly or monthly basis. Note that the metrics may not be accurate for previous 7 days as the minimum look back date is 8 days in Daton.

  4. Which days are preferred attribution offset? It depends on your use case. If you use 30day attribution for your reporting, then you must choose 31day offset on Daton. Amazon Ad console will use 14day attribution for most of their reports. If you want to match with Amazon reports, then you must use 15day offset on Daton.

  5. Why do I see duplicates in my tables? Since we replicate the data after a few days (based on selection from UI), we append the new data to the tables by default. You can also configure the tables or integrations to ‘upsert’ instead of ‘append’ to handle the duplicates.

  6. How do I eliminate duplicates from these tables? You can use _daton_batch_runtime to identify most recent record for a primary key of the table. Use the deduplication guide at the bottom of this page.

  7. How much historical data can be replicated through Daton? Amazon Ads APIs share previous 60 days of reports. Daton can lookback and replicate previous 60 days of data from the date of integration.

  8. Will reloading a table affect my historical data? Yes. Daton will drop and create the table again for reloads. Historical data replicated so far would be lost and previous 60 days data would be replicated again.

  9. Is present days data replicated through Daton? No. Amazon will not share present day’s reports through APIs, until the day ends. Daton can replicate only previous days data after 2 AM of seller time.

  10. Why are most of my jobs showing zero records processed? Daton replicates previous day’s data in the first job after 2 AM of seller time. All jobs after that will be skipped and marked success with zero records processed. This is to reduce the volume of data and duplicates on destinations. If the first job fails, then Daton will repeat the job based on frequency selected.

  11. What is reportDate column? ReportDate is the date for which the data belongs to. For example, reportDate=’2021-04-01’ will have all metrics such as clicks, spend, attributedSales14d generated for 1st April.

  12. How accurate is data replicated by Daton? There will be <1% variance after 15 days. There can be 5-10% variance for previous day (applicable for previous week if you select look back after option).

  13. Why do my metrics do not match with Amazon even after 8 or 15 days? What steps must I take? There could be various reasons for this – • Deduplication mistakes: You could have made mistakes while removing duplicates from Daton populated tables. Use the guide at the bottom of this page for deduplicating the data. • Are you using right attribution metric while comparing with Amazon reports? • Errors in integration: Check if there are errors in Daton jobs for the subject dates and report to us. • Check if all campaigns present in Amazon reports are also present in Daton tables. Are there any name changes for campaignIds? • Check if you have used campaignName for deduplication. You must always use campaignId for primary key as campaignNames can be changed.

  14. Can I change attribution offsets for my integrations? Yes. You can change them on edit integration workflow.

Deduplication Guide

Step 1: Identify the primary keys for the report or table. Sample primary keys for a few reports -

Report Name

Primary key for deduplication

CampaignsReport

campaignId + reportDate

PlacementCampaignsReport

campaignId + placement + reportDate

AdGroupReport

campaignId + adGroupId + reportDate

KeywordReport

campaignId + keywordText + matchType + reportDate

SearchTermKeywordReport

campaignId + query + matchType + keywordText + reportDate

ProductAdsReport

campaignId + asin + reportDate

ProductTargetingReport

campaignId + targetingText + reportDate

SearchTermProductTargetingReport

campaignId + targetingText + query + reportDate

Step 2: Identify most recent record for the primary key using _daton_batch_runtime. Following is an example for SponsoredProducts_CampaignsReport for BigQuery warehouse, to fetch all deduplicated rows –

SELECT FROM (select ,ROWNUMBER() OVER (PARTITION BY campaignId, reportDate order by _daton_batch_runtime desc) row_number from `daton-210514.AmazonDataset.AmazonSP 4xxxxxxxxxxxxxxxxxxx1_SponsoredProducts_CampaignsReports` ) where row_number=1

Step 3: Create or save the query as a view.

Step 4: Use the above view in downstream queries.