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

CAKE SubID skew is not BuyGoods SubID skew

How to run thisTraffic3 steps
CalculatorCAKE SubID-mismatch share · Calculator lives in the articleOpen

Weight mismatched conversions by conversions on one CAKE offer window. That weight is CK SubID mismatch %.

Pair: SubID-mismatch share on Traffic. BuyGoods twin: BuyGoods mismatch. Affise twin: Affise mismatch.

What you type

SubID mismatches — CAKE conversions whose SubID did not match the click in the offer window.

Conversions — CAKE conversions booked in that same offer window.

CK SubID mismatch % = mismatched ÷ conversions × 100. A fat CK SubID mismatch % usually means a postback or landing param broke on that offer — fix the CAKE seat; never invent a CK SubID mismatch chip.

What not to do

Never invent CK SubID mismatch %. Never load BuyGoods or Affise SubID rows into CAKE inputs. Never fold creative-reject share into mismatch. Never average every offer when one partner owns the skew.

Related: Traffic, BuyGoods mismatch, Affise mismatch, creative-reject.

Procedure

  1. Type SubID mismatches and conversions.
  2. Read CK SubID mismatch %.
  3. Chase partner postback / landing params when CK SubID mismatch % is material.

Failure modes

  • Inventing CK SubID mismatch %.
  • Loading BuyGoods or Affise SubID rows into CAKE inputs.
  • Folding creative-reject share into mismatch.

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

CK SubID mismatch %
SubID-mismatched conversions ÷ conversions × 100 on one CAKE offer window.

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

FAQ

Is this BuyGoods SubID-mismatch share?
Offer ledger vs BuyGoods. [SubID-mismatch share](/manuals/buygoods-subid-mismatch-share) stays on BuyGoods. Mismatch counts never leave CAKE here.
Is this Affise SubID-mismatch share?
Separate network book. [SubID-mismatch share](/manuals/affise-subid-mismatch-share) stays on Affise. CAKE owns every count here.
What CK SubID mismatch % should I invent?
None. Pull mismatched conversions and conversions from the same CAKE offer window.