zigpoll source documentation #7848
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Comment on lines
+1
to
+3
| `--- | ||
| title: Zigpoll Source | ||
| --- |
There was a problem hiding this comment.
Suggested change
| `--- | |
| title: Zigpoll Source | |
| --- | |
| --- | |
| title: Zigpoll Source | |
| id: h00x3Ep5el | |
| --- |
There was a problem hiding this comment.
Hi @forstisabella h00x3Ep5el
| 2. Search for "Zigpoll" in the Sources Catalog, select Zigpoll, and click **Add Source**. | ||
| 3. On the next screen, give the Source a name and configure any other settings. | ||
|
|
||
| - 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). |
There was a problem hiding this comment.
Suggested change
| - 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). | |
| - 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). |
|
|
||
| ## Stream | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Suggested change
| 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. | |
| 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. |
|
|
||
| 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. | ||
|
|
||
| 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`. |
There was a problem hiding this comment.
Suggested change
| 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`. | |
| 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`. |
| 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. | ||
|
|
||
| If there are any issues with how the events are arriving to Segment, [contact the Zigpoll support team](mailto:[email protected]). | ||
| ` |
|
|
||
| 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. | ||
|
|
||
| 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`. |
There was a problem hiding this comment.
Hi @JasonZigelbaum - I'd usually not recommend the identifier approach taken here - let's talk about identifiers when we meet.
|
|
||
| This source is maintained by Zigpoll. For any issues with the source, [contact the Zigpoll Support team](mailto:[email protected]). | ||
|
|
||
| ## Getting started |
There was a problem hiding this comment.
Ideally it would be good to support sending Zigpoll events to Segment's US and EU Workspaces.
Currently it looks like only US Workspaces are supported.
To support EU Workspaces you'd simply need to post the events to a different domain. You could give the customer the option to select which Region they prefer.
If you don't have any EU customers then you may want to just support the US Region for now. Most Segment customers are on the US Region.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added documentation for the Zigpoll source.