Library · Traffic · How to run this
Hyros touch-fork is not Triple Whale path-gap
Line up first-touch $ against last-touch $. Take |first − last| ÷ last. That is touch-fork %.
Pair: First-vs-last-touch gap on Traffic. Triple Whale twin: path-gap. Mix twin: new-vs-returning.
What you type
First-touch $ — Hyros revenue credited to the first touch in the named span.
Last-touch $ — Hyros revenue credited to the last touch in that same span.
Touch-fork % = |first − last| ÷ last × 100. When touch-fork % runs hot, revisit Hyros assist maps — never invent a touch-fork chip.
What not to do
Skip inventing touch-fork %. Skip dropping a Triple Whale or Rockerbox export into Hyros fields. Skip treating new-vs-returning dollars as first vs last touch. Skip merging spans when one campaign owns the skew.
Related: Traffic, path-gap, new-vs-returning, assisted share.
Procedure
- Type first-touch $ and last-touch $.
- Read gap %.
- Revisit assist maps when gap % is material.
Failure modes
- Inventing gap %.
- Dropping a Triple Whale or Rockerbox export into Hyros fields.
- Treating new-vs-returning dollars as first vs last touch.
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
- First-vs-last-touch gap %
- |First-touch $ − Last-touch $| ÷ Last-touch $ × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Triple Whale first-vs-last-touch gap?
- Different attribution book. [First-vs-last-touch gap](/manuals/triple-whale-first-vs-last-touch-gap) reads Triple Whale path dollars. Here you only line up Hyros first-touch $ against last-touch $.
- Is this Hyros new-vs-returning share?
- Sibling Hyros mix. [New-vs-returning share](/manuals/hyros-new-vs-returning-share) is first-buyer vs repeat-buyer. This page pits first-touch credit against last-touch credit.
- What touch-fork % should I invent?
- None. Pull first-touch $ and last-touch $ from the same Hyros span.