What CDP collects: events
The events the Monfri script sends by itself on stores, news sites and any other site, how orders arrive from the store, and the live Events screen.
An event is one thing a visitor did: opened a page, looked at a product, added it to the cart, read an article. The Monfri script sends events by itself — you do not tag buttons or write code. What it sends depends on the type of your site.
On every site
| Event | When |
|---|---|
Page view (type page) |
Every page the visitor opens. |
Consent Updated |
The visitor accepted or declined in the consent banner. |
Identify (type identify) |
The visitor becomes known — signs in, or leaves an e-mail address at checkout or in a form the platform reports. See Profiles. |
On an online store
On CloudCart, WooCommerce, Shopify and Magento, the script knows the store's pages and sends:
| Event | When |
|---|---|
Product Viewed, Product Quick Viewed |
A product page, or a product's quick view, is opened. |
Product List Viewed, Product Clicked |
A category or a list of products is opened; a product in it is clicked. |
Products Searched |
The store's search is used. |
Product Added, Product Removed, Cart Viewed, Cart Updated |
The cart changes or is opened. |
Checkout Started, Checkout Step Viewed, Checkout Step Completed, Shipping Info Entered, Payment Info Entered |
The steps of the checkout. |
Coupon Entered, Coupon Applied, Coupon Removed |
A discount code is used. |
Order Completed |
The thank-you page after an order. |
Product Engaged, Page Engaged |
How long and how far a visitor looked at a page, sent when they leave it. |
Product Shared, Promotion Clicked, Newsletter Subscribed |
Sharing, a banner, a newsletter sign-up. |
Orders also come straight from the store once it is connected — including orders placed by phone or by an admin, and their later changes. Monfri recognises an order that arrived both ways and keeps it once. See Connect your online store.
On a news site
| Event | When |
|---|---|
Article Viewed |
An article is opened. |
Article Engaged |
The reader scrolled 25 % or stayed 15 seconds. |
Article Read |
The reader scrolled 50 % or stayed 25 seconds. |
Article Reading Session |
When the reader leaves: the time on the article and how far they got. |
Article Shared |
A share button was clicked. |
Which of these are sent is set in Settings → Tracking & SDK → Advanced tracking configuration → Events — see Sites in CDP: the domains that send you data.
From other Monfri services
Web push and the chatbot add their own events, such as Push Subscribed and Assistant Proactive Shown, so you can use them in segments.
Watch events arrive
In CDP, open Audience → Events. The list shows the last 100 events as they arrive, with Live at the top while it is connected.
| Column | What it shows |
|---|---|
| Event | The event's name. |
| Type | page, track (a named event) or identify. |
| Profile | Who did it — a name or e-mail when the visitor is known. |
| Properties | The details, such as the product or the order total. |
| Time | How long ago. |
Untick Real-time to stop the stream and read; Refresh then loads the latest 100. Clear empties the list on your screen — nothing is deleted.
Good to know
- Your developers can send events of their own with the same script; ask us at [email protected] for the details.
- Automated browsers, such as test robots, send nothing, and known bots are filtered out.
- What happens before the visitor answers the consent banner depends on the consent mode — see Consent and cookies on your site.
If something doesn't work
No events yet
Nothing has arrived. See Check that tracking works.
Store events are missing, page views arrive
The script does not recognise the store. In Tracking & SDK, set the site type to E-commerce and choose the Platform, then click Update script.
Connecting... stays on
The live connection is blocked — often by a company firewall or a browser extension. Untick Real-time and use Refresh.