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.
What is Channel Attribution?
- ·Reports channel conversion daily, not month-end: Visitor-to-signup conversion broken down by channel, delivered same time every day.
- ·Flags anomalies as they happen: A channel spiking or dropping to zero gets called out, not discovered a month late.
- ·Turns the data into a recommendation: Names a specific channel worth increasing spend on and a specific one underperforming its cost — with the reasoning stated plainly.
- ·Never moves budget on its own: It recommends where the data points; budget decisions stay with you.
What does Channel Attribution produce?
| 📊Daily conversion table | Visitor-to-signup rate, broken down by channel. |
| ⚠️Anomaly flag | A channel spiking or dropping to zero, called out explicitly. |
| 📈Standout channel | Flagged as worth increasing spend on, with reasoning. |
| 📉Laggard channel | Flagged as underperforming its cost, with reasoning. |
The SOP, step by step.
- 01
Pull the day's traffic
Visitor and signup data, tagged by UTM source.
- 02
Calculate conversion by channel
Not a single blended number — each channel reported separately.
- 03
Flag anomalies
A channel spiking or dropping to zero, called out explicitly.
- 04
Deliver daily
Same time each day, so channel performance is a habit, not a quarterly surprise.
- 05
Compare performance to spend
Which channels are converting well relative to what they cost.
- 06
Identify the standout
The channel most worth increasing investment in, with the reasoning.
- 07
Identify the laggard
The channel underperforming its cost, flagged for review.
- 08
State the reasoning
Not just a ranking — why each recommendation follows from the data.
What it produces, in practice.
Illustrative example generated for this page — actual output depends on your real data.
📈 Daily Channel Report
Sample · illustrativeSocial remains the strongest channel; one paid channel is at zero conversion.
| Channel | Visitors | Signups | Signup rate | Read |
|---|---|---|---|---|
| Social (X) | High | Mid | ~10% | ✅ Increase spend |
| Organic search | Mid | Mid | ~8% | 🔎 Underinvested — SEO opportunity |
| Paid channel | Mid | 0 | 0% | ❌ Recommend cutting |
| Direct | High | Mid | ~7% | ⚠️ Large black box — needs UTM |
Anomaly: the paid channel has had zero conversions for 3 straight days — recommend pausing or swapping creative.
Note on "Direct": inflated by in-app navigation losing its referrer. Tagging utm_content on every placement would shrink this bucket.
Watch Growth Analyst set up a new automation.
What Channel Attribution connects to.
PostHog / GA
ConnectedPulls visit and signup data tagged by UTM source.
UTM tracking
ConnectedReads the UTM convention already set on each placement.
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