Reports

Waitlist
Executive summaryLast 30 days

Northwind SupplyExecutive summary

The one-page answer for a client or a board. · Generated 27 Jul, 13:05

Executive summary

Over the last 30 days, Northwind Supply spent €62.6k across 6 active campaigns on 3 platforms, producing 2,126 purchases at €29.46 each. That returned €300k of revenue at 4.79×. Cost per result moved +3.0% against the previous period, on spend +8.1%.

Spend
€62.6k
+8.1% vs previous
Purchases
2,126
+5.0% vs previous
Cost per purchase
€29.46
+3.0% vs previous
Revenue
€300k
ROAS
4.79×
Target 3.4×

Spend and results over the period

25/0630/0605/0710/0715/0720/0724/07
SpendPurchases

Spend distribution

Share of budget by platform

€62.6kTOTAL
Meta Ads56%
Google Ads37%
TikTok Ads7%

What this means

Ada's reading of the period, recomputed from the current state of every campaign

Key wins

  • Search | Brand & Category returned 7.47× on €5k — the strongest performer in the account.
  • 1 campaign is improving period over period: Performance Max | Retail EU.
  • 3 changes were reviewed and approved this period, including Prospecting | Autumn Layering — approved campaign creation. the campaign was created paused and awaits a separate activation approval.
  • 7 of 8 creatives are still fresh, so there is rotation headroom before the next refresh is needed.

Key risks

  • Prospecting | Summer Trail — ROAS fell 29% against the previous period.
  • Summer Trail — Ridge hero has a fatigue score of 84 and is carrying €12.6k of spend.
  • Retargeting | Site & Cart — Ahead of plan by 26%. Projected to finish over budget.
  • Performance Max | Retail EU — Ahead of plan by 15%. Projected to finish over budget.

Recommended next steps

  • Rotate Summer Trail — Ridge hero out of its highest-spending placement and bring an approved variant forward.
  • Consider moving roughly 20% of Prospecting | Summer Trail's budget toward Search | Brand & Category, which returns 7.47× against 2.49×.
  • 1 campaign is created and held paused awaiting activation approval.
This report is generated from the demo dataset and recomputes whenever you approve a change. Exporting produces a simulated success state — no file is created and nothing is sent anywhere.