Integrations
Navattic gathers three types of data to help you assess the performance of your interactive demos: Engagement data, Visitor data, and Account data.
While Navattic provides in-app analytics, we recommend setting up an integration to see the value demos generate for your business in the tools you already use. We also recommend installing Navattic JS on the website where your demos are presented (i.e., your marketing website) to enhance your data collection.
To get started, Navattic supports three types of data:
- Demo event data: such as view_step or start_flow, and more. This is gathered automatically for your demo to help you understand which demos are most engaging or where visitors are dropping off.
- Visitor data: such as email, UTMs, a visitor's last-viewed demo step, and more. This is gathered for all visitors (both identified and anonymous) and may be sent through playbooks if a visitor is identified.
- Account data: such as company domain, number of employees, company location, and more. This is provided through a partnership with Clearbit.
Continue reading for a summary of each data type and recommended integration setups.
Navattic gathers three types of data, which may be sent through integrations.
Demo event data includes the actions a user takes within a Navattic demo such as viewing a step, starting a new Flow, opening or closing a Checklist, or clicking a link that navigates to an external URL. Demo Engagement Data can be tied to anonymous visitors, identified Visitors, or identified Accounts.
These integrations can receive and organize visitor data:
- Salesforce, HubSpot, and Marketo receive detailed demo engagement data including view_step, start_flow, etc. that is connected to:
- Identified Visitors
- Identified Accounts
- GA4, Segment, Amplitude, Adobe Analytics, and other events-based analytics platforms receive detailed demo engagement data including view_step, start_flow, etc. that is connected to
- Anonymous Visitors
- Identified Visitors
- Identified Accounts
- Slack receives simple demo engagement data (start_flow and identified) for:
- Identified Visitors
- Identified Accounts
This includes individual Visitor identification data such as email, name, phone number, company, and other custom fields you may use.
Visitor data enters Navattic via any of these identification options. In summary, these options are:
- A form by Navattic, HubSpot, or Marketo
- Navattic identification variables that are attached to demo share links
- Query strings that are attached to demo share links
- JavaScript (requires technical setup)
These integrations can receive and organize visitor data:
- Salesforce, HubSpot, and Marketo can create and/or update contacts when visitors are identified in Navattic. These platforms combine visitor data and demo engagement data to paint a full picture of the visitor's activity within your demo.
- Some events-based platforms like GA4 and Segment can receive Visitor Identification data, although not all events-based platforms will support this.
- Slack can send a real-time notification to a designated channel when Visitors are identified in Navattic.
This includes Account-level identification data such as Company Name or Industry that occurs if Navattic Account-Based Engagement is enabled in your workspace.
When Account-Based Engagement is active, Navattic will use Clearbit Reveal to identify anonymous users and Clearbit Enrichment to enrich firmographic (company) information from identified users (i.e. If a user fills a form with their email [email protected], Navattic will enrich Apple).
This helps marketing and sales teams reduce the number of fields they include in a form or remove the form entirely while still seeing the Accounts that are most engaged with their demos.
These integrations can receive and organize account data:
- Salesforce and HubSpot can create and/or update Company Accounts when they are identified within Navattic. These platforms combine account data and demo engagement data to paint a full picture of the account's engagement with your demo.
- Some events-based platforms like GA4 and Segment can receive Account Identification data, although not all events-based platforms will support this.
- Slack can send a real-time notification to a designated channel when Accounts are identified within Navattic.
Direct Integrations pass the Engagement, Visitor, and Account data that is available within Navattic to other tools. This lets you view and report on Navattic data in the platforms you already use, to track demo ROI and guide your outreach strategy.
Some direct integrations require you to identify Visitors and/or Accounts before integrating while others do not. You can identify Visitors from your website by installing Navattic JS. Find setup guides for each option below or visit Direct Integrations to learn more.
For customers who embed demos on a website, we highly recommend using Navattic JS to enhance your data collection in two ways:
- Identify demo visitors previously cookied by your CRM (e.g., HubSpot) instead of needing to use a form.
- Send demo events to events-based platforms like Google Analytics.
How it works: Navattic demos emit "events" whenever users perform actions - viewing a step, starting a flow, clicking a link, etc. When your demo is embedded on a landing page, this integration lets you send those events to any platform that can accept them like Amplitude, PostHog, and Mixpanel.
Note: Your demo needs to be embedded in a landing page in order to use Navattic JS. Visit Navattic JS for detailed setup steps.
While there are many possible integrations, this section is a good starting point for some of the most common setups for marketing, sales, and product use cases. Use this to determine the recommended starting point for your use case and reach out to [email protected] if you have any questions.
Scenario A: I'm using Navattic demos to create new leads
In this case, you likely want to first identify contacts in Navattic and then send data to the corresponding places. You can mix and match between the two columns below. We recommend embedding your demo on a landing page for this use case.
1. I have identified Visitors... | 2. I want to see my data in... |
|---|---|
You can identify demo Visitors by using a Form within Navattic (Navattic Form or an Embed Step HubSpot or Marketo Form) or an an external form paired with Navattic JS. |
Scenario B: I want to see how Navattic demos impact overall website events and don't need identified Visitor information.
In this case, you do not need to send identified Visitor or Account data but will want to send demo event data, such as step_viewed, flow_started, checklist_completed, etc., to an events-based platform. We recommend embedding your demo on a landing page for this use case and installing Navattic JS.