Filter Amazon Ads Export Data to Relevant Campaigns, Ad Groups, and Marketplaces

What to filter before loading into Power BI or Looker Studio

Start by narrowing the export to the campaigns and ad groups that align with the current reporting question. This often means excluding paused or test campaigns and keeping only the marketplace codes you actually sell in.

• Campaign name or ID — isolate specific product lines, match types, or experimental campaigns.
• Ad group — remove broad groups that mix too many intent levels if they are not part of the analysis.
• Marketplace — separate Amazon.com, Amazon.co.uk, Amazon.de, and others to avoid mixing currencies and seasonal effects.
• Date range — keep a consistent comparison window so period-over-period trends remain valid.

Keeping filtered datasets ready for reliable reporting

After filtering, check that the remaining rows still contain the columns your dashboard expects. If you remove marketplace rows, avoid also removing the regional column entirely; keep the dimension so filters work later in Looker Studio or Power BI.

Tools like Amazon Ads Dashboard by Todoza can consolidate exports and provide drill-down views, which makes it easier to preview which campaign and marketplace segments are worth keeping before the final BI load.

When this matters

Filtering matters most when you are comparing performance across marketplaces with different currencies, or when a single campaign group is responsible for most of the spend. In those cases, unfiltered exports can hide the signal you need. It also matters when a stakeholder asks for a quick answer; a filtered dataset lets you refresh the dashboard without rebuilding measures.