Site tracking
Turn on visit measurement for your store, install the script on a custom-built site and check that every event arrives.
Connecting your store sends us its orders, customers and catalog. It does not tell us what your visitors do before they buy. That is the job of site tracking. A small script measures page views, viewed products, add to carts and checkout starts, then sends them to us.
This information feeds several Fullmetrix features.
- Live activity, which shows what is happening on your site right now.
- The journey of each contact, with the pages and products they viewed.
- Segments built on actions, such as "viewed a product without buying it".
- WhatsApp automations triggered by an abandoned cart, a started checkout or a viewed product.
To open the setting, click Settings in the sidebar, then the Tracking tab. The page is titled Site tracking.
What you need to connect first
Site tracking is set store by store, so you need at least one connected store. Without a store, the page shows No store to track and a View integrations button that takes you to your platform connection.
If your organization has several stores, a row of buttons appears below the title, one per store, with the site address. A green dot means tracking is active on that store. Click a store to show its settings.
Turn tracking on or off
At the top right, a box shows Tracking active with a green dot, or Tracking disabled with a grey dot. The switch next to it turns collection on or off for the selected store.
Tracking is active as soon as your store connects. You have nothing to do to start it.
To turn it off, click the switch. The Disable tracking? window warns you that any script still on the site will no longer record new events. Click Disable to confirm, or Cancel. The message Site tracking disabled confirms it.
Once tracking is off, we reject new events from this store. Data already received is kept and diagnostics remain available. To resume collection, click the switch again. The message Site tracking enabled appears, with no confirmation window.
What you lose by turning tracking off
While it is off, live activity stays empty, new visitor journeys are not recorded, and WhatsApp automations that depend on a cart or a visit no longer trigger. Visits from that period cannot be recovered.
Install tracking on your site
In most cases, you have nothing to install. The large card on the left tells you how tracking is loaded on your store.
The card is titled with your platform name followed by module, for example PrestaShop module. The Fullmetrix module you installed to connect the store also loads tracking on all its pages. You have no code to add.
If diagnostics receive nothing, check that the module is installed and active in your store admin. Your platform guide is in Platforms.
Install the code on a custom site
The Headless installation card shows the Installation code, a single line specific to your store that looks like this.
<script async src="https://.../t.js?key=YOUR_CODE" data-auto-spa="true"></script>Always copy the code shown in the app, because it contains your store's connection code.
Copy the code
Click Copy to the right of the code. The button shows Copied.
Paste it into your site
The easiest way is Google Tag Manager. Create a Custom HTML tag, paste the code, and fire it on all pages once the visitor has accepted cookies. You can also paste the code in the head of every page of your site.
Check delivery
Open your site in a browser, view a product, add it to the cart and start a checkout. Then go back to the Site tracking page and look at the Event delivery card.
If someone else will install the code, click Send instructions to my developer. Enter their address in Developer email, then click Send instructions. We email them the code, the list of supported events and the verification steps. The message Instructions sent to followed by their address confirms it.
If your site already sends Google Analytics 4 ecommerce events to the dataLayer, such as view_item, add_to_cart, begin_checkout or purchase, the script picks them up without extra code. It also follows page changes on sites that do not reload the page on each click.
To go back to installation through the module, click Return to automatic mode. This button does not show when a separate site is detected.
Cookie consent stays managed by your site
Fullmetrix does not show a cookie banner. Your consent tool decides when measurement scripts may load. On a custom site, fire the Fullmetrix code after the visitor agrees, like your other measurement tools. To learn more, read GDPR and privacy.
Check that events arrive
The Event delivery card shows what we received from your site over the last 30 days. It refreshes by itself every ten seconds. The circular arrows icon at the top right forces an immediate refresh.
Below the title, the text reads Active. Last event followed by a duration and ago when an event arrived recently. Otherwise, it shows how many of the seven expected events were received, for example 5/7 events received. The progress bar follows the same count.
The list details the seven events. A green tick and a number mean the event was received, with the count over 30 days. An empty circle means it has not been received yet.
| Event | What it measures |
|---|---|
page_viewed | A visitor opens a page |
product_viewed | A visitor opens a product page |
identify | A visitor is recognized, for example by logging in or entering their email or phone |
added_to_cart | A product is added to the cart |
cart_updated | The cart is changed or viewed |
checkout_started | A visitor starts checkout |
order_completed | An order is placed |
It is normal for some events to be missing on a store with few visits, or right after activation. order_completed only appears after an order, and identify only after a visitor gives their email or phone. Run a full journey yourself to trigger them.
Two messages can replace the list. Tracking is disabled. New events are rejected by the API. means the switch is off. Diagnostics are temporarily unavailable. means we cannot read the events right now. Your data is not lost, try again a few minutes later.
Visits from bots, such as search engines and automated test tools, are ignored by the script. They do not appear in diagnostics.
Restrict allowed domains
The Allowed domains card prevents another site from using your store's code to send us fake events. When the list is filled in, we only accept events coming from these addresses.
The field is prefilled with your site address, but nothing is restricted until you click Save. To add several domains, separate them with commas, for example https://www.mystore.com, https://mystore.com. You can enter up to ten. If you leave out https://, we add it. The message Allowed domains saved confirms it.
List every version of your address
https://www.mystore.com and https://mystore.com are two different domains. If your site is reachable under both, or on a subdomain per country, add each address. Otherwise visits on the forgotten address are no longer counted.
To lift every restriction, empty the field then click Save. If none of the addresses you typed is valid, the message Aucune origine valide ("no valid origin") appears and nothing is saved.