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

Triple Whale pixel-path ROAS is not Hyros call-path ROAS

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

On one Triple Whale pixel-path cut, compute attributed $ ÷ media $ at the typed mean touches. That quotient is TW pixel-path ROAS.

Pair: Path-length vs ROAS on Traffic. Hyros sibling: call-path ROAS. Holdout sibling: pixel-holdout.

What you type

Avg path length — Mean pixel touches in the Triple Whale path bucket for the cut.

Revenue $ — Attributed dollars Triple Whale booked to that same path bucket.

Spend $ — Media dollars tied to that Triple Whale pixel-path cut.

TW pixel-path ROAS = attributed ÷ media. Soft TW pixel-path ROAS on a long path usually means pixel-map lag — chase that seat; never invent a ROAS chip.

What not to do

Do not invent TW pixel-path ROAS. Do not load a Hyros call-path or Rockerbox journey export into Triple Whale pixel-path fields. Do not fold pixel-holdout lift or halo-vs-direct into path ROAS. Do not mix mean touches from one week with media $ from another.

Related: Traffic, Hyros call-path ROAS, pixel-holdout, halo gap.

Procedure

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

Failure modes

  • Inventing TW pixel-path ROAS.
  • Dumping a Hyros or Rockerbox path-length file into Triple Whale pixel-path fields.
  • Folding Triple Whale pixel-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

TW pixel-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 Hyros path-length vs ROAS?
No — that export lives under [Hyros call-path ROAS](/manuals/hyros-path-length-vs-roas). This door only reads Triple Whale pixel-path attributed $ ÷ media $ at Triple Whale mean touches.
Is this Triple Whale pixel-holdout?
Holdout lift, not path ROAS. [Incrementality holdout](/manuals/triple-whale-incrementality-holdout) is lift $ vs holdout spend. Here the quotient is attributed revenue ÷ media $ at a path-length bucket.
What TW pixel-path ROAS should I invent?
None. Copy mean touches, attributed $, and media $ from the same Triple Whale pixel-path cut.