You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/navattic/index.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "Navattic Source"
2
+
title: Navattic Source
3
3
hidden: true
4
4
---
5
5
@@ -9,14 +9,11 @@ This source is maintained by Navattic. For any issues with the source, [contact
9
9
10
10
## Getting Started
11
11
12
-
13
12
To get started with the Navattic source:
14
13
1. Navigate to **Connections > Sources** and click **Add Source** in the Segment App.
15
14
2. Search for *Navattic* in the Sources Catalog, and select the Navattic tile, and click **Add Source**.
16
15
3. Give the Source a nickname configure any other settings.
17
-
18
16
- 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: SourceName_Prod, SourceName_Staging, SourceName_Dev).
19
-
20
17
4. Click **Add Source** to save your settings.
21
18
5. Copy the Write key from the Segment UI and log in to your Navattic account. Navigate to **Integrations > Segment** and paste the key. Click **Save** to connect.
22
19
6. Choose which Navattic events to send to Segment, as well as which demos (projects) to activate for this integration.
@@ -33,7 +30,7 @@ The table below lists possible events that Navattic sends to Segment. With the e
33
30
34
31
Event Name | Description |
35
32
------------ | ------------|
36
-
IDENTIFY_USER | A visitor submitted an email, usually through a form fill. This sends to the [Identifies table](/docs/connections/storage/warehouses/schema/#identifies-table) in Segment
33
+
IDENTIFY_USER | A visitor submitted an email, usually through a form fill. This sends to the [Identifies table](/docs/connections/storage/warehouses/schema/#identifies-table) in Segment.
37
34
VIEW_STEP | A visitor viewed a step in the demo.
38
35
START_FLOW | A visitor started a flow.
39
36
COMPLETE_FLOW | A visitor has completed a flow.
@@ -59,7 +56,7 @@ url | If the event is NAVIGATE, then this property contains the URL of the link
59
56
60
57
## Adding Destinations
61
58
62
-
Now that your Source is set up, you can connect it with Destinations.
59
+
Once your Source is set up, you can connect it with Destinations.
63
60
64
61
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](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting.
0 commit comments