Using Hotjar with Zapier

Zapier lets you connect Hotjar to 5,000+ other web services. Automated connections called Zaps, set up in minutes with no coding, can automate your day-to-day tasks and build workflows between apps that otherwise wouldn't be possible.

Each Zap has one app as the Trigger (such as Hotjar), where your information comes from and which causes one or more Actions in other apps, where your data gets sent automatically. This integration supports the following Hotjar tools to be used as triggers:

• Surveys
• Recordings

Before getting started, be aware of the following:

• You need to have an account with both Hotjar and Zapier.
• The integration is ready to use and does not need to be enabled first.
• All Team Members with Read & Write access permissions or higher can create a Zap.
• The Hotjar Tracking Code needs to be installed on your site.
• To trigger actions in Zapier, you need to have one of the Hotjar tools (Recordings, Surveys) actively targeting users on your website.

To get started, scroll down or click one of the sections below:

• Create a Zap for a Survey
• Create a Zap from within your Zapier account
• List of available Hotjar parameters
• Suggested use cases
• Hotjar versions in Zapier

Create a Zap for a Survey

The integration is ready to use and does not need to be enabled first.

Go to your Surveys page.

Edit the desired Survey.

Choose one of your Surveys from the list on the left. Click on the three-dotted menu on the right, then select Edit.

Expand the Forward Response section in the tool settings.

Choose one of the scenarios to create a new Zap.

To learn more about creating new Zaps, read Zapier's Getting Started Guide.

Back to top

Create a Zap from within your Zapier account

Log in to Zapier.

Click the Create Zap button.

For the Trigger, select Hotjar.

Select New Recording or New Survey Response as the Event.

Choose which Hotjar account you'd like to use in this Zap.

You may need to connect a new account to Zapier. For help with this, see Zapier's documentation on connecting your apps to Zapier.

For the Action, select the app you want to connect with Hotjar and define the desired action as Event.

Creating a Zap requires no coding knowledge and you'll be walked step-by-step through the setup. Take a look at Zapier's Getting Started Guide to learn more about this process.

Test and publish your Zap.

Back to top

List of available Hotjar parameters

To customize your Zaps, you can use Hotjar's metadata related to Recordings and Surveys.

Back to top

Suggested use cases

Below, you'll find examples of automated workflows created using the Zapier integration. Click on the following links to get step-by-step setup instructions:

• Hotjar + Google Sheets - Create custom reports in Google Sheets. Automatically add a new row or column in a spreadsheet when there’s a new Hotjar event that matches your criteria. Use the data to plot a line graph to monitor rage clicks over time. Investigate trends and take action when you see a clear spike in behavior.
• Hotjar + Miro - Send survey responses to Miro. Share feedback with other teams to focus on areas for improvement.

Back to top

Hotjar versions in Zapier

In this section, we're going to discuss how we use versions to keep improving our Zapier integration. When creating a new Zap, you might have noticed several different versions of Hotjar to choose from.

Each Trigger event has a set of fields available, fields which you can insert into whatever tool you're forwarding to. For example, in the New Recording event, there's "site_id", "browser", "country code", "device", among others.

In most cases, new versions of Hotjar in Zapier will add new fields you can start using. Unfortunately, sometimes we might need to make changes to fields you already use or, in rare cases, remove fields.

These kinds of updates with breaking changes will be infrequent, however there are situations where this will be unavoidable. If you rely on a field that was either modified or removed, you might need to update how you handle the data forwarded to your Zaps.

When a breaking change update occurs, we'll do the following:

• Set a deprecation date.
• Let you know via email that a certain version you rely on for your Zaps is going to be removed at a future date.
• Give you ample time to double check your Zaps and perform any needed updates.

Changelog

v2.0.1

• We added a new field, "answers," to Surveys. This field contains survey answers. There's already an existing field, "questions", which presents similar information, but there are some issues with it - If there are any skipped, conditional, or multiple choice questions, certain answers might not show up. We recommend adopting the new "answers" field instead.
  
  This update is transparent to you. There's no action needed on your end, unless you prefer to start using the new field, as recommended.

v2.0.0

• We've changed the format of the Survey's "created_datetime_string" field. The field is now formatted as ISO-8601. This is a breaking change.
• We've modified the Created field in Recordings to be displayed as a Unix Timestamp. Before, it was displayed in a non-standard datetime format.

v1.2.6

• We've made a few behind-the-scenes changes needed to support releasing versions. This version is being deprecated. Please upgrade to the latest one at your earliest convenience.

Back to top