What Data Do I Need to Use the Amz Ad Waste Detector?
← Back to How to Separate Budget Constraints From Poor Campaign Performance
Quick answer
Amazon Advertising Console exports in CSV or XLSX format are the core data inputs for the Amz Ad Waste Detector. Automated email import and GitHub Actions provide additional paths for moving campaign reports into the tool without repeated manual downloads. The system uses those structured exports to evaluate spend, sales, and performance signals related to Amazon Ads campaigns and search-term data.
If you're preparing the tool for a new analysis, the fastest setup is to export your Amazon Ads data from the reporting console and save it as a CSV or XLSX file. Amz Ad Waste Detector can then use that file directly, or you can configure a recurring import route.
Accepted file formats
CSV and XLSX exports from the Amazon Advertising Console are accepted as primary input files. This covers the most common reporting workflow: running or scheduling a report in Amazon Ads, downloading the file, and loading it into the tool.
Keep the original report structure intact. Aggregating, renaming, or deleting columns before upload can reduce the tool's ability to map spend and performance signals correctly.
Automated email import and GitHub Actions
For teams that do not want to manually download files each week, the tool supports automated email import. This allows scheduled Amazon Ads reports to arrive and be processed as part of a recurring workflow.
GitHub Actions can also be used to handle files in a repository. That path is useful when your reporting pipeline already lives in a version-controlled environment.
- CSV or XLSX from Amazon Advertising Console
- Automated email import for recurring reports
- GitHub Actions processing for connected workflows
When this matters
Input format and import method become especially important when comparing budget limits against campaign performance. If files are delayed, aggregated, or inconsistently formatted, it becomes harder to isolate wasted spend from a simple budget shortfall.
Choosing a stable import path helps maintain the granular campaign and search-term detail that the analysis requires.
Related products
Related guides
Once the correct CSV/XLSX or automated data stream is in place, the next step is to interpret that data in a way that separates real budget constraints from poor campaign performance. That distinction is covered in more depth in the guide on how to separate budget constraints from poor campaign performance.