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 phone-path device stitch vs single-device is not Northbeam device-hop

How to run thisTraffic3 steps
CalculatorHyros cross-device gap · Calculator lives in the articleOpen

Grab one Hyros phone-path stitch book. Take |cross-device $ − single-device $| over single-device $. That quotient is HY cross-device gap % — Northbeam device-hop books never feed this call path.

Pair: Cross-device gap on Traffic. Northbeam twin: NB cross-device. Creator twin: HY influencer-paid.

Phone-path stitch inputs

Cross-device revenue $ — Hyros dollars tagged journeys that switched devices (or phone ↔ web) before purchase.

Single-device revenue $ — Hyros dollars tagged journeys that stayed on one device on that same book.

HY cross-device gap % = |cross-device $ − single-device $| ÷ single-device $ × 100. When HY cross-device gap % climbs, reconcile phone-path identity stitching — leave empty chips empty.

What not to do

Skip inventing HY cross-device gap %. Skip loading a Northbeam device-hop CSV into Hyros boxes. Skip stuffing influencer $ into the cross-device field. Skip blending books when one Hyros phone-path stitch book owns the swing.

Related: Traffic, NB cross-device, HY influencer-paid, HY multi-touch.

Procedure

  1. Type cross-device revenue $ and single-device revenue $.
  2. Read HY cross-device gap %.
  3. Reconcile phone-path identity stitching when HY cross-device gap % is material.

Failure modes

  • Inventing HY cross-device gap %.
  • Pasting a Northbeam device-hop file into Hyros boxes.
  • Folding influencer $ into the cross-device field.

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 cross-device gap %
|Cross-device $ − Single-device $| ÷ Single-device $ × 100 on one Hyros phone-path stitch book.

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

FAQ

Is this Northbeam cross-device gap?
Hyros phone-path stitch book vs Northbeam device-hop book. [Cross-device gap](/manuals/northbeam-cross-device-gap) stays on Northbeam. Cross-device / single-device dollars belong here.
Is this Hyros influencer-vs-paid gap?
Device stitch vs creator vs paid media. [Influencer-vs-paid gap](/manuals/hyros-influencer-vs-paid-gap) stacks influencer against paid. Here you only compare cross-device $ to single-device $.
What HY cross-device gap % should I invent?
None. Source cross-device revenue $ and single-device revenue $ from the same Hyros phone-path stitch book.