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

Northbeam MTA ledger skew is not Hyros pixel book-fork

How to run thisTraffic3 steps
CalculatorNorthbeam modeled-vs-platform gap · Calculator lives in the articleOpen

Divide |MTA $ − console $| by console $ on one Northbeam MTA window. That quotient is NB MTA skew %.

Pair: Modeled-vs-platform gap on Traffic. Hyros twin: pixel book-fork. Spend twin: platform vs modeled.

What you type

Modeled revenue $ — Northbeam multi-touch attributed revenue for the MTA window.

Platform revenue $ — Ad-console / last-touch booked revenue for that same window.

NB MTA skew % = |MTA $ − console $| ÷ console $ × 100. Fat NB MTA skew % usually means MTA mapping lag vs console reporting — chase that path; never invent an NB MTA skew chip.

What not to do

Skip inventing NB MTA skew %. Skip pasting a Hyros pixel book-fork export into Northbeam MTA seats. Skip folding bank cash into the console field. Skip blending channels when one MTA path owns the skew.

Related: Traffic, pixel book-fork, platform vs modeled, modeled-vs-cash.

Procedure

  1. Type modeled revenue $ and platform revenue $.
  2. Read NB MTA skew %.
  3. Chase MTA mapping when NB MTA skew % is material.

Failure modes

  • Inventing NB MTA skew %.
  • Pasting a Hyros pixel book-fork export into Northbeam MTA seats.
  • Folding spend-$ coverage into the MTA skew.

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

NB MTA skew %
|Modeled revenue $ − Platform revenue $| ÷ Platform revenue $ × 100.

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

FAQ

Is this Hyros modeled-vs-platform gap?
Different attribution book. [Modeled-vs-platform gap](/manuals/hyros-modeled-vs-platform-gap) scores Hyros pixel book-fork. Here you only skew Northbeam multi-touch attributed $ against ad-console booked $.
Is this Northbeam platform vs modeled?
Sibling Northbeam door with a spend third input. [Platform vs modeled](/manuals/northbeam-platform-vs-modeled) adds spend. This page is two-input |MTA $ − console $| ÷ console $.
What NB MTA skew % should I invent?
None. Pull modeled revenue $ (MTA) and platform revenue $ (console) from the same Northbeam MTA window.