ads puts your paid channels in one table: Apple Search Ads, Meta and TikTok, with spend, installs and cost per install. Keep a copy in the repo, and verify and experiments judge an ad change on the same days as a listing change.
Where each channel comes from
When
appeeky/search-ads/ exists, ads and verify use it for Apple Search Ads, even with APPEEKY_API_KEY set. Without APPEEKY_API_KEY, ads shows only Apple Search Ads from the repo.
List your Meta and TikTok campaigns
Apple Search Ads needs nothing in the spec. Meta and TikTok ad accounts often promote more than one app, so list the campaigns that belong to this one inappeeky.spec.yaml:
See the numbers
A channel that cannot be read is listed in red with the reason; the others still print. With no data at all,
ads tells you to connect the channels in Appeeky and list the Meta and TikTok campaign ids.
The ads files
ads --save writes appeeky/ads/<date>.yaml, named after the end of the window, so the repo keeps a history of ad performance next to the listing:
to is exclusive: the window is from up to the day before to. A second save on the same day replaces that day’s file.
For day-by-day numbers, data pull writes apple-search-ads.csv, meta-ads.csv and tiktok-ads.csv to .appeeky/data/ (needs APPEEKY_API_KEY). See Commands.
The ad metrics
verify compares these before and after every push, and experiments can use any of them as their one metric:
So a listing change and an ad change are judged over the same days. A new subtitle that lifts organic installs while Search Ads installs stay flat reads differently from one that only moved paid installs.
Run an ad experiment
APPEEKY_API_KEY, the baseline is the metric over the same number of days before the start. Otherwise pass --baseline yourself. On the check date, verify measures the metric and closes the experiment. See Experiments.