Library · Traffic · How to run this
Call attribution is not LTV vs day-0 ROAS
Call-attributed orders ÷ orders make attribution %. Type both.
Pair: Call-attribution share on Traffic. ROAS: LTV vs day-0 ROAS. Cover: ad-account coverage gap.
What you type
Call-attributed orders — Orders Hyros credited to a call path in the window.
Orders — Orders in that same Hyros window.
Attribution % = call-attributed orders ÷ orders × 100. Fix call tracking when attribution % is thin or fat vs truth — do not invent an attribution chip.
What not to do
Do not invent attribution %. Do not mix LTV ROAS gaps into order counts. Do not treat ad-account coverage as call share. Do not average every skill when one owns the hole.
Related: Traffic, LTV vs day-0 ROAS, ad-account coverage gap, refund-adjusted ROAS gap.
Procedure
- Type call-attributed orders and orders.
- Read attribution %.
- Fix call tracking when attribution % is material.
Failure modes
- Inventing attribution %.
- Mixing LTV ROAS gaps into order counts.
- Treating ad-account coverage as call share.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Call-attribution share %
- Call-attributed orders ÷ Orders × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this LTV vs day-0 ROAS?
- Sibling Hyros book. [LTV vs day-0 ROAS](/manuals/hyros-ltv-vs-day0-roas) is ROAS points. This page is call-attributed orders ÷ orders.
- Is this ad-account coverage gap?
- Related seat cover. [Ad-account coverage gap](/manuals/hyros-ad-account-coverage-gap) is connected vs live accounts. This page is call-attribution share.
- What attribution % should I invent?
- None. Type call-attributed orders and orders from the same Hyros window.