briefing

shallow

com.apptiller/apptiller · Verify this server

Use this when the user asks what's wrong with their ads, what to change, or what an earlier ad change did. What Apptiller's analyst found in each app's last 14 days of synced data: Meta campaigns and ad sets, and Apple Ads campaigns, ad groups and keywords, that spent with no results, cost far more per result than the rest of their channel, or far less. Each finding has its evidence (spend, results and their source, cost per result with a 90% range, the baseline it was compared with), how sure it is, and one proposed change (pause, bid or budget). Like is compared with like: one channel, level, objective and currency, measured in the deepest result the group has enough of (purchases, trials, sign-ups, attributed installs, then installs the network claims), from one source. Also, per group, what it was judged by or why it couldn't be, and the changes Apptiller made in the app's ad accounts over the last 30 days (with change ids), each with its effect: the 7 days before it against the 7 after, in the result and source its finding was judged by, net of how the rest of its group moved over the same days, with how sure that is and a verdict (better, worse or unclear: cheaper results after a cut, more of them after a raise). An Apple Ads change also gets `search` once the app's App Store Connect analytics are connected (search results campaigns only): all of App Store search's first-time downloads a day before and after (Apple's App Analytics, organic included), the part Apple Ads credits its search results campaigns with, and the share of Apple Ads' move that was new to search, with a 90% range set by how much organic search moved week to week before (verdict incremental, organic or unclear, once Apple's numbers for all 7 days after are in); the analyst doesn't raise again what a raise mostly took from organic search. While a change is being measured, the analyst leaves alone the entity, those above it and those inside it; their proposals wait (status 'waiting', and `waiting` says for which change and until when). After that it judges them on the days since the change only, and if the finding still holds proposes the next step, saying what the last one did. The analysis runs daily at 12:40 UTC; set refresh to run it now. Nothing in an ad account changes from this tool: a proposal changes something only once the user approves it and it is applied.

100.0/100

1 trials · measured 10 days ago

briefing scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.apptiller/apptiller, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-11-12100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: briefing
[![Vouch score](https://vouch.tools/api/tools/ec564ec5-287d-4922-9fa9-4572ed678548/badge.svg)](https://vouch.tools/tools/ec564ec5-287d-4922-9fa9-4572ed678548)
briefing — Vouch