ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Events: list of events

 

Learn from this article about:

What is an event

Timestamp

Payload

Types of events possible to track

What is an event

Events are collected behaviours of a customer.

Different types of information can be fetched depending on the event type.

Each event contains:

  • Timestamp (time and date),
  • Payload (varies for each event type, more details below).

 

Timestamp

The timestamp is recorded in the following format yyyy-mm-dd hh:mm:ss

In most cases, it shows when exactly an event happened in the browser (uses the clock set up in the browser). 

Each time the event reaches the server there is also a reception side noted on the server-side that helps to verify timestamp noted in the browser. 

Remember: By default, Meiro Events uses time recorded by the browser.  

It is because it is the most precise as information travelling to the server may have a delay ( for example due to poor internet connection or other distractions).

Remember: But in cases when Meiro Events detects a discrepancy between time recorded by the browser versus time recorded by the server, the time recorded by the server will be used as the most accurate. 

For example, it can happen that a user does not have time set up correctly on his device. In those cases, time noted by the server is perceived as the most correct one. 

Timestamp from the browser is translated to UTC timezone and to the local timezone on the server-side.

 

Payload

Payload varies for each type of event. This is the data that is collected for a particular event. 

For each event we know:

  • User ID,
  • Session ID,
  • Fingerprint (unique identifier).

 

Types of events possible to track

 

Page view

 

{  
type: "page_view",
timestamp: "2019-05-05T18:45:41.062Z",
version: "1.2.0",
payload:
{
page_title: "Customer Data Platform that helps you target precisely",
url: "https://meiro.io/",
referrer: "https://www.google.com/search?q=meiro",
},
user_id: "unique user id",
fingerprint: "fingerprint MD5 hash",
session_id: "base64 session id (timestamp&user_id)",
external_id: "some id string"
// OPTIONAL ATTRIBUTE, OCCURS WHEN CONFIGURED
}

 

The page view event can track on all pages where SDK is deployed.

Data collected from this event:

  • Page title, 
  • Page URL, 
  • Referrer.

The page view event will be automatically connected to the website after deployment.

 

Learn more: How to set page view on the application and how to pass additional data.

    {
      type: "outbound_link_click",
      timestamp: "2019-05-05T18:45:41.062Z",
      version: "1.3.0",
      payload: {
        page_title: "Contact | Meiro",
        url: "https://www.meiro.io/contact",
        referrer: "https://www.google.com/search?q=meiro",
        href: "https://www.linkedin.com/company/meirocdp/"
      },
      user_id: "unique user id",
      fingerprint: "fingerprint MD5 hash",
      session_id: "base64 session id (timestamp&user_id)",
      external_id: "some id string" 
    // OPTIONAL ATTRIBUTE, OCCURS WHEN CONFIGURED }

    Data collected from this event:

    • Page title, 
    • URL, 
    • Referrer,
    • Hypertext REFerence (The HTML code used to create a link to another page).

     

    The outbound link click event will be automatically connected from the website after deployment.

    Custom event

    Example of the event:

    {
      type: "custom_event",
      timestamp: "2019-05-05T18:45:41.062Z",
      version: "1.3.0",
      payload: {
        page_title: "Contact | Meiro",
        url: "https://www.meiro.io/contact/",
        referrer: "https://www.google.com/search?q=meiro",
        additional_event_payload
      },
      user_id: "unique user id",
      fingerprint: "fingerprint MD5 hash",
      session_id: "base64 session id (timestamp&user_id)",
      external_id: "some id string" 
    // OPTIONAL ATTRIBUTE, OCCURS WHEN CONFIGURED }

    Data collected from this event type can be customised by the administrator of the website.

     

    The custom event can record any event possible to collect through JavaScript and JSON listeners. The list of trackable custom events can be found under this link

    Learn more: How to set custom event.

    Contact Form

    {
    type: "contact_form_submit",
    timestamp: "2019-05-05T18:45:41.062Z",
    version: "1.1.0",
    payload: {
    page_title: "Contact | Meiro", // required
    url: "https://www.meiro.io/contact/", // required
    referrer: "https://www.google.com/search?q=meiro", // required
    form_id: "registerForm (required, string)", // required
    email: "john@doe.com (optional, string)",
    first_name: "John (optional, string)",
    last_name: "Doe (optional, string)",
    phone_number: "+420439847320 (optional, string)",
    national_id: "CZE (optional, string)",
    gender: "male (optional, string)",
    birthdate: "10-10-1992 (optional, string)",
    whatsapp: "@hodlmao (optional, string)",
    instagram: "maleshe (optional, string)",
    facebook: "JohnDoe10023 (optional, string)",
    linkedin: "JohnDoeB (optional, string)",
    internal_user_id: "439FID43 (optional, string)",
    external_id: "43FSOSOIRTEOI43 (optional, string)",
    field00: "optional scalar value (null, string, number, bool) or array of scalar values"
    ...
    field30: "optional scalar value (null, string, number, bool) or array of scalar values"
    },
    user_id: "unique user id",
    fingerprint: "fingerprint MD5 hash",
    session_id: "base64 session id (timestamp&user_id)",
    external_id: "some id string"
    // OPTIONAL ATTRIBUTE, OCCURS WHEN CONFIGURED
    }

    Data collected from this event:

    • Form ID,
    • Email,
    • First Name,
    • Last Name,
    • Phone Number,
    • National ID,
    • Gender,
    • Birthdate,
    • Whatsapp,
    • Instagram, 
    • Facebook, 
    • LinkedIn, 
    • Internal User ID, 
    • Field00, Field30 are optional customizable values that can hold a scalar value or an array of scalar values (null, string, number or bool).

     

    Learn more: How to track contact form on the website.

    Google Client ID sync

     

    {
    type: "ga_cid_sync",
    version: "1.0.0",
    payload: {
    page_title: "Customer Data Platform that helps you target precisely",
    url: "https://meiro.io/",
    referrer: "https://www.google.com/search?q=meiro",
    client_id: "google analytics client id"
    },
    timestamp: "2020-09-08T14:58:53.110Z",
    user_id: "unique user id",
    fingerprint: "fingerprint MD5 hash",
    session_id: "base64 session id (timestamp&user_id)"
    }

     

    A cookie sync between Meiro Events ID and Google Analytics ID in order to accurately identify a user across all the devices they use to access your site.

    Learn more: about Cookies and User Identification here.

     

    Data collected from this event:

    • Page title,
    • URL,
    • Referrer,
    • Client ID, 

    Web Banner Impression

     

     


    session_id: "MTYyMjE4Njg0ODM3NCZlOWQ2NjNhZS0wY2MwLTQ0ZDQtYjVmOC1lZjFhZTZiMTU2NTE=" 
    timestamp: "2021-05-28T07:27:37.351Z" 
    type: "web_banner_impression"
    user_id:
    "e9d663ae-0cc0-44d4-b5f8-ef1ae6b15651" 
    version: "1.0.0" 
    payload:
    {   
    page_title: "Index page",   
    url: "http://cdp.meiro.d3v:8060/",   
    referrer: "",  
    banner_id: "b2b14ad1-e120-403d-b9a1-4a063d2ed8f0"
    }}



    Data collected from this event:

    • Page Title
    • URL
    • Referrer
    • Banner ID

    Web Banner Click

    { 
    session_id:
    "MTYyMjE4Njg0ODM3NCZlOWQ2NjNhZS0wY2MwLTQ0ZDQtYjVmOC1lZjFhZTZiMTU2NTE=" 
    timestamp: "2021-05-28T07:27:37.351Z" 
    type:
    "web_banner_click" 
    user_id:
    "e9d663ae-0cc0-44d4-b5f8-ef1ae6b15651"
    version: "1.0.0"
    payload: {   
    page_title:
    "Index page",   
    url:
    "http://cdp.meiro.d3v:8060/",   
    referrer: "",   
    banner_id:
    "b2b14ad1-e120-403d-b9a1-4a063d2ed8f0"   
    destination_url: "some link url" 
    }}

    Data collected from this event:

    • Page Title
    • URL
    • Referrer
    • Banner ID
    • Destination URL