Use cases
Cosmetics and beauty shop
A small cosmetics brand sells skincare online and publishes routines and ingredient guides on its blog.
Illustrative example – not a real customer
The portrait they want
Which guides and routines bring readers, which products they research, and whether they return.
Typical problems
- Customers read a lot before buying, across blog posts and product pages.
- It is unclear which guides lead to product interest.
- The team wants to respect privacy because customers care about it.
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
- purchase
- search
- sign_up
Example custom events
custom.routine_quiz_completeVisitors who finish a skin routine quiz.custom.ingredient_filterWhich ingredient filters people use.
The portrait they can see today
- Top blog posts and product pages side by side.
- Sessions by referring website and channel.
- Consent is asked per purpose, so only visitors who accepted analytics are counted.
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 soonCustomer profiles for signed-in buyers.
- Coming soonReports on repeat purchases.
Try it on your own website
Create an account, add your website and publish your consent banner. No payment during the test phase.