All use cases

A weekly all-channel report with ROMI and conclusions

On Monday you have to say which channel brought money, not just which one spent it. The agent pulls spend and revenue per channel for the week.

Medium · 20 min · once a week

What you get

Channel        Spend      Revenue     ROMI
Yandex Direct  84,200 ₽   312,000 ₽   270%
VK Ads         41,500 ₽    96,400 ₽   132%
Telegram       18,000 ₽    no data       —
Total         143,700 ₽   408,400 ₽   184%

Telegram passes no revenue into Metrica, so that row has no
ROMI at all. Sample figures.

A sample on made-up data — your numbers will be your own.

Who it fits

  • A Monday stand-up where one table has to answer what each channel brought in money.
  • Budget is split between Direct and VK, and every week someone decides where to move it.

When it won't work

Revenue tracking isn't set up in Metrica — then this is a spend report, not a payback one.

How the agent does it

1

Set week and goal

Name one action in Metrica that counts as a result. Otherwise the agent takes every goal at once and the totals drift apart.

2

Run the build

Spend from the ad accounts and revenue from Metrica are joined by campaign tag. Names aren't matched — they drift apart too easily.

3

Check the numbers

Budgets get moved on this report. Rows where the revenue has no known source are flagged separately, so start there.

What you set

Connect Yandex Direct, VK Ads and Yandex Metrica. Manually: the week's boundaries, which action counts as a result, the period to compare against.

What you'll need

Яндекс Директ
VK Реклама
Яндекс Метрика

Starter prompt

Copy the prompt or open it straight in a chat with the agent.

Prompt for the agent

Build a report on ad channels for [period — week from … to …] using data from Yandex Direct, VK Ads and Metrica. For each channel and campaign: spend, clicks, conversions on goal [goal name in Metrica], revenue from that goal, ROMI and the change versus [the previous week]. Calculate ROMI only where revenue comes from Metrica. Where there is no revenue — don't substitute an average order value and don't carry it over from another channel, move such channels into a "ROMI not calculated" block and write what is missing. Don't explain a drop by seasonality until you show the same week a year ago. Output XLSX: a sheet by channels, a sheet by campaigns and five lines of conclusions — what grew, what fell and where to move budget.

Open in chat
Check the result

Check the weekly report. List: — channels where revenue was not taken from Metrica but calculated by you; — campaigns that didn't match between the ad account and Metrica, and where you assigned their spend; — rows where ROMI is calculated on fewer than [10] conversions; — the discrepancy between total spend in the report and the total in the ad accounts — show both figures; — conclusions that rest on a single week and fall apart over a month. Whatever you can recalculate yourself — show as an "I suggest changing" list, don't fix it silently.

A second prompt — the agent uses it to review its own work and show what's left for you.

Related use cases