Skip to article
ecomservices.io
Traffic · How to run this
TargetsCalculatorContributionNot on this page yetPlatformsCalculatorTrackersCalculatorAudiencesNot on this page yetLandingsCalculatorAttributionCalculatorAffiliatesCalculatorPacingNot on this page yetOptimisationCalculatorImplementationNot on this page yet

Library · Traffic · How to run this

Hyros call-path ROAS is not Rockerbox journey ROAS

How to run thisTraffic3 steps
CalculatorHyros path-length vs ROAS · Calculator lives in the articleOpen

Divide revenue $ by spend $ at the typed avg path length on one Hyros call-path window. That quotient is HY call-path ROAS.

Pair: Path-length vs ROAS on Traffic. Rockerbox twin: journey ROAS. Holdout twin: call-holdout.

What you type

Avg path length — Mean touches on the Hyros call-path bucket for the window.

Revenue $ — Attributed revenue $ in that same Hyros call-path bucket.

Spend $ — Media $ tied to that Hyros call-path bucket.

HY call-path ROAS = revenue ÷ spend. Soft HY call-path ROAS at a long path usually means call-map lag — chase that seat; never invent a ROAS chip.

What not to do

Never invent HY call-path ROAS. Never paste a Rockerbox or Northbeam path-length file into Hyros call-path fields. Never fold call-holdout lift or halo-vs-direct into path-length ROAS. Never mix path length from one week with spend from another.

Related: Traffic, Rockerbox journey ROAS, call-holdout, halo gap.

Procedure

  1. Type avg path length, revenue $, and spend $.
  2. Read HY call-path ROAS.
  3. Bid on call-path ROAS when HY call-path ROAS is the trusted book.

Failure modes

  • Inventing HY call-path ROAS.
  • Dumping a Rockerbox or Northbeam path-length file into Hyros call-path fields.
  • Folding Hyros call-holdout or halo-vs-direct into path-length ROAS.

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

HY call-path ROAS
Revenue $ ÷ Spend $ at the typed average path length (touches).

Work with us — We run this job on your accounts. Services

FAQ

Is this Rockerbox path-length vs ROAS?
Different attribution export. [Path-length vs ROAS](/manuals/rockerbox-path-length-vs-roas) reads Rockerbox journey ROAS. Here you only score Hyros call-path revenue ÷ spend at Hyros avg touches.
Is this Hyros incrementality holdout?
Holdout grain, not path ROAS. [Incrementality holdout](/manuals/hyros-incrementality-holdout) is call-holdout lift vs spend. This page is revenue ÷ spend at avg path length.
What HY call-path ROAS should I invent?
None. Type avg path length, revenue $, and spend $ from the same Hyros call-path window.