Channel Attribution
helio / channel-attributionSet a UTM convention once. Your AI teammate reports visitor-to-signup conversion by channel every day, and flags which ones deserve more budget and which don't.
Report yesterday's signups by channel from our GA data, tagged by UTM source, and flag which channel is worth more budget and which is converting at zero. Send it to Slack at 9am. Ask me what you need before you start.
Swap in your analytics source and the delivery time you want.
What is Channel Attribution?
It reads visitor and signup data tagged by UTM source and reports conversion by channel every day at the same time, instead of at month-end. It flags a channel spiking or dropping to zero, names which one deserves more spend, and leaves the budget call to you.
What it does
Any chatbot reads a conversion number once. Helio runs it as a standing job — from your context, kept current, delivered to you.
| Owns the job, not just the chart | It pulls the day's traffic, computes conversion per channel, flags anomalies, and delivers the read every morning. |
| Runs again without starting over | Once saved, the report runs on a daily schedule from the same UTM convention. |
| Works from your context | It reads live visitor and signup data from PostHog or GA, tagged by UTM source. |
| Keeps itself current | When you add a channel or change the UTM convention, it updates the report and remembers past baselines. |
| Lands where you work | The daily table and its recommendations arrive in Slack, Lark, or email. |
Three things it gets right
Conversion split by channel
It reports visitor-to-signup rate for each UTM source separately, so one weak channel can't hide inside a blended average.
Zero-conversion caught in a day
A channel dropping to zero gets flagged the same morning it happens, three days before month-end review would.
States its attribution logic
It says whether pre-login and post-login IDs are linked, and flags a bloated direct bucket that needs utm_content.
Questions
- Does it require a specific UTM naming convention?
- It works with whatever convention you already use — the key requirement is that placements are tagged consistently so channels can be told apart.
- How does it handle logged-out to logged-in attribution?
- It states its attribution methodology explicitly — whether pre-login and post-login IDs are linked — rather than presenting a number without the caveat.
- Can it break this down by campaign, not just channel?
- Yes — if your UTM tagging includes campaign-level detail, the report can be scoped down to that level too.
- Does it decide the budget for me?
- It recommends where the data points, but budget decisions stay with you — it doesn't move spend on its own.
Know which channel is actually working.
Tag your placements once — Helio reports the real conversion by channel every day.
Ask about this automation