Hotjar

Getting Started with Hotjar and setting it up.

Hotjar is an integrated website analytics solution that provides heatmaps of user behaviour, session recordings, mouse tracking, conversion funnels, feedback polls, full surveys, and test user recruitment. It is basically an easy way to understand your users visually.

Destination Info

• Accepts Identify, and Track calls

• Refer to it as Hotjar in the Integrations object

Components

• Browser

Use cases of Hotjar

Hotjar is a visual & direct way to understand and empathize with your users.

Hotjar helps you collect feedback that explains your behaviour.

Hotjar gives you fast product experience insights with no sleep-leaving curves.

Getting buy-in and demonstrating Hotjar's value is simple.

1. Hotjar is a visual and direct way to understand and empathize with your users.

2. With Hotjar, you can collect feedback that explains the behaviour of your users.

3. Hotjar gives you fast product experience insights with no steep learning curve.

Connection

Connection	Web	Mobile	Server
📱Device Mode	✅	🚫	🚫
☁️Cloud Mode	🚫	​🚫	🚫

Getting Started

Before we get started, you will need the following parameters.

Parameter	Description
SiteID	​Your site ID for HotJar. It should be a whole number, for example 562496.

Methods

Identify

In order to make an identify call, the user must first enable the User Attributes feature. The user properties will be shown once the identify call is made in Hotjar.

The method call will fail if the identify call is made after the Hotjar tracking code.

The user attributes are set in the first call that is made. These user attributes can’t be deleted and their data type cannot be modified. It is advised you ensure that the data type and property names are correct before you send it for the first time (even for testing purposes).

You can refer to the Hotjar Identify doc to know more.

The userId that is received in identify event is passed as it is.

Case 1: When userId is null/empty

lmSMTObj.identify("", {
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai",
    "email": "[e-mail]",
    "phoneNo": "9848012345"
})

In this case, the email and phoneNo will be scraped off the payload, as it is part of PII data of the user. The final payload will be something like:

hj('identify', null,
{
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai"
});

Case 2: When userId is present

hj('identify', null,
{
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai"
});

In this case, the email and phoneNo will not be scraped off the payload since userId is present. The final payload will be something like:

hj('identify', "viz_001", {
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai",
    "email": "[e-mail]",
    "phoneNo": "9848012345"
});

Case 1: When userId is null/empty

lmSMTObj.identify("", {
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai",
    "email": "[e-mail]",
    "phoneNo": "9848012345"
})

In this case, the email and phoneNo will be scraped off the payload, as it is part of PII data of the user. The final payload will be something like:

hj('identify', null,
{
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai"
});

Case 2: When userId is present

lmSMTObj.identify("viz_001", {
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai",
    "email": "[e-mail]",
    "phoneNo": "9848012345"
})

In this case, the email and phoneNo will not be scraped off the payload since userId is present. The final payload will be something like:

hj('identify', "viz_001", {
    "firstName": "John",
    "lastName": "Doe",
    "gender": "Male",
    "age": "27",
    "city": "Mumbai",
    "email": "[e-mail]",
    "phoneNo": "9848012345"
});

Track

With track call, only event names can be sent to Hotjar. Event properties are not supported with Hotjar.

Example call

lmSMTObj.track("filterApplied", {
    "product_id": "1",
    "product_name": "ABC"
})

Hotjar method

hj('event', 'filterApplied');

To test if your event has been successfully sent to Hotjar, click here and follow the steps.

Demo: Setting up destination Hotjar