SupportHow Store Insights work
Read Customer App traffic, cart activity, and conversion results.
How this fits into Lead360Explore the white label platformDeliver branded customer experiences and campaign destinations for client businesses.- 01
How Lead360 helps
- 02
Read the summary
- 03
Follow the funnel
- 04
Ask360 analysis is read only
How Lead360 helps
Store Insights helps teams understand how customers interact with published app experiences by presenting measured activity and trends. It supports informed iteration when staff compare the correct date range, audience, destination, and business outcome instead of treating a single metric as proof.
When to use this area
Use Store Insights after publishing customer app content or a campaign to review reach, engagement, and changes over time.
Before you begin
- Define the decision the report should support.
- Choose a date range that includes the relevant launch and comparison period.
- Confirm tracking and event definitions before interpreting totals.
Read the summary
- Click Rate compares tracked clicks with page views.
- Cart Opens counts recorded cart sessions; Conversions and Abandonment use those sessions.
- Average Cart Time and Active Users describe recorded sessions and identified contacts for the selected period.
Follow the funnel
- Compare Page Views, Product Views, Add to Cart, Checkout, and Completed in order.
- The largest drop shows where to investigate, but it does not by itself prove why customers stopped.
- Use Top Products to see which catalogue items received the most recorded views.
Ask360 analysis is read only
Ask360 can return a read-only Ask360 report for up to the last 365 days, explain every metric, and identify the largest observed funnel drop. It never changes campaigns, products, contacts, carts, or payments from this tab.
Confirm the result
A completed How Store Insights work workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Compare trends across equivalent periods.
- Check source events or destination records for important conclusions.
- Document any filter, attribution, or data-latency limitation alongside the result.
Troubleshooting
Recent activity is missing
Check the report timezone, date range, event processing delay, publication time, and whether tracking was active on the customer destination.
Two reports disagree
Compare metric definitions, filters, attribution windows, deduplication, and included channels before reconciling totals.
Frequently asked questions
What should I confirm before using How Store Insights work?
Define the decision the report should support. Choose a date range that includes the relevant launch and comparison period. Confirm tracking and event definitions before interpreting totals. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with How Store Insights work?
Store Insights helps teams understand how customers interact with published app experiences by presenting measured activity and trends. It supports informed iteration when staff compare the correct date range, audience, destination, and business outcome instead of treating a single metric as proof.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.