STEP 2 Events

Basic information

The tracking code collects events, which are understood as every touch points with your brand (all customer’s activities).

  • Some events are collected by default - e.g.:

    • page visits
    • session start/end for anonymous users
    • system events like: message sent, newsletter open
  • Other events must be additionally sent – e.g.:

    • add to cart, transactions, add to favorite, button click (and anything else you need to track)
Detailed information:
  • Read more details about events, their types and places in Synerise in which you can find them

Check our Webinar

Watch our webinar to see how it works in practice and how events are built.

Source of Events

You can get events in multiple ways. Below you’ll find a list of possible sources:


Events can be tracked using our JS SDK to collect page visits, transactional events, add to favorites or anything else.

Detailed information:


You can use our API endpoints to track user activity by sending events to the Synerise Platform. To do this, you must create a Workspace API key and set the scope of the key.

Detailed information:


You can import historical events using the Synerise import tool (Shovel), which can be also used to import the customer’s base to the CRM.

Detailed information:


There is a group of events generated by Synerise eg. message.sent,

Construction of event

All events have at least a few important elements. All of them will be described below.

Screenshot presenting construction of event

  1. Label; Human-readable information about the activity, such as a page title.
  2. Time; The time when the event occurred.
  3. Action; Indicates the action type, in the form of context.activity, so, for example, page.visit means that a page has been visited.
  4. Parameters; This includes any parameter that may be required (it depends on the activity context, for example, the url of the page for a page.visit). A parameter is any detailed information about an action that you want to collect and use later in analytics.
  5. Customer ID; UUID is a reference to the customer that generated the activity.

Default and custom events

There is group of default events, which are the same in every workspace. These are e.g. events with actions:

  • page.visit

  • transaction.charge


  • message.sent

But Synerise is an open system – you can send whatever event you want, using custom events. If you want to send the event that a customer watched a video on your website, clicked a specific button, saw a specific banner, etc., you can send a custom event with the parameters that are important to you.

Example custom event:

SR.event.trackCustomEvent("video.played", { 
     'eventLabel': 'videoPlayed', 
     "name": "Promo Video Top", 
     "campaign": "Promo quarter 1", 
     "time": "4m", 
     "url": "", 
}, "Video Played") 

Transaction tracking

Why we need this integration: To collect transactional events in real-time. You will epecially transactional events for analyses of your ecommerce performance, creating more advanced segments for campaigns, creating abandoned basket campaign, train AI reommendations models eg. cross-sell.

There are basically two ways to integrate online transactions:

  1. By SDK

    • with dataLayer
    • with syneriseLayer
  2. By API (requires authorization)

Note: SKU in transaction frame have to be the same as product:retailer_part_no and product ID in product feed.
Detailed information:

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.



Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker