Library · Traffic · How to run this
CAKE offer browser-fence ledger is not BuyGoods hop browser-match book
Mount one CAKE offer browser-fence ledger. Sum sales whose browser tag misses the offer browser fence. Ratio that sum to sales the ledger scored. Scale by 100 for CK browser-mismatch %. BuyGoods hop browser-match books, CAKE offer device-fence ledgers, and offer geo-fence ledgers never land on this browser-fence ledger.
Pair: Browser-mismatch share under Traffic. BuyGoods twin: BG browser-mismatch. Device twin: CK device-mismatch.
Offer browser-fence fields
Browser-mismatched conversions — CAKE sales whose browser tag misses the offer browser fence on the offer browser-fence ledger.
Conversions scored — CAKE sales that ledger scored in the same offer slice.
CK browser-mismatch % = browser-mismatched conversions ÷ conversions scored × 100. When CK browser-mismatch % swells, retune the offer browser fence on that ledger — blank chips stay blank.
Guardrails
Skip inventing CK browser-mismatch %. Skip folding device-fence or geo-fence rows into the browser tally. Skip dumping BuyGoods hop browser CSVs into CAKE offer boxes. Skip blending offers when one CAKE offer browser-fence ledger owns the miss pile.
Related: Traffic, BG browser-mismatch, CK device-mismatch, CK geo-mismatch.
Procedure
- Type browser-mismatched conversions and conversions scored.
- Read CK browser-mismatch %.
- Retune the offer browser fence when CK browser-mismatch % swells.
Failure modes
- Inventing CK browser-mismatch %.
- Folding device-fence or geo-fence rows into the browser tally.
- Dumping BuyGoods hop browser CSVs into CAKE offer boxes.
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 browser-mismatch %
- Browser-mismatched conversions ÷ conversions scored × 100 on one CAKE offer browser-fence ledger.
Work with us — We run this job on your accounts. Services
FAQ
- Is this BuyGoods browser-mismatch share?
- CAKE offer browser-fence ledger vs BuyGoods hop browser-match book. [Browser-mismatch share](/manuals/buygoods-browser-mismatch-share) stays on BuyGoods. Browser fence misses / scored sales for CAKE belong on this offer ledger.
- Is this CAKE device-mismatch share?
- Offer browser-fence ledger vs offer device-fence ledger. [Device-mismatch share](/manuals/cake-device-mismatch-share) ratios device fence misses. Here you only tally sales whose browser tag misses the offer browser fence.
- What CK browser-mismatch % should I invent?
- None. Pull browser fence misses and scored sales from the same CAKE offer browser-fence ledger.