Library · Traffic · How to run this
Northbeam MTA call credit is not Hyros call-path attribution
On one Northbeam MTA window, put call-attributed orders over orders. That quotient is NB call %.
Pair: Call-attribution share on Traffic. Hyros twin: call-attribution. ROAS twin: LTV vs day-0.
What you type
Call-attributed orders — Orders Northbeam credits to an MTA call touch in the window.
Orders — Orders in that same Northbeam MTA window.
NB call % = call-attributed orders ÷ orders × 100. A thin NB call % usually means call-touch coverage holes on that MTA cut — chase those paths; never invent an NB call chip.
What not to do
Skip inventing NB call %. Skip pasting a Hyros call-path export into Northbeam fields. Skip folding LTV ROAS gaps or email-attribution counts into call orders. Skip blending models when one MTA cut owns the call pile.
Related: Traffic, Hyros call-attribution, LTV vs day-0, email-attribution.
Procedure
- Type call-attributed orders and orders.
- Read NB call %.
- Chase call-touch coverage when NB call % is material.
Failure modes
- Inventing NB call %.
- Pasting a Hyros call-path export into Northbeam fields.
- Mixing LTV ROAS gaps into order counts.
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 call %
- Call-attributed orders ÷ Orders × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Hyros call-attribution share?
- Call-path day-0 vs Northbeam MTA call touch. [Call-attribution share](/manuals/hyros-call-attribution-share) reads Hyros. Here both order counts stay on one Northbeam MTA window.
- Is this Northbeam LTV vs day-0 ROAS?
- ROAS points vs call order share. [LTV vs day-0 ROAS](/manuals/northbeam-ltv-vs-day0-roas) is ROAS. This page is call-attributed orders ÷ orders.
- What NB call % should I invent?
- None. Pull call-attributed orders and orders from the same Northbeam MTA window.