AI reports
Have your recurring campaign review prepared for you
Describe the campaign question, schedule and recipients. The Linkrunner AI agent prepares a report from your project data and delivers it by email or Slack. In beta on request.
Part of the AI agent, in beta. Request access and we approve it quickly.
Scheduled reports
Asia/Kolkata
- Weekly ROAS checkMon 26 OctEvery Monday, 9:00 AM3 people
- Daily install pulseFri 23 OctEvery day, 9:30 AM2 people
- Creator campaigns, D7 revenueThu 29 OctEvery Thursday, 6:00 PM4 people
- October closeMon 2 NovOnce, 2 Nov, 10:00 AM6 people
Set up in chat with the AI agent. 4 of 20 reports used.
Weekly ROAS check is ready
Mon 9:04 AM
Linkrunner AI agentTo you and 2 teammates · completed 19 Oct 2026, 9:04 AM
Two campaigns lost ROAS last week while spend held steady. Always on, India fell the most; its top creative has run for 5 weeks.
| Campaign | ROAS | vs prior week |
|---|---|---|
 Meta·Diwali installs | 2.40 | +0.12 |
| Meta·Always on, India | 1.60 | -0.48 |
 Google·Search, brand terms | 3.10 | +0.05 |
| Google·App campaigns, installs | 1.85 | -0.31 |
Join 400+ growth teams using Linkrunner.
What a report is
Turn a recurring question into a scheduled report
In the inbox, or in the channel
Each recipient gets the summary by email with a link to the full report. Reports can also post to a connected Slack channel.
# campaign-review
Mon 9:04 AM
Weekly ROAS check
Two campaigns lost ROAS while spend held steady.
- Always on, India: ROAS 1.60, down 0.48
- App campaigns, installs: ROAS 1.85, down 0.31
- Diwali installs: ROAS 2.40, up 0.12
Recipients come from your project
Pick up to 20 project members per report. When someone leaves the project, their copy stops.
Recipients
3 of 20
Search project members
YouAdmin
Growth leadMember
Performance marketerMember
Product analystMember
# campaign-review
Mon 9:04 AM
Weekly ROAS check
Two campaigns lost ROAS while spend held steady.
- Always on, India: ROAS 1.60, down 0.48
- App campaigns, installs: ROAS 1.85, down 0.31
- Diwali installs: ROAS 2.40, up 0.12
How it works
Set up a report in one chat
- 01
Ask the agent
In the agent chat, say what the report should cover, when it should run and who should get it.
- 02
Confirm the schedule
Check the brief, the timezone and the recipients the agent proposes, then confirm.
- 03
Read it, then dig in
The report lands in each recipient's inbox. Open it in the agent to see the full answer and ask follow-up questions.
From chat to inbox
Ask once, read it every Monday
You ask in chat
Every Monday at 9, send me Meta and Google ROAS by campaign for last week, and flag anything that dropped
The agent confirms
- Runs
- Every Monday, 9:00 AM, Asia/Kolkata
- Sends to
- You and 2 teammates
In your inbox, Monday 9:04 AM
Weekly ROAS check is ready
Your app, completed 20 Oct 2026, 9:04 AM Asia/Kolkata
- Meta and Google ROAS by campaign for last week, against the week before.
- Two Meta ad sets lost ROAS while spend held steady. Both point to the same creative.
- Google install volume rose; cost per sign-up stayed flat.
Limits
What each project gets
Report delivery to a connected channel
Slack
Hear from our customers
Trusted by teams that care about more than attribution.
“The level of customisation that Linkrunner was able to offer was unmatched by any of the other competitors we looked at. Their team took the time to understand our exact requirements and delivered a solution that felt tailored to our needs, rather than forcing us into a fixed framework. That flexibility made a significant difference for us and was one of the key reasons Linkrunner stood out.”
Ronald M Thomas
Digital Marketing, Playo
34%
CPI reduction in 3 months
₹20.30 → ₹13.39
Google Ads CPI drop (Dec '25 → Feb '26)
Frequently asked questions
How do I set up a scheduled report?
What can a report cover?
How often can a report run?
Who can create and receive reports?
Can a scheduled report change my campaigns?
How do I get access?
Set up your next recurring campaign review
Request beta access, describe the report you need and confirm the schedule and recipients in chat.