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.

To get started, Navattic supports three types of integrations:

Continue reading for a summary of each data type, integration type, and recommended setups for common marketing, sales, and product use cases.

Navattic gathers three types of data, which may be sent through integrations.

Engagement data or demo engagement 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:

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:

These integrations can receive and organize visitor data:

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:

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. Find setup guides for each option below or visit Direct Integrations to learn more.

Tracking Scripts are enabled on individual Navattic demos to send demo engagement data to other platforms. Most often, this is used to record a "page view" on existing HubSpot or Marketo contacts, which can then be used to create sales or marketing reports.

This differs from the Direct Integrations introduced above, as Visitor identification occurs outside of Navattic, separately from the visitor's interaction with your demo, and does not enter the Navattic platform. Tracking Scripts may be used for demos that are embedded in an iFrame or shared as a direct link.

Find a recommended setup guide by use case below or visit Tracking Scripts to learn more.

Note: While tracking scripts are a low-lift no-code way to get started with integrations, Direct Integrations offered with HubSpot, Marketo, and GA4 can send even more data types such as utm_source, browser, referrer, etc. We recommend exploring a direct integration if you want to see more detailed data in your CRM.

Embed Events are used to send Navattic events to event-based analytics platforms that are used to analyze how users interact with your website. This is a flexible integration option that lets you receive Navattic events just like you receive other website events.

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 Embed Events. Visit Embed Events 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 (marketing use case)

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.

Scenario B: I'm sharing Navattic demos with existing contacts (sales use case)

In this case, you likely want to send demo engagement data directly to the platform that currently houses your Contact information.

If you are sharing a direct link to your demo rather than embedding this on a landing page, tracking scripts may be used to send basic engagement data to these platforms (ex. "Caroline viewed your Product Overview Demo on December 2, 2024"). This is great for sales use cases, where you may quickly send a demo before or after a call.

The advanced options may be supplementary if your demo is embedded on a landing page or identifies contacts with some type of form. This is more similar to Scenario A above and will sync more fields such as "utm_source", "browser", "referrer", etc.

Scenario C: I want to see how Navattic impacts overall website events and don't need to see individual visitor information.

In this case, you do not need to send identified Visitor or Account data, but will want to send demo engagement data such as step_viewed, flow_started, checklist_completed, etc. to another platform. We recommend embedding your demo on a landing page for this use case. Select your preferred platform below.