How Does Ad Badger Sync with Amazon?

There are several sync-events that Ad Badger performs with Amazon to ensure the most accurate data to perform optimizations.

  • Initial Sync: When you first sign up with Ad Badger, we pull the maximum amount of data allowed by Amazon which is 60 days of data.
  • Automatic Daily Sync: Every day, we pull in another day's worth of data - without the last 2 days. This is because the previous 48 hours are notably unreliable - both from the API, as well as from Amazon itself. It's important to be aware of this 48 hour delay and to never make any optimization decisions based on this data. The Team discusses this data-delay in a podcast episode here: During daily sync, Ad Badger also pulls in any new campaigns, ad groups, keywords, etc. you created in the last 48 hours, but they will not have any report data just yet.
  • Attribution Sync: As you know, Amazon has potentially a 30-day delay in reporting its revenue to ads. This is when a user clicks on an ad on the 1st of the month but doesn't convert until the 10th of the month. Ad Badger goes and grabs older historic data to account for this attribution lag, to ensure we are always making the smartest decisions for your campaigns. These happen throughout the month.
  • The Epic 180 Day Data View: In Amazon, much of your data is limited to viewing 60 days at a time (like a search term report in Amazon). In Ad Badger, we have an Epic 180 Day Data view, so you can make decisions based on aggregate data. We're working on building even longer time frames available for premium plans.

Those 3 automatic syncs cover all the bases and ensure you have the most up-to-date data to optimize your campaigns.

We also have some sync-events in the works:

  • Manual Sync: Ad Badger v2 will soon have a manual sync, which will allow you to pull in new data from the past 48 hours if you want, as well as any new campaigns you created since the last daily sync. Most plans will be able to perform manual sync once a day. We expect to roll out manual sync in late 2020, once our servers can handle the workload.

How did we do?

Powered by HelpDocs (opens in a new tab)