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