Monolytics Event Tracking: Visual Implementation Guide

This guide demonstrates how to register events on your website. Events provide insights into what's happening on your site, such as user actions, system events, or errors.

Note that event names are case-sensitive, and recording two events with names differing only in case will result in two distinct events.

Ensure that you have installed the Monolytics code on your site. Depending on your installation method, the way to track events will also differ. Choose the method that suits you:

1) Installing the event code directly in the site's code

2) Configuring events using Google Tag Manager

If you need help - write us at [email protected]

After you have set up Monolytics, you can start tracking events using the monolytics_send_conversion() method. Below is an example of the code for transmitting an add_to_cart event.

if (window.monolytics_send_conversion) {
  monolytics_send_conversion('link_click_pro_analytics');
}

We recommend using the snake_case format for event names, where each space is replaced with an underscore (_), and words are written in lowercase.

You can use any names for your events, but it is better to use names that are understandable not only to you but also to your colleagues. Here are several examples of event names and the situations in which they are used:

• view_item - the user viewed a product card

• add_to_cart - the user added an item to the cart

• purchase - the user made a purchase on the site

• sign_up - user registration on the site

• sign_in - the user logged into their account on the site

• form_submit - the user submitted a form

If you use Google Tag Manager for handling marketing and analytical codes on your website, we also recommend using it for transmitting data to Monolytics.

In Google Tag Manager, you can set up the transmission of events in one of two ways:

By using events that are already being sent to the dataLayer

By configuring the data transmission yourself

If your website is already sending data to the dataLayer, you can quickly duplicate its transmission to Monolytics. To do this, you need to create a Custom HTML tag with settings similar to those you see in the screenshots below and connect it to the triggers of your custom events.

To do this, follow these steps:

• Go to the "Tags" tab and click the "New" button.

• In the window that opens, click on the pencil icon.

• In the next step, select the "Custom HTML" tag type.

• In the window that opens, paste the following code:

<script>
(function () {
  if (window.monolytics_send_conversion) {
    monolytics_send_conversion({{Event}});
  }
})();
</script>

Add a trigger to your tag. To complete this step, you need to know the names of the events being sent to the dataLayer. Suppose you have an add_to_cart event being sent. Then you would need a trigger with the matching settings.

Don't forget to name your tag and save the settings.

If your website does not utilize data transmission to the dataLayer, you can set up the data transmission to Monolytics by yourself. To transmit an event, you will need a Custom HTML tag and a corresponding trigger.

To do this, follow these steps:

• Go to the "Tags" tab and click the "New" button.

• In the window that opens, click on the pencil icon.

• Next, choose the "Custom HTML" tag type.

• In the window that opens, insert the following code. Remember to replace YOUR_EVENT_NAME with the name of the event you want to track.

<script>
(function () {
  if (window.monolytics_send_conversion) {
    monolytics_send_conversion('YOUR_EVENT_NAME');
  }
})();
</script>

Add a trigger to your tag. The trigger settings will be similar to those used when transmitting data to Google Analytics or Facebook Ads.

Monolytics displays information in real time in its reports, so you'll be able to see the first events within a few minutes.

Enjoy using it ;)

If you need help - write us at [email protected]

An event is only evidence when its meaning is confirmed by the owner of the flow. Name events for the outcome they observe (signup_completed, not button_click_3), and record what must be true for the event to fire.

Event properties and client/user properties scope an answer: which plan, which segment, which variant. Keep cardinality bounded, avoid personal data in property values, and treat identity as configuration, not an assumption - a browser client is not a verified person.

After registering an event, confirm it is actually observed: trigger the flow, then check that the event appears with the expected properties. An event that never fires is a data gap, not a zero.

Before asking for a number, check the readiness of the signal behind it. A readiness check records six things about the question you want to answer:

• Question - “What share of trials completed signup_completed in the last closed week?”

• Analysis unit - recording, browser client, or identified user; these are different units and are never silently substituted.

• Required signal - the signup_completed event, plus any property that scopes the segment.

• Required semantics, identity, and window - what the event is confirmed to observe, which unit carries it, and which closed period the answer covers.

• Current status - one of the six states below.

• Next step - the concrete action that moves the question toward an exact answer.

The six states are:

• Event observed and owner meaning confirmed - an exact answer is supported.

• Event missing or not observed - instrument it first.

• Owner meaning missing - confirm what the event actually observes.

• Identity or analysis unit unavailable - the question needs a different unit or configuration.

• Data window immature - wait for a closed period.

• Measurement primitive unsupported - the platform cannot express this question exactly today.

The example event name changes across SaaS, e-commerce, marketplace, and lead-generation products; the measurement contract stays identical.

Missing evidence is not zero. A model hypothesis is not an owner-confirmed outcome. Adding one event does not make every business question exact.

When Monolytics Assistant reports an evidence gap, it names the missing event, property, Survey, or recording. This guide is the implementation path for that next step.

For the tracking-code install itself, see the tracking code installation guide, and the event tracking FAQ for short answers.

Start free