Calculate ad spend share for each campaign
Budget sits in Yandex Direct and two marketplace dashboards, and payback is estimated by eye. Spend as a share of revenue is computed per campaign.
Medium · 20 min · once a week
What you get
Ad spend share, Jun 01–14 (target: under 12%) Campaign Spend, ₽ Revenue, ₽ Share WB · Chairs, autobid 84,000 412,000 20% Ozon · Tables, search 61,000 980,000 6% Direct · Brand 22,000 790,000 3% Direct · Categories 48,000 215,000 22% Over target: 2 campaigns, 132,000 ₽ of spend. No revenue attached: 39,000 ₽ — 12% of budget.
A sample on made-up data — your numbers will be your own.
Who it fits
- The ad report is stitched from three dashboards that each count things their own way.
- You need a "cut it or fund it" call on specific campaigns, not one number for the channel.
When it won't work
Campaigns are named at random and tied to no category or product — there is nothing to match the spend to.
How the agent does it
Set period and target
Anything under two weeks is noisy on marketplaces: orders arrive well after the click. Name the share above which a campaign counts as losing money.
Run the calculation
Each campaign is counted on its own, and revenue is never shifted between dashboards to cover a gap. If it doesn't add up, the agent says so.
Check before cutting
Ask the agent to review its own work: where a verdict rests on twenty orders, where an order may be counted twice, and how much spend has no revenue.
What you set
Connect Yandex Direct, Ozon and Wildberries. From you: the period, the spend share you consider acceptable, and which orders count as ad-driven.
What you'll need
Starter prompt
Copy the prompt or open it straight in a chat with the agent.
Calculate ad cost share for every campaign for [period]: Yandex Direct and the ad dashboards of Ozon and Wildberries. For each campaign: spend, revenue by the dashboard's attribution, ad cost share, order count, average order value. Within a single platform use one attribution model and state which one. Don't add up revenue from different dashboards for the same order — that's double counting. If a campaign's revenue can't be tied to its spend, move it into "attribution not determined" rather than crediting it with the category's overall sales. Separate campaigns with an ad cost share above [target] from those with too little data for a conclusion: at spend below [threshold] or fewer than [20] orders, mark the row as unreliable. Output a table of campaigns in descending order of spend and a bottom line: how much budget went into campaigns with an ad cost share above target.
Open in chatReview the ad cost share calculation. List: — campaigns where the conclusion rests on fewer than [20] orders or on [a few days]; — which attribution model you took for each platform and where they don't agree; — orders that could have been counted twice in different dashboards; — awareness campaigns or new launches that ad cost share isn't measured on; — spend left without attributed revenue, and its share of the total budget.
A second prompt — the agent uses it to review its own work and show what's left for you.