Zigpoll

Zigpoll is a survey and feedback platform for ecommerce stores, used to run post-purchase, on-site and email surveys such as attribution ("how did you hear about us?"), customer satisfaction and product feedback questions. With Weld you can sync your Zigpoll polls and responses into your data warehouse and join them with your order and ad platform data.

Features

Feature nameSupported
Column HashingTrueColumn level
BlockingTrueColumn level
IncrementalTrue
Custom dataFalse
HistoryTrue
ReSyncTrueTable level
TemplatesFalse

Data Schema


Setup Guide - ELT

Step 1 - Get your Zigpoll API key

  1. Sign in to Zigpoll with an account that can administer your Zigpoll account.
  2. Open your account settings and copy your API key.

Step 2 - Create the connection

  1. In the Weld app, navigate to Connections and click + New Connection.
  2. Search for Zigpoll and select it.
  3. Enter the destination schema name of your choice. This name is used to identify the connection in future syncs.
  4. Paste your API key.
  5. Click Connect to validate the key and establish the connection.

Step 3 - Data To Sync

Select the tables you wish to include in the sync. You can view the schema, remove columns or hash sensitive information.

The connector exposes the following streams:

StreamPrimary keySync modeSubstreams
accountidFullAccount admins
pollidIncrementalPage rules
slideidIncrementalAnswers, logic rules
responseidIncrementalAnswers
participantidFullPolls, slides, tracked emails, responses
emailidFull
insightidFullInsight items
webhookkeyFull

Each substream lands in its own destination table, linked back to its parent record.

Step 4 - Configure sync

  1. Select how often you would like the data to sync.
  2. Provide a unique destination table name.

Weld will take over from here and commence syncing data from your Zigpoll account.


How syncing works

Incremental syncs

poll, slide and response sync incrementally: the first run backfills everything, and each run after that asks Zigpoll only for records changed since the previous successful sync. Records are merged into the destination table on their primary key, so a record updated in Zigpoll is updated in place rather than duplicated.

The remaining streams — account, participant, email, insight and webhook — are refreshed in full on every run.

Was this page helpful?