Skip to content

Commit 2bbe922

Browse files
Apply suggestions from code review
1 parent ed0472e commit 2bbe922

File tree

1 file changed

+6
-6
lines changed
  • src/connections/sources/catalog/cloud-apps/zigpoll

1 file changed

+6
-6
lines changed

src/connections/sources/catalog/cloud-apps/zigpoll/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
`---
1+
---
22
title: Zigpoll Source
3+
id: h00x3Ep5el
34
---
45

56
[Zigpoll](https://www.zigpoll.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} provides merchants with powerful post-purchase surveys, AI-powered insights, and zero-party data collection tools. With Zigpoll, you can capture customer feedback directly at the point of conversion and send it seamlessly into your marketing and analytics stack.
@@ -12,17 +13,17 @@ This source is maintained by Zigpoll. For any issues with the source, [contact t
1213
2. Search for "Zigpoll" in the Sources Catalog, select Zigpoll, and click **Add Source**.
1314
3. On the next screen, give the Source a name and configure any other settings.
1415

15-
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (e.g., Zigpoll_Prod, Zigpoll_Staging, Zigpoll_Dev).
16+
- The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (for example, Zigpoll_Prod, Zigpoll_Staging, or Zigpoll_Dev).
1617

1718
4. Click **Add Source** to save your settings.
1819
5. Copy the Write key from the Segment UI.
1920
6. Log in to your Zigpoll account, navigate to **Settings > Integrations > Segment Integration**, and paste the key to connect.
2021

2122
## Stream
2223

23-
Zigpoll uses Segment’s stream Source component to send event data. It uses the `track` and `identify` methods to send data to Segment. These events are then available in any destination that accepts server-side events, and in a schema in your data warehouse, so you can query using SQL.
24+
Zigpoll uses Segment’s stream Source component to send event data. It uses the Track and Identify methods to send data to Segment. These events are then available in any destination that accepts server-side events and as a schema in your data warehouse that you can query using SQL.
2425

25-
The default behavior is for Zigpoll to pass the survey participant’s unique ID as the `userId`. If a participant’s email is available, Zigpoll also passes it as an identifier. If no `userId` is available, Zigpoll will pass the email as the `anonymousId`.
26+
The default behavior is for Zigpoll to pass the survey participant’s unique ID as the `userId`. If a participant’s email is available, Zigpoll also passes it as an identifier. If no `userId` is available, Zigpoll passes the email as the `anonymousId`.
2627

2728
## Events
2829

@@ -49,5 +50,4 @@ Now that your Source is set up, you can connect it with Destinations.
4950

5051
Log into 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.
5152

52-
If there are any issues with how the events are arriving to Segment, [contact the Zigpoll support team](mailto:[email protected]).
53-
`
53+
If there are any issues with how the events are arriving to Segment, [contact the Zigpoll support team](mailto:[email protected]).

0 commit comments

Comments
 (0)