Seven steps you can run yourself. Each step has a formula, a benchmark, and a red flag. By the end you will have a defensible number for monthly revenue leaking out of your anonymous traffic.
Each step builds on the one before. Step 1 sizes the universe. Step 2 narrows to the recoverable cohort. Steps 3–6 explain the failure modes. Step 7 puts a dollar on the leak.
Step 01 of 07
Quantify your anonymous traffic share
Do this
Pull session count and identified-session count for the last 30 days. Identified = sessions where email, phone, or known login attached at any point.
anonymous % = 1 − (identified sessions / total sessions)
Benchmark
Most stores: 92–98%. Below 90% means strong identity capture; above 96% means severe leakage exposure.
Red flag
If you cannot answer this question in your analytics tool, you do not have identity tracking instrumented. Stop here, fix that first.
Step 02 of 07
Find the intent-weighted bounce
Do this
Filter sessions to "engaged" — 3+ pageviews OR 60+ second dwell OR scroll depth > 60%. Compute bounce rate within that cohort. Compare against unfiltered bounce rate.
high-intent bounce = engaged sessions that bounced / engaged sessions
Benchmark
High-intent bounce > 50% is leakage. Healthy stores sit at 30–45%.
Red flag
A flat bounce rate hides this. The cohort that browsed but left is what you can recover.
Step 03 of 07
Measure identity capture rate by step
Do this
Plot identification rate at each funnel step: landing → engaged → cart → checkout → purchase. Use the Identity Signal Heatmap framework.
capture at step N = identified sessions at step N / sessions reaching step N
Benchmark
Exit-intent popup: 15–20%. Cart save: +5%. Checkout: +8–12%. If any step is < 5% gain, it is broken or missing.
Red flag
Most stores have one step doing 80% of the capture. Fragile. Add a second.
Step 04 of 07
Walk the cart-abandonment funnel
Do this
Build a funnel: add-to-cart → checkout-start → checkout-complete. Compute drop-off at each step. Cross-reference identified vs anonymous within each step.
Industry average: ~70%. Below 60% is good. Above 75% is leakage.
Red flag
If anonymous cart adders are 80%+ of total cart adders and you have no identity-capture mechanism on the cart page, that is the leak.
Step 05 of 07
Audit time-to-first-touch after exit
Do this
For sessions that captured identity but did not convert, measure median time from exit to first follow-up message (email, SMS, ad).
time-to-first-touch = median(timestamp of first follow-up − exit timestamp)
Benchmark
Under 30 minutes is competitive. Next-day batch is leakage. The bounce window passes in seconds; the recovery window passes in hours.
Red flag
If your ESP fires cart-abandonment emails the next morning, you are losing the recovery to anyone who acts in the same session.
Step 06 of 07
Find cross-channel attribution gaps
Do this
Pick 50 conversions at random. Trace the touch chain: ad → site → email → SMS → purchase. Check whether your attribution tool can connect every step.
% of conversions with full chain visibility
Benchmark
Below 60% chain visibility means you cannot prove which channel converted. You are guessing on spend.
Red flag
Anonymous-to-known transitions are the most common break point. If web events do not stitch to email opens to SMS clicks, you have parallel siloed analytics.
Step 07 of 07
Quantify ROAS leakage on retargeting
Do this
Pull retargeting ad spend and conversions for the last 30 days. Compare cost per conversion against owned-channel cost per conversion (email, SMS to identified users).
leakage = retargeting CAC − owned-channel CAC, × converted users that could have been owned
Benchmark
If owned CAC < 1/5 of retargeting CAC, every identified user you fail to capture is paid retargeting tax.
Red flag
The cheapest channel is the one you own. The leak is failing to convert anonymous to owned before retargeting becomes the only option.
Plan a half day for data pulls and one day for the math. The bottleneck is usually identity tracking — if it is not instrumented, you spend that day fixing instrumentation before you can audit anything.
What if I do not have identity events instrumented?
Start with steps 1, 2, and 4 — those work on session-level data alone. Steps 3, 5, and 6 require identity tracking. The audit will surface that gap as the first thing to fix.
Can I just have you do it?
Yes. The free 12-hr ROI audit runs this exact framework on your store and returns a 2-slide breakdown. Faster, more thorough, and benchmarked against comparable stores. Linked at the bottom.
Are these benchmarks reliable?
They are typical ranges for mid-market DTC ecommerce on Shopify. Your numbers will vary by category, AOV, and traffic mix. Use them to flag obvious leaks (anything 2×+ outside the range), not to grade incremental performance.
What do I do once I have the leak number?
Pick the largest leak category and fix the highest-leverage step. The methodology page covers how to size each leak; the metrics page covers what to track post-fix; the mechanism page covers how Convertive executes the fix in real time.