Behavior Analytics for E-commerce Managers — A Weekly Operating Routine
E-commerce managers juggle merchandising, campaigns, and site changes. Learn a weekly routine using funnels, heatmaps, session recordings, and error tracking to find what is costing sales and fix it in order of impact.
Short answer: each week, check the purchase funnel by device, find the step that changed most, watch a dozen sessions that stopped there, and check for new errors on cart and checkout. Before and after every campaign and site change, repeat the check. That routine finds most of what is quietly costing a store sales.
Table of Contents
- What Your Platform Does Not Show
- The Store Funnel
- A Weekly Routine
- Around Campaigns and Sales
- After Site Changes
- Reporting Upward
- Key Takeaways
What Your Platform Does Not Show
Your commerce platform is the ledger: orders, revenue, products, customers. It is accurate and it stops at the transaction.
It does not show:
- What shoppers looked at and ignored on a product page
- Why a cart was abandoned
- That a coupon field stopped working on Tuesday
- That the add-to-cart button is hidden on some phones
- Which campaign's visitors leave within seconds
Those are behavior questions, and they are where most recoverable revenue is.
The Store Funnel
Set this up once.
- Product page viewed
- Added to cart
- Cart viewed
- Checkout started
- Order completed
Track add-to-cart and order completion as events, so they are counted on confirmation and not on a click:
deepsync("track", "purchase_completed", { value: 2499, currency: "INR" });With a value attached, the Conversions view reports revenue attributed to the goal (goals). Compare the funnel by device, and by new and returning shoppers.
Platform notes: on WooCommerce the whole checkout runs on your domain and is recorded. On Shopify plans other than Plus, the hosted checkout does not run theme code, so recording stops at the checkout boundary (Shopify install).
A Weekly Routine
Step 1: Numbers (10 minutes)
- Funnel step conversion against last week and the four-week average
- Mobile and desktop separately
- The step that moved most
Step 2: Sessions (20 minutes)
- Open the sessions that dropped at that step. In DeepSync, click the step's drop-off number.
- Watch ten to twelve, mostly mobile.
- Note what each shopper did last.
Step 3: Errors and speed (10 minutes)
- New JavaScript errors on product, cart, and checkout pages, by sessions affected
- Rage clicks on those pages
- Real-user load time for your top product and landing pages on mobile
Step 4: One fix (5 minutes)
- Choose the most frequent, cheapest problem. Assign it.
Step 5: Check last week's fix (5 minutes)
- Did the step improve for the affected device?
Common findings by step:
| Step | Frequent cause |
|---|---|
| Product → cart | Size or variant confusion, images that will not zoom, button below the fold on mobile |
| Cart → checkout | Shipping cost surprise, coupon not applying, minimum order unclear |
| Checkout → order | Forced account, payment failure, long form, session expiry during bank authentication |
Around Campaigns and Sales
Before launch
- Open the landing page on a phone, on mobile data.
- Place a test order using the campaign's coupon.
- Check that links carry the right UTM tags (UTM guide).
- Note baseline conversion.
First hour
- Watch real sessions from the campaign. With live session view on Pro and above, you can watch as visitors arrive.
- Check the coupon is applying.
- Check errors on cart and checkout.
During
- Compare conversion for campaign traffic with normal traffic.
- Watch bounced sessions from the campaign to see whether the page matches the ad (paid traffic that does not convert).
After
- Conversion and revenue by campaign, from attribution.
- What campaign shoppers looked at and bought.
- Write down what to change next time.
A sale is the worst time to discover a broken coupon. It is also when it is most likely to be discovered, because traffic is highest. Check first.
After Site Changes
Theme updates, new apps or plugins, and new payment options are the usual cause of a sudden drop.
- Take a funnel baseline before the change.
- Check errors on key pages within the hour.
- Place a test order on mobile and desktop.
- Compare the funnel for the following days.
- Audit page weight after adding any app. Each one adds scripts (script impact).
Reporting Upward
Leadership wants outcomes and reasons, not charts.
| Instead of | Report |
|---|---|
| "Conversion was 2.1%" | "Mobile cart-to-checkout fell four points after the theme update" |
| "We looked at heatmaps" | "Six of twelve shoppers left when shipping cost appeared; we now show it on the cart" |
| "Bounce rate is high" | "Campaign visitors leave in seconds because the page headline does not match the ad" |
| A list of metrics | One finding, one fix, one result |
Attach a short recording. Thirty seconds of a real shopper failing to pay makes a case that no slide can.
Place one test order a week on your phone
Using your own store as a customer, on a mobile connection, catches problems before the data does.
Key Takeaways
- Your platform is the ledger; behavior data explains it.
- Run a fifty-minute weekly check on funnel, sessions, and errors.
- Verify coupons and checkout before and during campaigns.
- Report one finding, one fix, and one result.
Conclusion
Most stores are losing sales to a small number of fixable problems. A weekly routine finds them one at a time, and that steady work is what moves conversion.
Frequently Asked Questions
Related articles
Stay in the loop
Get the latest insights on product analytics and user behavior delivered to your inbox.



