Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Navattic Source


Source Info
  • The Navattic Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
  • This source is in Beta

Navattic(link takes you to an external page) is a no-code tool which enables go-to-market teams to build beautiful, interactive demos of their products to excite and engage prospects.

This source is maintained by Navattic. For any issues with the source, contact the Navattic Support team.


Getting Started

getting-started page anchor

To get started with the Navattic source:

  1. Navigate to Connections > Sources and click Add Source in the Segment App.
  2. Search for Navattic in the Sources Catalog, and select the Navattic tile, and click Add Source.
  3. Give the Source a nickname and configure any other settings.
    • The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example: Navattic_Prod, Navattic_Staging, Navattic_Dev).
  4. Click Add Source to save your settings.
  5. Copy the Write key from the Segment UI and log in to your Navattic account. Navigate to Integrations > Segment and paste the key.
  6. Optionally, select either the US (default) or EU region for your events.
  7. Click Save to connect.
  8. Choose which Navattic events to send to Segment, as well as which demos (projects) to activate for this integration.

Navattic uses the stream Source component to send Segment event data. It uses server-side Track and Identify methods to send data to Segment. These events are then available both in destinations that accepts server-side events and in a schema in your data warehouse, so you can query using SQL.

Navattic generates its own ID for each visitor to your product demo. This ID passes as the userId when pushing Navattic events to Segment.


The table below lists possible events that Navattic sends to Segment. With the exception of IDENTIFY_USER, all events are sent to the Tracks table in Segment. Additionally, every Navattic event includes the userId, which is Navattic-generated for each user.

Event NameDescription
IDENTIFY_USERA visitor submitted an email, usually through a form fill. This sends to the Identifies table in Segment.
VIEW_STEPA visitor viewed a step in the demo.
START_FLOWA visitor started a flow.
COMPLETE_FLOWA visitor has completed a flow.
NAVIGATEA visitor clicked on a link from within the demo.
OPEN_CHECKLISTA visitor expanded a checklist.
CLOSE_CHECKLISTA visitor collapsed a checklist.
COMPLETE_TASKA visitor completed a checklist task.
CONVERTEDA visitor viewed a step tagged Mark as converted.

The table below lists the properties included in the events listed above.

Property NameDescription
projectAn object containing the demo's (project's) ID and name.
checklistAn object containing the checklist's ID and name. Populated only if the demo contains a checklist.
flowAn object containing the current flow's ID and name.
stepAn object containing the current flow step's ID, name, and index (step.indx)
session_idA string that uniquely identifies this visitor's current session.
urlIf the event is NAVIGATE, then this property contains the URL of the link that the visitor clicked on. Otherwise, it is empty.

Once your Source is set up, you can connect it with Destinations.

Log in to your downstream tools and check to see that your events appear as expected and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving to Segment, contact the Navattic support team.