Use cases
Online fashion and apparel shop
An independent clothing shop sells on its own website and runs social campaigns before each new collection.
Illustrative example – not a real customer
The portrait they want
Who comes from each collection launch post, which pieces they look at, and who comes back to buy.
Typical problems
- It is hard to tell which campaign brought visitors to a new collection.
- Size questions make people leave product pages without adding to cart.
- Visitors browse on the phone and buy later, so the path is hard to follow.
What applies today
Consented first-party tracking
The banner asks per purpose, nothing is recorded before a choice, and the server checks consent for every event.
Traffic, sources and pages reports
Visitors, sessions and page views over time, channels and campaigns, and the most viewed pages.
Standard and custom events
product_view, add_to_cart, checkout_start, purchase and more, plus custom.* events you declare in the console.
Several websites in one organization
Each website has its own reports, managed by the same team with roles.
Sample setup
Standard events
- page_view
- product_view
- add_to_cart
- checkout_start
- purchase
- search
Example custom events
custom.size_guide_viewWho opens the size guide before adding to cart.custom.wishlist_addProducts people save for later.
The portrait they can see today
- Sessions by campaign (utm_source, utm_campaign) for each collection launch.
- The most viewed product and collection pages.
- Whether data is arriving, and when the numbers were last updated.
Coming soon
- Coming soonNew and returning visitors, to see who comes back.
- Coming soonBuying signals from the events above (views, carts, checkouts, purchases).
- Coming soonAutomated traffic filtered out (in progress).
- Coming soonRevenue and orders by campaign.
- Coming soonGroups of returning and lapsed customers.
Try it on your own website
Create an account, add your website and publish your consent banner. No payment during the test phase.