Help

Once a survey is designed and published, you send it out from the Share tab. Everything you distribute is a collector — one link, QR code, embed, email campaign, WhatsApp campaign, social post, printable sheet or Shopify placement, each with its own share code, its own on/off switch and its own response count. This guide walks through the Share tab, every collector type, and the settings that govern who may respond and how often.

Everything you send out goes through a collector. A collector is one distribution channel for one survey — a WhatsApp campaign, an email campaign, a web link, a QR code — and the Share tab is where you create them, switch them on and off, and watch the numbers come in.

What a collector is

Each collector belongs to a single survey and stands on its own:

Its own address. The link a respondent opens is built from the collector’s own id, so two collectors on the same survey are two different addresses.
Its own on/off switch. The Status column is a switch reading Active or Inactive, and you can flip it without touching the survey.
Its own counts. Opened and Responses are tracked per collector, not just per survey.

Every response is attributed to the collector it arrived through, so you can run an email campaign and a printed QR code for the same survey and still see which one is producing answers.

Where the tab sits

The Share tab is step 4 of the survey designer. The steps run Design, Preview, Publish, Share, Analyze across the top of the editor, and selecting it puts ?step=share at the end of the browser address. On a narrow screen the five steps collapse into a dropdown, so pick Share from that list instead.

The Share tab under its Distribution Channels heading, with the channel filter tabs above the collector table — note that Status is a switch you flip in place, not a text label, and that the Flow column is drawn only on the All and WhatsApp tabs.

There are four ways in:

Inside the designer, click the Share step in the top bar.
From the Publish step, click Next at the top right of the app bar.
From your workspace survey list, open a survey row’s ⋮ menu and click Send.
From the survey list on your dashboard, use the same Send row-menu item.

Note: On a phone, the designer’s overflow menu carries a second item also labelled Share while you are on Design or Preview. That one opens a preview link popup for colleagues, not this tab.

Publish the survey first

The Create Collector button stays disabled until the survey is published, and the tab shows a warning: Survey is not active, please publish before sharing this survey.

1Go to the Publish step, one to the left of Share.
2Publish the survey from that step.
3Return to Share. The create buttons are now enabled.

You can still open the Share tab while a survey is unpublished; the list of existing collectors loads as normal. Only the create buttons are switched off.

What is on the tab

The header reads Distribution Channels, with the Create Collector button on the right. Below it, a card holds the channel filter tabs — All, WhatsApp, Email, Links, Website, Social, Integrations — and the collector table: Type, Name, Flow, Status, Opened, Responses, Actions. Section 2 goes through the table and the row actions.

Which collector to use

Share > Create Collector offers eight types, and the choice comes down to where your respondents already are. All eight appear while the All filter tab is selected; on the other filter tabs you are offered only the channels that tab covers.

Collector	Use it when
WhatsApp	You have respondents’ phone numbers and want the survey delivered as a WhatsApp message, with or without a WhatsApp Flow.
Email	You are sending the survey by email and want the send handled as a campaign you can watch progress on.
Web Link	You need one URL to paste wherever you like — a newsletter, a chat message, a document.
QR Code	Respondents will scan rather than click: a poster, a receipt, a table card, a slide.
Download Survey	You want a copy of the survey itself to keep or hand out. The download is a PDF, one page per survey page.
Website	The survey should sit on your own site, as a popup or inline in the page.
Social Media	You want to post the survey from a social account. The menu lists Facebook, Twitter/X, LinkedIn, Instagram, Slack, MS Teams and Messenger.
Shopify	The survey belongs in a Shopify store’s checkout flow.

Those eight are the whole list. There is no SMS collector, and no panel or audience-buying option.

What is not on this tab

Several settings people look for here sit one step to the left. Response goals, rewards, access restrictions, start and end dates, and the survey end page are all on the Publish step, under Publish & Settings: its tabs are Survey End Page, Schedule, Options and Response Goals, alongside a Restriction button. Section 12 covers where each one lives.

2. The collector list

Every collector you create for a survey is listed on one screen, under the heading Distribution Channels. The Create Collector button sits to the right of that heading, and below it a card holds the channel filter tabs, the table of collectors and the pagination bar.

Filter tabs

Seven tabs run across the top of the card: All, WhatsApp, Email, Links, Website, Social and Integrations. A tab carries a count chip only when that channel has at least one collector. Links covers web link, QR code and download collectors; Integrations covers Shopify and the other integration collectors. The tabs filter the rows already on screen — nothing is re-fetched.

The Flow column is drawn only while All or WhatsApp is selected, so the other five tabs show six columns instead of seven.

What each column means

Column	What it shows
Type	An icon for the collector’s channel. Hover it to see the channel name.
Name	The collector’s name, with the date it was created underneath (for example `3 Sep 2026`; a dash if there is no date).
Flow	Shown on the All and WhatsApp tabs only. For a WhatsApp collector that uses Native Flow distribution and has a phone number configured, this is the state of that WhatsApp Flow: No Flow, Published, Draft or Deprecated. Every other row shows a dash.
Status	A switch rather than a text value, labelled Active or Inactive beside it. Flipping it saves straight away and reloads the list. This switch is the only on/off control a collector has.
Opened	How many times the survey has been loaded through that collector. It counts page loads, not people, so a respondent who reloads counts twice. Preview loads and the print render behind Download Survey are not counted. A collector that has never been opened shows 0.
Responses	How many responses have been recorded against that collector. It is a plain number, not a link.
Actions	The ⋮ button that opens the row menu.

Not every channel asks you to name a collector. When a collector has no name of its own, Name falls back to its channel label — a new web link reads Link, and others read QR Code, WhatsApp, Email, Download, Website or Shopify. A social collector falls back to the platform instead, such as Facebook, Twitter / X or LinkedIn. These fallback labels, and the tooltip in the Type column, stay in English whatever language you use the app in.

Note: An active email collector that has started sending shows a campaign progress bar with a sent-of-total counter under its name; click it to open the campaign progress dialog. After you send an email campaign, the list refreshes itself every 10 seconds for two minutes and then stops.

Opening a row and its ⋮ menu

Click anywhere on a row to open that collector’s editor. Some rows behave differently: a download collector’s row starts the PDF download instead of opening an editor, and a social collector’s row opens the survey’s active social collector, which is not necessarily the row you clicked.

The ⋮ menu at the end of a row holds:

Edit — the same as clicking the row.
Download — on download collectors only.
Re-sync Flow and Delete Flow — on WhatsApp collectors that use Native Flow only.
Delete, in red — on every row.

To delete a collector:

1Open the row’s ⋮ menu and click Delete.
2Read the Delete Collector dialog: “Are you sure you want to delete this collector? This action cannot be undone.” On a WhatsApp Native Flow collector it adds “The WhatsApp Flow for this survey will NOT be deleted. Other collectors can still use it.”
3Click Delete to confirm, or Cancel to keep the collector.

Warning: Deleting removes the collector outright. There is no archive and no undo.

Empty state and pagination

The table shows an empty state whenever the page you are on holds no rows — most often because no collector matches the tab you selected. The column headers stay in place and the body of the table shows an inbox icon, the text No collectors found and a Create your first collector button, which offers the same channels as Create Collector.

The pagination bar sits at the foot of the card and pages through the rows already loaded in your browser. It shows 10 rows per page by default, and you can choose 5, 10, 25 or 50. It is hidden when nothing matches the current tab. If you delete the last rows on a later page you can see the empty state with the pagination bar still below it — go back to page 1.

What the list does not do

There is no search box and no column sorting. The seven channel tabs are the only way to narrow the list.
There is no multi-select and no bulk action; you act on one row at a time.
There is no duplicate or clone action.
You cannot copy a survey URL from a row. Copy it inside the web link or QR code editor.
You cannot open a collector’s responses from its row. The Responses number is not a link; responses are on the Analyze step.
You cannot rename a collector from the list. A web link or QR code collector is named in its own editor, in the Name field.
There is no scheduled open or close date on a collector. The Active / Inactive switch is the only lifecycle control.

3. Creating a collector

Every route to your respondents starts with a collector. Collectors are created from the Create Collector button at the top right of the Distribution Channels header.

1Open the survey and go to the Share step.
2Click Create Collector. When the table has no rows to show, the Create your first collector button in the middle of it does the same thing. Both are disabled until the survey is published.
3Pick a channel.
4Finish in the panel that opens, then close it — Download Survey is the exception, it opens no panel and downloads the PDF instead. The collector appears in the table below, switched on.

The menu offers exactly eight channels, each with a coloured icon, a title and a one-line description.

The Create Collector menu with all eight channels and their one-line descriptions; how many you see depends on the filter tab you were on, since Links narrows it to three and single-channel tabs skip the menu entirely.

WhatsApp — Send surveys via WhatsApp messages with automated flows
Email — Distribute surveys through email campaigns with tracking
Web Link — Create shareable links for easy survey distribution
QR Code — Generate QR codes for offline and print distribution
Download Survey — Download survey as HTML for offline use or embedding
Website — Embed surveys on your website with popup or inline options
Social Media — Post surveys across social platforms and track engagement
Shopify — Integrate surveys into your Shopify store checkout flow

How many of the eight you see depends on the filter tab that is active when you click the button. The menu opens only when the tab covers more than one channel; when it covers exactly one, that channel is created or opened directly and no menu appears.

All — the full eight-channel menu.
Links — a three-channel menu: Web Link, QR Code, Download Survey.
WhatsApp, Email, Website, Social, Integrations — no menu. The button goes straight to that channel; on Integrations it goes to Shopify.

Channel	What it produces	Configured where
WhatsApp	A WhatsApp collector with its own campaign settings. WhatsApp collectors are the only ones that use a WhatsApp Flow.	Created immediately, then its editor opens.
Email	An email campaign. Once a send has started, a sent/total progress bar appears under the collector’s name in the table.	Created immediately, then its editor opens.
Web Link	A shareable survey link, on the default survey domain or on a custom domain available to your workspace.	Created immediately, then its editor opens.
QR Code	A QR code you can recolour and download as `QR_Code.png`.	Created immediately, then the QR panel opens.
Download Survey	A PDF of the survey, one PDF page per survey page.	Created immediately, then the PDF downloads. No editor opens.
Website	Embed code for your own site, as a popup or inline.	Its own screen opens first; the collector is created there.
Social Media	A post on a social platform. The menu item lists Facebook, Twitter/X, LinkedIn, Instagram, Slack, MS Teams and Messenger.	Its own screen opens first; the collector is created there.
Shopify	A survey placed in your Shopify store checkout flow.	Its own screen opens first; the collector is created there.

Note: The menu describes Download Survey as HTML. The file you actually get is a PDF.

Warning: WhatsApp, Email, Web Link, QR Code and Download Survey write the collector to your list the moment you pick them — before you have configured or named anything, and with no confirmation step. If you change your mind and close the panel, the row stays behind, switched on, and you have to delete it. Each click of Download Survey creates another collector, so downloading the PDF twice leaves two rows.

Tip: A collector you have not named is listed under its type, for example Link, QR Code or WhatsApp. Set a name in the collector’s own panel so a survey with several collectors stays readable.

4. Web Link

A Web Link collector gives you one public URL that anyone can open. Put it in a newsletter, a chat message or a social post: everyone who opens it answers the same survey, and every response is counted against that one collector.

The link has the shape https://surveys.surveyanalytica.com/s/<collector id>. The last part is the id of the collector, not of the survey, so each Web Link you create on the same survey has its own URL and its own Opened and Responses counts.

1Open the Share tab and click Create Collector.
2Choose Web Link (“Create shareable links for easy survey distribution”). The collector is created straight away and its popup opens.
3Copy the URL using the copy icon to its right. A browser message confirms Link copied. The URL is plain text in the popup, not a clickable link.
4Type a label in the Name field so you can tell this link apart from your others. Left empty, the row is named Link.
5Click Save, then close the popup.

The Web Link popup, the only place a collector’s URL is ever shown, listing the default address and any custom domain your organisation has added — the [name_value] placeholders are literal text you replace by hand before sending.

The URL is shown only inside this popup. The collector table lists the type, name, status and counts, but never the link itself — to get it again, reopen the popup by clicking the collector’s row, or by choosing Edit in the row menu.

If your organisation has added a custom domain, the popup lists an extra URL for each one, such as https://feedback.yourcompany.com/s/<collector id>, each with its own copy icon. They all open the same survey, so use whichever host you want respondents to see. An organisation admin adds domains under Account > Organization > My Domains > Surveys.

Name and Disable Response Override

Setting	What it does
Name	A label for the collector, shown in the Name column of the table. It changes nothing about the link.
Disable Response Override	Stops a respondent submitting the survey a second time. It applies only when the respondent is identified: the check matches their user or contact id against responses already recorded for this survey, and someone who arrives without an identity is not blocked. It is not a per-device or per-browser limit.

Tip: The identity this check needs arrives as the session id that the Email and WhatsApp collectors add to the links inside each message. A respondent who opens a Web Link without one — from a newsletter or a social post — is not checked.

Passing data in the link

A Web Link can carry data in its query string — a respondent id, a source code, a name. Only parameters whose name matches a Custom Variable defined on the survey are stored with the response; anything else in the query string is ignored.

Custom Variables are not defined on the Share tab. Go back to the Design step, open the Settings menu and choose Variables (“URL parameters”). In the Custom Variables dialog, type a Variable Name and an optional Description, add the row, then click Save Variables. Names are lowercased, and any character that is not a letter, number or underscore becomes an underscore. See Survey Settings.

Once at least one variable exists, the link in the Web Link popup is shown with placeholders attached, for example https://surveys.surveyanalytica.com/s/<collector id>?name=[name_value]&email=[email_value]. Replace [name_value] and [email_value] with real values yourself before you send the link — nothing fills them in for you, and the popup has no field for entering values.

What a Web Link does not do

A Web Link is a plain, open URL. It has no expiry or open and close schedule, no password, no response limit of its own, no per-device restriction, and no anonymity setting. It also does not produce a personalised URL for each recipient.

To stop a link, set its status to Inactive in the collector table. There is no scheduled close.
To cap responses, use the survey-wide limit in the Publish step: its Response Goals tab has a Response Limit section with a Set maximum responses toggle, a Maximum Responses field and an Auto-close survey when limit is reached toggle. That cap covers the whole survey, not one link.
For links that identify who answered, use the Email or WhatsApp collector instead. Those append a session id to the survey link in each message, so the response is tied to the contact you sent it to.

5. QR Code

A QR collector turns your survey link into a scannable code for posters, receipts, table tents, packaging and anything else printed. You reach it at Share > Create Collector > QR Code, style it in a live preview, and download it as a single image file.

1Open the survey and go to the Share step. The collector table sits under the Distribution Channels heading.
2Click Create Collector. The button stays disabled until the survey is published, and an unpublished survey shows the warning Survey is not active, please publish before sharing this survey.
3Choose QR Code from the menu, captioned Generate QR codes for offline and print distribution. The menu lists only the channels belonging to the filter tab you are on, so start from All or Links; on a single-channel tab such as Email, the button creates that channel’s collector at once and shows no menu.
4The collector is created immediately, with no confirmation step, and the QR panel opens showing a live preview of the code.
5Set the colours and any routing options, then click Download and Save. You need both — see the warning below.

The QR panel with its live preview and Styling Options; Download keeps the colours, background image, language and variable value while Save keeps only the name and Disable Response Override, so click both before you close it.

The controls on the QR panel

The colours, the background image, the language and the custom-variable value all feed the preview as you change them.

Control	What it does
Name field (placeholder Name)	Names the collector in the table. A QR collector left unnamed is listed as `QR Code`.
Background	Colour behind the code, under the Styling Options heading. Defaults to `#ffffff`. It is a native colour swatch, so you pick from your operating system’s colour picker rather than typing a hex value.
QR Code	Despite its name, this is the colour of the code itself — the dark modules. Defaults to `#000000`, and is also a native colour swatch.
Background Image	Opens the Media library picker (images only) and places the picture behind the code in the preview. It is a backdrop, not a logo inside the code.
Disable Response Override	A toggle on the collector, and the one setting that both Download and Save keep.
Language dropdown	Shown only when the survey has more than one language. It lists raw language codes such as `en` and `de`, not language names, and your choice is baked into the link the code carries.
Custom variable key and value	Shown only when the survey defines custom variables. Pick a key and type its value; the values you set are appended to the encoded link as a query string.

What Download gives you

There is one download control, labelled Download, and it always produces a PNG named QR_Code.png. That filename is the same for every code of every survey, so rename the file as you save it if you are making more than one. The image is roughly 266 × 266 pixels: the code at its fixed 256-pixel size, plus a small margin.

The code encodes that collector’s own link on the platform’s default domain, in the form https://surveys.surveyanalytica.com/s/<collector id>. The QR image replaces the link list you get on a Web Link collector, so this panel shows no URL text and no copy button.

Warning: Save and Download save different things, and neither saves everything. Save keeps the name and Disable Response Override, but discards the colours, the background image, the language choice and the custom-variable value. Download keeps all of those, but discards a name you have just typed. Click both before you close the panel.

Note: The background image belongs to the preview, not to the code. Before committing anything to print, open the downloaded QR_Code.png and check it against what you saw on screen.

Printing the code

Keep strong contrast between the Background and QR Code colours, with the code darker than what sits behind it. The defaults — black on white — give you that contrast.
Scan the downloaded file with a phone before it goes near a printer, then scan a printed proof. Test the file, not the on-screen preview.
The code is always generated at the same fixed resolution, so print it at a size that keeps the individual squares crisp, and leave clear space around it.

What the QR collector does not do

PNG is the only export; there is no SVG or PDF on this panel.
There is no size, resolution or DPI control, no error-correction setting, and no centre-logo overlay.
You cannot choose the filename, and you cannot point the code at one of your custom domains — it always uses the platform’s default host, even where the Web Link collector offers your own domains.
There is no per-recipient or batch generation: one code per collector.
Scans are not reported separately. The row shows the same Opened and Responses counters as every other collector.

After the code is printed

A QR collector is listed under the Links filter tab, alongside Web Link and Download Survey collectors. Click its row, or use Edit in the row’s action menu, to reopen the panel and download the image again; that menu offers only Edit and Delete. The code carries the collector’s id, so a printed code cannot be redirected elsewhere — switching the row’s status toggle from Active to Inactive is the way to take it out of service.

6. Download Survey

The Download Survey collector produces a printable copy of your questionnaire. Choosing it creates a collector and starts the download straight away: there is no settings panel, no dialog and nothing to fill in first.

Note: The menu caption reads Download survey as HTML for offline use or embedding. What you actually get is a PDF, and it contains no embed code. Embedding is handled by the Website collector instead.

1Open the survey and go to the Share step. The survey has to be published first — until it is, Create Collector is disabled and the pane shows Survey is not active, please publish before sharing this survey.
2Click Create Collector. If you pick the Links tab first, the menu narrows to three cards: Web Link, QR Code and Download Survey.
3Click Download Survey. The collector is created immediately and the file starts building.
4Wait while the pane is covered by a dimmed overlay with a spinner. The spinner is the only feedback — there is no percentage, no stage text and no cancel button. The server allows up to 400 seconds for a survey to render. If it fails, the message is Download failed.
5Your browser saves the PDF. It is named after the new collector’s id, with a .pdf extension; you cannot choose the name in the product.
6The new row appears in the collectors table with the name Download.

A page of the PDF the Download Survey collector produces, rendered as a respondent would see it with the answer controls left blank — nothing written on the printed sheet returns to the platform.

Tip: Leave the tab open until the file arrives. Navigating away stops your browser waiting, but the server carries on generating the PDF and you will not receive it.

What is in the PDF

Every page of your survey becomes exactly one page of the PDF, rendered from the live survey as a respondent would see it, with the answer controls left blank.

Part of the page	What prints
Header	Your survey’s logo if you have set one, otherwise the SurveyAnalytica logo, with a QR code in the top-right corner.
Title block	The survey name and description. If the survey has an end date, a Survey Ends line with that date follows.
Body	The page title, then every question on that page as an empty control ready to be written on. Questions whose options are piped from an earlier answer are left out when they resolve to no options.
Buttons	None. There is no submit, next or previous button, and no progress bar.
Footer	Your survey’s terms and conditions text, or the default text when you have not set any, and a Powered By SurveyAnalytica link, on every page. If the survey has no logo of its own, a SurveyAnalytica strip is added below it.
Page size	Each PDF page is sized to the full height of the rendered survey page rather than to A4 or Letter, so a long survey page becomes one very tall PDF page.

There are no options

This is the only collector with no configuration at all. You cannot set a page range, paper size, orientation or margins; you cannot choose a different format; you cannot pick a language, name the collector, or leave out the logo, the QR code or the branding. The PDF reflects the survey’s own theme, logo, terms and conditions, and default language.

The collector row

A download collector behaves differently from the others in the table. Clicking the row’s type or name cell regenerates and downloads the PDF again rather than opening an editor, and so does Edit in the row menu. The row menu also carries a Download item, which does the same thing, and Delete, which removes the collector after a Delete Collector confirmation.

The collector also carries a working web link, so switching its status to Inactive stops that link resolving. It has no effect on PDFs you have already downloaded or printed. The OPENED and RESPONSES counts move only when someone opens that web link in a browser and answers online, so for paper-only use they stay at 0.

Answers written on paper do not come back

Warning: There is no scan, photograph or OCR path for a completed paper form. Nothing you write on the printed sheet reaches SurveyAnalytica through this collector.

The QR code on the PDF does not close that loop either: it encodes the survey’s internal id as plain text, not a web address, so scanning it with a phone camera returns an id rather than opening the survey. The PDF also prints no survey address a respondent could type in.

If you need the answers in the platform, plan for it up front:

Use the Web Link or QR Code collector for anyone who can answer on a device, and treat the PDF as a reading or reference copy.
Enter the paper answers yourself through one of those links.
The separate Import Survey Responses option on the survey import screen brings in existing responses from a Google Form. It does not read paper or scans.

Note: The survey setting Offline Responses is unrelated to this collector. It lets the online survey collect answers in the browser without a connection; it does not make the printed PDF submittable.

7. Website

The Website collector puts your survey on pages your visitors are already looking at. You choose how it appears, where the code is going, and what makes it show up; for a website the wizard hands you a single script tag to paste.

Start from Share > Create Collector > Website — the row reads Embed surveys on your website with popup or inline options. Create Collector stays disabled until the survey is published, with the warning Survey is not active, please publish before sharing this survey. Choosing Website opens a dialog titled Embed Survey with five steps: Embed Mode, Target Platform, Design, Trigger & Rules and Get Code. The steps are numbered circles at the top of the dialog, not tabs; the current step’s name is shown beside them, and hovering a circle shows its name. You can click back to a step you have already passed, but not forward.

The eight embed modes

Step 1 lists eight modes grouped under five category chips — Floating, Overlay, Inline, Redirect and Mobile — in the order below. NPS/CSAT Widget is selected when you arrive and is the only card carrying a Recommended chip.

NPS/CSAT Widget (Floating)

A small floating card showing one NPS or rating question. The visitor answers it in place and the card expands into the rest of the survey. There is no launch button. Choose it when you want a score from people who were not planning to take a survey.

Popover (Floating)

A launch button sits in the bottom right of the page and opens the survey in a floating popover. Choose it for an always-available feedback button.

Side Tab (Floating)

A launch button opens the survey in a floating panel. Choose it to keep the survey out of the way until it is asked for.

PopUp (Overlay)

The survey opens in the centre of the screen, over the page. Choose it when the survey is what you want the visitor to deal with next.

Slider (Overlay)

The survey slides in from the side of the screen. Choose it when a centre overlay would be too interruptive.

Standard (Inline)

The survey renders as part of the page, with no launch button. The script appends it to the end of the page body, so it lands at the bottom wherever you paste the tag.

New Page (Redirect)

A launch button opens the survey in a new browser tab, leaving your page as it was. Choose it for longer surveys that need the full window.

Mobile App (Mobile)

For a survey shown inside a mobile app’s WebView. Picking it narrows step 2 to iOS Native, Android Native, React Native and Flutter, and you get app source code instead of a web snippet.

Note: The preview on the right of the dialog is a mock website, not your survey. There are only two drawings: the widget and the PopUp. Popover, Slider, Side Tab, Standard, New Page and Mobile App all show the PopUp drawing.

Building the embed

1On Embed Mode, pick one of the eight cards, then click Next.
2On Target Platform, pick where the survey is going. Generic HTML is pre-selected. Click Next.
3On Design, set the appearance. Outside widget mode, Next stays disabled until Button Text has something in it.
4On Trigger & Rules, click a card under When to Show and add any display conditions you need.
5Click Generate Code. The collector is created at this point and the wizard moves to Get Code.
6Copy the snippet and paste it where the blue instruction on that step tells you, then click Done.

Warning: The collector is only written when you press Generate Code. There is no separate save — close the wizard before that step and nothing is kept.

The Embed Survey wizard on its Embed Mode step with NPS/CSAT Widget selected by default; the panel on the right is a mock website used to illustrate the mode, not a preview of your own survey.

Target platform

Ten platform tiles are grouped under Web, CMS Platforms, E-commerce, Native Apps and Hybrid / Cross-Platform. The choice changes the code you are given and the paste instruction on the last step; it does not connect to or publish anything on the platform itself.

Platform	What you get	Where the wizard tells you to put it
Generic HTML	The script tag	Add this script to your website’s HTML head section.
WordPress	The script tag, plus a `[surveyanalytica id="…" type="…"]` shortcode line	Add to your theme’s header.php or use a plugin like ‘Insert Headers and Footers’.
Wix	The script tag	Go to Settings > Custom Code > Add Custom Code > Head section.
Squarespace	The script tag	Navigate to Settings > Advanced > Code Injection > Header.
Shopify	The script tag	Add to theme.liquid before </head> or use our Shopify app.
Webflow	The script tag	Add to Project Settings > Custom Code > Head Code.
iOS Native, Android Native, React Native, Flutter	WebView source code to paste into your app — Swift with `WKWebView`, Kotlin with a WebView fragment, `react-native-webview`, or `webview_flutter`. Each wraps the same script tag in an inline HTML page.	—

Note: The embed script has no renderer for Mobile App mode, so the four app snippets are scaffolding for your developers to build on rather than a finished embed.

Note: Reopening a saved website collector restores the mode, the design and the trigger, but the platform resets to Generic HTML. Re-pick it before you copy the code again.

Design

For every mode except the widget you get a Button Settings group — Button Text (default Click Me), Background Color, Text Color, Border Radius (a slider from 0 to 50, shown in the caption as Border Radius (8px)) — and a Button Preview underneath. Button Position is shown but permanently disabled: each mode has a fixed position. Standard mode never draws a launch button, so its button settings have no effect, but Button Text is still required before you can move on.

For NPS/CSAT Widget the button group is replaced by Widget Settings:

Widget Position — Bottom Right, Bottom Left or Bottom Center.
Background Color and Text Color. The 0–10 buttons keep their fixed red, amber and green colours.
Show Inline Question First — on by default. Turning it off hides the question picker below it.
Inline Question — lists only the NPS and rating questions in your survey. The empty choice, Default NPS question, shows a generic 0–10 prompt whose answer is not carried into the survey; picking one of your own questions passes the visitor’s answer to the survey in the URL. If the survey has neither question type you see This survey has no NPS or rating question to show inline instead of the picker.
Remember Dismissal — on by default. When a visitor closes the inline card, the widget does not come back in that browser.
Auto-show Delay — 0 to 10 seconds, default 3 seconds. It only applies when Show Inline Question First is off.

Trigger and conditions

In every mode with a launch button, a visitor can click it to open the survey. A trigger is an extra rule that opens the survey on its own. Pick one card under When to Show.

Trigger	What happens on the page
Page Load	Show immediately when page loads.
Scroll Depth	You set a Scroll percentage (default 50). At runtime the survey opens as soon as the visitor scrolls at all — the percentage you set is not applied.
Time Delay	You set Delay (seconds) (default 5), and the survey opens that many seconds after the page loads.
Exit Intent	The survey opens when the visitor’s pointer moves as if to leave the page. Display Conditions are not applied to this trigger.

Warning: Page Load looks selected when you arrive, but a trigger is only recorded when you click a card. Walk past this step without clicking and the collector is saved with no trigger, so the survey opens only when a visitor clicks the launch button.

Display Conditions narrow where the trigger is allowed to fire. Click Add Condition to add a row, choose a Condition Type — Page URL, User Logged In or Custom Attribute — then a Matcher (Equals, Not Equals, Contains, Starts With, Ends With) and a Value; a Page URL row shows /pricing as its placeholder. Custom Attribute adds an Attribute Path field that reads a value from the visitor’s browser storage, for example localStorage.userTier. Every condition you add must be true — they are combined with AND, and there is no OR, no grouping and no nesting. With no rows you see No conditions set. Survey will show based on trigger only. A User Logged In row has no field for the storage key it needs, so it never matches.

The last section, Additional Options, holds a single switch, Hide After Completion. It is stored with the collector, but nothing on the page acts on it.

Note: This whole step is ignored for NPS/CSAT Widget. The widget runs from its own Widget Settings on the Design step; the trigger and any conditions you set here are not applied to it.

Getting and pasting the code

Step 5 opens on Embed Code Generated! with three tabs — Embed Code, Direct Link and QR Code — a Copy button, a blue alert naming the exact place to paste, and the Collector ID at the bottom. For every web platform the snippet is a single script tag, shaped like this:

<script defer crossorigin="anonymous" src="https://…/shareButton.js?type=…&bColor=…&radius=…&bText=…&backColor=…&id=…&bType=…"></script>

Paste it into the head of every page the survey should appear on, or into the site-wide header your platform provides; the alert on this step names the setting for the platform you picked. The script builds the survey frame itself once the page loads, so there is nothing else to install. The other two tabs give you the same survey as a link, and as a QR code with Download PNG and Download SVG.

Tip: The wizard does not ask for a name, so every website collector is listed as Website. If you run several, note each Collector ID from step 5 against the page you put it on.

What the Website collector does not do

There is no mode called Full Page. New Page opens the survey in a new browser tab and Standard embeds it in the page.
There is no plain <iframe> or JavaScript-free snippet. Every web platform gives you the script tag.
The [surveyanalytica] shortcode printed in the WordPress snippet has no handler in the product. Paste the script tag instead.
There is no frequency capping — no impression limit, session limit, cool-off period or “show once every N days”. The widget’s Remember Dismissal is the only repeat suppression, and it applies to that mode only.
There is no device, location, referrer or new-versus-returning-visitor targeting. Display Conditions are the only targeting available.
There is no control over the size, width, height or font of the widget or the popup, and no A/B testing or traffic sampling.
Button Position cannot be changed; each mode fixes it.

8. Email

The Email collector sends your survey to a contact list as a designed email campaign, then tracks delivery, opens and clicks against that collector. You build it in a full-screen dialog titled Email Campaign, in two phases: pick a template, then fill in one configure-and-send form.

1Publish the survey first. Create Collector stays disabled until you do, and the Share pane shows Survey is not active, please publish before sharing this survey.
2Go to Share > Create Collector and choose Email — Distribute surveys through email campaigns with tracking. On the Email filter tab there is only one channel, so the click skips the menu. The collector is created immediately and the Email Campaign dialog opens.
3Under Choose an Email Template, search with Search templates… or use a category chip, click a card to preview it, then click Apply. The gallery is not filtered to email designs — landing pages, blog posts and other page types appear in it too.
4Fill in the form that replaces the gallery. Change template, top left, returns you to it while the collector is still new.
5Under Create email template, click the pen icon on the first row to open Edit Email Template and edit the body in the drag-and-drop designer.
6Click Create Campaign to send, or to register the schedule if you set one.

The Email Campaign form, where the language buttons under Campaign Languages decide which language’s subject, contact list, attachment and schedule you are editing — step through every one before you click Create Campaign.

The campaign form

Everything below Campaign Languages is stored per language. A multi-language survey gets one button per language and a separate subject, contact list, attachment and schedule for each; the campaign body is machine-translated into every survey language when you apply the template.

Field	What it does
Campaign Name	Editable in place; Created By beside it is read-only.
Campaign Languages	One button per survey language. The selected button sets which language the rest of the form edits.
Contact List	A dropdown of up to 20 lists, each with its contact count; the first entry is Select. Edit appears once a list is chosen, and + Contact List opens a Create Contact List dialog. See Contact Lists.
From Name	The sender display name, default `SurveyAnalytica Mailer`. On a free plan the field is disabled and a caption below it reads A custom sender name is available on paid plans. Free accounts send under your organization name.
From Email	An autocomplete with the placeholder Select a sender…, listing your verified addresses plus the platform default `notifications@surveyanalytica.net`. + Add email account opens Add Sender: pick a verified domain, type a Username for the local part, choose a Workspace if the domain is shared, then Use this address. Manage sending domains links out — see Sending Domains.
Email Subject	Required. Stored per language.
Email Attachment	A drop tile for one file. No file type or size is enforced in the interface, but the whole collector travels in a request capped at 10 MB, so keep it small. A trash icon clears it.
Schedule	Read-only, showing Start Immediately until you set one. The Schedule button opens two tabs: Date & Time, a picker that cannot go earlier than today and commits when you accept it, and Cron, an expression builder pre-filled with `30 5 * * 1,6` and carrying Save and Clear. A schedule fires once for the whole campaign; there is no per-recipient local-time delivery.

Note: Recipients are exactly one contact list per campaign language. There is no segment picker, no filtering or sampling of the list, no way to type an address by hand, and no cc or bcc. Contacts are de-duplicated by email address, and anyone who has unsubscribed, complained or previously bounced is skipped before sending.

Personalising the message

Merge tokens use single braces, for example {name}. In the designer’s text toolbar, the Embed Data button (an icon whose label shows as a tooltip) lists what you can insert: the survey’s custom variables plus the fields on the contact list you selected, so choose the list first if you want its fields on the menu. If there is nothing to offer, the button does not appear. Token names match your list’s field names, so {firstName} works only if your list has a field called firstName. At send time each token is replaced with that recipient’s value; a token that matches nothing is left visible in the delivered email rather than blanked out.

Warning: Tokens are merged into the email body only. The Email Subject is sent exactly as typed, so {name} in a subject line arrives as the literal text {name}.

Note: Only two gallery designs carry an unsubscribe link of their own. For the rest the platform appends its own unsubscribe footer at send time and then shows No unsubscribe link in your template — the platform appended one; it warns, it does not block. A send to a contact list is refused until your organization has a postal address on file, shown as Add your postal address with an Open organization settings action.

Reminders

Under Create email template, the first row is the main email and can only be edited. + Reminder adds a follow-up and opens the Reminder popup: Remind after a number of days, Send to either Non-respondents only or All contacts, its own subject, and a template from the chips or from Browse All Templates. Reminder rows have their own schedule, edit, clone and delete icons.

Save for later, or Create Campaign

Create Campaign validates the form, then sends or registers your schedule. Missing values come back in one message: Email subject is required, Please select a contact list, Sender email is required, From name is required. Only the selected language is checked, so on a multi-language campaign step through every language button before you send.

Warning: Save for later skips validation and saves the collector as inactive. If you re-open a campaign that is already live and press Save for later, you deactivate it.

Tracking what happened

The Delivery Analytics card in the form holds six counters, in this order: Sent, Delivered, Opened, Clicked, Bounced, Complaints. Underneath, four rates appear once something has been sent: Delivery Rate, Open Rate, Click Rate and Bounce rate. Open Rate is measured against delivered messages and Click Rate against opens, not against sends. A Campaign Progress bar appears above the card once a send exists.

View Details, or the progress bar on the collector row, opens the Campaign Progress dialog: a status chip, a phase label, timestamps, and a Delivery Metrics block of Total Contacts, Sent, Delivered, Read, Failed, Bounced, Complained and Skipped, with Delivery Rate, Read Rate and Failure rate. Two tabs, All Messages and Failed Messages, list per-recipient rows with Recipient, Status, Queued At and Attempts; Refresh and Close sit in the footer.

Tip: The Opened column in the Share collector table is that collector’s own counter, not the email open count. Read email opens from Delivery Analytics inside the campaign.

What the Email collector does not do

There is no test send and no send-to-myself preview. The only way to see the delivered email is to launch the campaign.
There is no A/B subject-line testing and no automatic winner.
There is no send-time optimisation. Scheduling is a date and time, or a cron expression, that you set yourself.
There are no segments and no manual recipients — one contact list per language — and no cc or bcc.
You cannot save a design from here as a reusable template. The Reminder popup can pick saved templates, but nothing in this collector writes one.

9. WhatsApp

A WhatsApp collector sends your survey to a contact list from a connected WhatsApp Business sender. Pick it from Share > Create Collector > WhatsApp — described in the menu as “Send surveys via WhatsApp messages with automated flows”. A collector row is created and a full-screen WhatsApp Campaign dialog opens on a six-step wizard: Setup, Method, Template, Audience, Mapping, Review.

What the wizard requires

You cannot skip ahead — Continue stays disabled until the current step is complete, and while you can click backwards on the step bar you can never click forwards. What is enforced:

The survey must be published. Until it is, Create Collector is disabled and the Share tab shows “Survey is not active, please publish before sharing this survey”.
A Campaign Name and a sender chosen under WhatsApp Sender.
A distribution method.
A template — and, for Native Flow, a flow synced to Meta first.
A contact list.

The Mapping step never blocks you. There is no plan or quota gate on this collector, and nothing in the wizard shows message cost or a remaining balance.

Native Flow or Survey Link

Step 2 offers exactly two options, and the choice decides what the respondent does and which of your questions survive.

Native Flow — chip Recommended

“Survey rendered inside WhatsApp as an interactive form. No browser needed.” The message carries a Start Survey button.

Survey Link — chip All question types

“Template message with URL button. Opens the full survey in browser.” The button reads Take Survey and points at https://surveys.surveyanalytica.com/s/<collector id>.

	Native Flow	Survey Link
Where the respondent answers	In the WhatsApp conversation, without leaving the app	In a browser, on the collector’s survey link
Question types	Several are converted, downgraded or dropped	The survey exactly as you designed it
Template needed	One carrying a Flow button; only those are offered	The generated template carries the URL button; templates holding another survey’s Flow button are hidden
Extra setup	The flow must be created and published to Meta from the Template step	None beyond the template

A Native Flow opens on a generated welcome screen titled with your survey name and a Start button; each survey page becomes one screen, footed with Continue and, on the last page, Submit. The flow preview in Review shows a yellow bar counting “<n> adaptation(s)” and any “<n> unsupported rule(s)”, which expands to the individual conversions:

Question type	Inside a Native Flow
`MULTISELECT_DROPDOWN`	Becomes a checkbox group
`SLIDER`	Becomes a radio button group
`MATRIX`	Becomes one radio button group per row
`IMAGE_CHOICE`	Radio buttons or checkboxes — “Images omitted”
`RANKING`	Radio button group — “Top-choice only”
`BARCODE`	Text input — “Scanner not supported”
`DATETIME`	Listed as “DatePicker + TextInput: Split date/time”, but only the date picker renders
`APPOINTMENT`	“DatePicker + TextInput: Basic fallback”
`PAYMENT`, `PRODUCT_CARD` without options, `SIGNATURE`	Skipped — “Not supported in Flows UI”

Note: Skip logic inside a Native Flow needs a configured HTTPS endpoint; without one the flow falls back to static page order and the sync reports that the rules are disabled. If your survey depends on branching, use Survey Link. Note too that the link button always uses surveys.surveyanalytica.com — a custom domain set up under Domains is not applied to this collector.

Build the campaign

1Setup. Enter a Campaign Name (up to 120 characters) and an optional Description, then pick a number in WhatsApp Sender (“Select a WhatsApp sender…”). The + icon, tooltip “Create a new Sender”, starts Meta’s embedded sign-up so you can connect a number without leaving the dialog.
2Method. Click the Native Flow or Survey Link card.
3Template. For Native Flow, handle the flow panel first: “Flow not created” offers Create & Sync Flow; “Flow exists (status: <status>)” offers Update & Publish or Update Draft; when done it reads “Flow synced & published” with the flow ID and a Re-sync button. Then click Customize & Create for a generated invite template, or Use Existing Template for the WhatsApp Message Builder picker (Change template swaps your choice). In the editor set Template name (helper text “lowercase_with_underscores”), a Category of UTILITY, MARKETING or AUTHENTICATION and a language; edit the Body (up to 1024 characters), where + Add variable inserts {{1}}, {{2}} and so on and each needs a value under Variable samples. Publish submits the template to Meta for review.
4Audience. Pick a list in “Search contact lists…” — each option shows its contact count and a Static or Dynamic chip; Create Contact List builds one on the spot. With nothing chosen the card reads “No audience selected”. See Contact Lists.
5Mapping. For an image, video or document header, stage a file on the dropzone — it names the format your template uses, as in “Drag & drop or click to upload (IMAGE)” — then press Upload, or use Choose from media library below the OR divider. Map each variable — the fields read Header {{1}}, Body {{1}} or Button "Take Survey" (URL suffix) — to a contact list field, or type a fixed value. A template with no variables and no media header shows “No template variables to map”.
6Review. Check the summary and checklist, optionally set a schedule, then send.

The WhatsApp Campaign wizard on its Method step, the choice that decides everything downstream: Native Flow answers inside WhatsApp but converts or drops several question types, while Survey Link opens the survey exactly as you designed it in a browser.

Tip: Fill the mapping in yourself. Left empty, the send fills the template variables by reading the first contact in the list and matching its field names positionally.

Review and send

The Review step puts a Campaign Summary (campaign, Sender, Method, Template, Audience) and a Readiness Checklist beside a phone preview. The checklist covers “Campaign named”, “Sender configured”, “Template ready”, “Audience selected”, “Flow synced” for Native Flow, and a template line reading “Template approved”, “Template <status>” or “Template status unknown”. For Native Flow, Message and Survey chips switch the preview between the message bubble and a live render of the flow.

When the template is not approved a warning sits above the buttons: Your template is currently “<STATUS>”. WhatsApp requires templates to be approved before sending. Please wait for approval or use an approved template. Send Campaign is disabled with the tooltip “Template must be approved by WhatsApp before sending”. If no status can be resolved at all — the “Template status unknown” case — the button stays enabled. Set Schedule adds a date and time.

Warning: Save Draft is not a draft. Both Send Campaign and Save Draft submit the campaign for sending; they differ only in whether the collector is left active. On a fully configured campaign, Save Draft starts the send.

Sending runs in the background and the dialog confirms at once with “Message Sent Successfully”, or “Message Scheduled Successfully” for a scheduled campaign. Recipients are de-duplicated by phone number, and a contact with no phone number is skipped without notice. Once sends exist the dialog header shows Sends, Delivered, Opens, Clicks and Bounced; a metric sitting at zero is hidden rather than shown as 0, and the whole strip is hidden on narrow screens. The collector row reports only Opened and Responses. For messaging with respondents, see Conversations — Omnichannel Messaging.

Flow status, Re-sync and Delete

On the All and WhatsApp tabs the collector table has a Flow column showing No Flow, Published, Draft or Deprecated, read live from Meta; any status the page does not recognise is displayed as Draft, and non-flow collectors show a dash. The row’s menu offers Edit and Delete, plus Re-sync Flow and Delete Flow on Native Flow collectors. Re-sync Flow rebuilds and republishes the flow from the survey and confirms with “WhatsApp Flow re-synced successfully” — run it after you edit the survey so the flow matches the questions you are now asking.

Warning: Delete Flow opens “Delete WhatsApp Flow?” and warns: “This will permanently remove the flow from Meta. WhatsApp collectors using Native Flow distribution will stop working until a new flow is created.” It adds that “The collector itself will NOT be deleted. You can re-sync to create a new flow later.” One flow is shared per survey, so deleting it stops every Native Flow collector on that survey, not only this one.

Deleting the collector leaves the flow in place. That dialog tells you “The WhatsApp Flow for this survey will NOT be deleted. Other collectors can still use it.”

What this collector does not do

No test send. The only rehearsal is the phone preview and, for Native Flow, the interactive flow preview.
No per-recipient delivery or read list, and no failure or bounce detail — only the aggregate counters above.
No phone-number format check. The number stored on the contact is the number that is sent.
No throttle, send-window or batch-size control.
Scheduling is a single date and time. There is no recurring schedule.
No opt-out control in this wizard, and the WhatsApp send does not filter the list by unsubscribe status — every contact with a phone number is messaged. Remove anyone you must not contact from the list before you send.

There is also no SMS collector on the Share tab; SMS lives as a flow action and as your own connected number under Domains, covered in Connect Your Own SMS Number.

The Social Media collector puts your survey on social platforms, and on three of them reports the engagement the post earns. The survey must be published before you can create it; there is no plan gate on this collector in the interface.

Open it from the Share tab. On the Social tab, Create Collector opens the dialog straight away; on the All tab it opens a menu, where you choose Social Media (“Post surveys across social platforms and track engagement”). The dialog is titled Share on Social Media and offers two modes on a tab bar: Quick Share, selected by default, and Advanced Post, which carries an API chip. They work very differently. Quick Share opens the platform’s own share window with your survey link filled in — SurveyAnalytica posts nothing and no account is connected. Advanced Post publishes through the platform’s API using an account you connect, and only that mode can return engagement metrics.

The two modes of the Share on Social Media dialog — Quick Share opens the platform’s own posting window and publishes nothing on your behalf, while Advanced Post publishes through the API and is the only mode that can report engagement back.

Under Select a Channel (“Choose a platform to quickly share your survey. The share dialog will open in a new window.”) you get eleven cards, in this order: Facebook, Twitter / X, LinkedIn, Instagram, Slack, Microsoft Teams, Messenger, WhatsApp, Telegram, Reddit and Pinterest. Pick one and a Customize & Share block appears with a Title field, prefilled with your survey’s name, a Description field, prefilled with its description, and a coloured Share button. That button opens the platform’s own posting window with the survey link already in it. You finish the post on the platform.

Warning: Four of the eleven cards — Instagram, Slack, Microsoft Teams and Messenger — do not open a share window. The Share button below them renders empty and nothing happens. Instagram, Slack and Microsoft Teams can be posted to from Advanced Post instead; Messenger cannot be posted to from this collector at all.

Note: Clicking a card creates the collector row, filed under the Social tab and stamped with that channel — but only when the survey has no social collector yet. If one already exists, the dialog reuses it and no new row is created. Picking a different card afterwards changes what you share, but does not update the channel recorded on the row.

Advanced Post is a four-step wizard that publishes the post for you.

1Select Platform. Choose one of seven cards: Facebook (“Post to your Facebook Pages”), Instagram (“Share to Instagram Business accounts”), Twitter / X (“Tweet to your profile”), LinkedIn (“Post to your profile or company page”), Slack (“Send messages to Slack channels”), Microsoft Teams (“Post to Teams channels”) and Messenger (“Send via Facebook Messenger”). You post to one platform per publish. Click Next.
2Connect Account. Connect Account opens a sign-in popup for that platform; until you connect one, the panel reads “No accounts connected for this channel.” Connected accounts then appear under Connected Accounts — click one to select it. For Slack and Microsoft Teams a second picker appears (Select Slack Channels / Select Teams Channels, “Select where to post…”), and you can choose more than one channel. For the other platforms the account itself is the destination and a Ready to post alert confirms it.
3Compose Your Post. Write the message, add hashtags, keep or switch off Include Survey Link, and add media where the platform allows it. A panel headed “Preview on” plus the platform name shows an approximation of the result; on a narrow screen that panel is hidden.
4Publish. Under Ready to Publish, click Publish Now. On success you see “Published Successfully!” and, where the platform supports it, the Engagement Metrics panel. Done closes the dialog.

What the compose step gives you:

The message box is prefilled with “We value your feedback! Please take a moment to complete our survey:” followed by your survey’s name.
Two chips sit under the box behind the label Insert variable. Survey Name and Survey Link insert the literal text {{surveyName}} and {{surveyLink}}. Nothing replaces those tokens when the post goes out — they appear on the platform exactly as typed. Use the Include Survey Link toggle to add the link, and type the survey name yourself.
Hashtags start with #survey and #feedback. Six suggestions are offered as chips: #survey, #feedback, #customerfeedback, #research, #opinion and #yourvoicematters. Entries are lowercased, de-duplicated, and a leading # is stripped.
A live counter shows your length against the platform limit: 280 for Twitter / X, 2,200 for Instagram, 63,206 for Facebook, and 3,000 for LinkedIn, Slack, Microsoft Teams and Messenger. Going over shows “Message exceeds character limit” but does not block publishing. The count is an approximation.
Media Attachments appears only for Facebook, Instagram, Twitter / X and LinkedIn. You paste a public image or video URL (“Paste image or video URL”); there is no file upload. Instagram will not let you continue until you add at least one.
The post is assembled as your message, then the hashtags, then the survey link, separated by blank lines.

Warning: Publishing to Messenger cannot complete. The send request requires a recipient id that this dialog never sends, so the request is rejected and the failure is shown in the dialog.

Note: Slack and Microsoft Teams posts are queued for delivery rather than sent while you wait, so “Published Successfully!” means accepted, not yet visible. Facebook, Instagram, Twitter / X and LinkedIn are sent immediately. Once a survey has a published social post, reopening the collector returns you to that post’s summary — there is no control for publishing a second one.

Metrics come from the platform, and only Advanced Post produces them. This is what each platform does in each mode:

Platform	Quick Share	Advanced Post	Metrics reported
Facebook	Opens the share window	Yes	Likes, Comments, Shares, Reactions, Reach, Impressions
Twitter / X	Opens the share window	Yes	Likes, Retweets, Replies, Quotes, Impressions, Bookmarks
LinkedIn	Opens the share window	Yes	Likes, Comments, Shares, Impressions, Clicks
Instagram	Card present, nothing opens	Yes, media required	None returned
Slack	Card present, nothing opens	Yes, choose channels	None returned
Microsoft Teams	Card present, nothing opens	Yes, choose channels	None returned
Messenger	Card present, nothing opens	Card present, publishing fails	None
WhatsApp	Opens the share window	Not offered	None
Telegram	Opens the share window	Not offered	None
Reddit	Opens the share window	Not offered	None
Pinterest	Opens the share window	Not offered	None

Where metrics exist, they appear in two places. The Engagement Metrics panel in the dialog shows a card per metric, a Post ID line and a Refresh Metrics button, and refreshes itself every minute; large numbers are abbreviated, and a value the platform has not returned shows as a dash. In the collector list, the same post shows three compact badges under the collector’s name, refreshed every five minutes — Likes, Retweets and Replies for Twitter / X, and Likes, Comments and Shares for Facebook and LinkedIn. Instagram, Slack and Microsoft Teams posts publish, but the publish response carries no post identifier the product can track, so the metrics panel does not appear in the dialog and the collector row shows no badges.

Tip: If you need engagement numbers back in SurveyAnalytica, publish through Advanced Post on Facebook, Twitter / X or LinkedIn. Everything else is a way to get the link out, not a way to measure it.

No scheduling. “Schedule posts for later” is listed under Platform Features on step 1, but there is no date or time control anywhere in the dialog. Publish Now posts immediately.
No file upload for media. Images and video are added by pasting a public URL.
No variable substitution. {{surveyName}} and {{surveyLink}} are published as literal text.
No API posting for Pinterest, Reddit, Telegram or WhatsApp — those are share links only. Tumblr does not appear in this collector at all.
No cross-posting. You cannot publish to Facebook and LinkedIn in one action; the multi-select applies only to channels within Slack or Microsoft Teams.
No editing, deleting or reposting from SurveyAnalytica after publishing, and no draft or approval step before it.
No way to disconnect an account here. Step 2 adds and selects accounts but offers no disconnect or re-authorise control.
No metric history, trend chart or export, and survey responses are not among the metrics — these are the platform’s engagement counts only.

11. Shopify

The Shopify collector connects a .myshopify.com store and puts your survey on the storefront — either by letting SurveyAnalytica add a script to the store for you, or by handing you a survey URL to place in a theme app block yourself. It runs as a four-step window: Connect Store, Integration Type, Configure, Deploy.

1Publish the survey first. Create Collector stays disabled until you do, and the Share tab shows Survey is not active, please publish before sharing this survey.
2Go to Share > Create Collector and choose Shopify. On the Integrations filter tab, Shopify is the only channel, so the button opens the Shopify window directly.
3On Connect Store, select a store under Connected Stores or click Connect New Store. If stores are already connected, the first one is selected for you.
4Click Next, then on Integration Type click Storefront Embed.
5Click Next. The collector is created and you land on Configure Placement, where you pick a Template and a card under Select Target Section.
6Click Next to reach Deploy to Shopify, then use either the Auto-Deploy or the Manual Setup tab. A new collector opens on Manual Setup.
7Click Done. The collector appears in the Share table as a row named Shopify, with an Active toggle and Opened and Responses counts.

The Shopify window’s Deploy step, contrasting Auto-Deploy, which puts a built-in recommend question on every storefront page, with Manual Setup, where you paste the survey URL into an app block you place yourself.

Connecting a store

Click Connect New Store, type the store name into Shop Domain — the field shows the placeholder mystore, a fixed .myshopify.com suffix and the helper text Enter only the store name without .myshopify.com — then click Connect. A popup opens Shopify’s authorisation screen. The permissions you grant appear as chips on the store card beside a green Connected chip; Read your Shopify Customers and Embed Survey in your Shopify Store are two of them, and any beyond the first three collapse into a +N chip.

Note: If the popup closes and no store appears under Connected Stores, the connection did not complete; no error is shown, so try again. There is no control for disconnecting or removing a store once it is listed.

The two integration types

Storefront Embed

Badged Recommended. This is the path that continues through the wizard: it creates the collector and takes you on to Configure and Deploy.

Automation Flow

Not an integration. Clicking this card closes the Shopify window and takes you to the flow designer. No collector is created and nothing about your store is carried across.

The chips printed on each card — including Order completed, Customer signup and Visual customization — are labels only; nothing in the wizard acts on them. To send surveys off store events, build the flow yourself: see Flows and Automation.

What the Configure step controls

Template defaults to Product Page and also offers Cart Page, Checkout Page, Collection Page, Home Page, Article Page, Blog Page and Search Page. Select Target Section defaults to New App Section and also offers Main Section, Header Section, Footer Section and Aside Section. Both choices do one thing: they build the link behind Open Theme Editor on the Manual Setup tab, so Shopify’s theme editor opens on the right template with the app block ready to add. Auto-Deploy ignores them.

Warning: Reopening a Shopify collector jumps straight to Configure, but a changed Template or Select Target Section is not saved on an existing collector. Clicking through this step also sets an inactive collector back to Active.

Auto-Deploy compared with Manual Setup

	Auto-Deploy	Manual Setup
What you do	Click Deploy Now; a script is added to your store.	Copy the survey URL, click Open Theme Editor, add the block by hand.
Where it appears	Every storefront page — the panel says The survey will appear on all pages.	Where you place the block: `<template> → Add Section → SurveyAnalytica`, pasting the survey URL into the block’s Survey URL field.
What shoppers see	A bubble at the bottom right that expands after three seconds into a built-in question, How likely are you to recommend us?, on a 0–10 scale labelled Not likely and Very likely. Your own questions appear only if the shopper clicks More questions →.	Your survey, at the URL you pasted.
Placement control	None; all pages or none.	Full, through the theme editor.

A successful deploy shows Deployed successfully! and a Script ID, and disables the button for the rest of that session; reopen the collector to deploy again, where it reads Update Deployment. If a shopper closes the auto-deployed survey, it does not return in that browser. Manual Setup also carries a Watch Video Tutorial button, which links out to the help site rather than playing in the app, and a Survey QR Code card for previewing on a phone.

Warning: There is no undeploy control. Switching the collector to Inactive or deleting it does not remove the script from your store.

What this collector does not do

No order-status or thank-you page placement; the Template list has no such option.
No post-delivery or order-fulfilled trigger, and no cart-abandonment trigger. There is a Cart Page template, but no abandoned-checkout event.
No per-page targeting for Auto-Deploy, and no display rules such as URL matching, scroll depth, exit intent or scheduling.
No visual customisation of the auto-deployed widget, and no way to choose which of your questions it shows.
No name field, so every Shopify collector is listed as Shopify.

12. Response settings, restrictions and goals

None of the settings that govern who may answer, how often, and for how long live on the Share tab. They are split between the Publish step and the Design step. This section is the map.

A map of the survey builder’s five steps showing that response behaviour toggles live under Design and Settings while limits, restrictions and dates live under Publish — the Share tab holds only the collectors themselves.

The Publish step opens a screen headed Publish & Settings. Its header carries Restriction, Un Publish and Publish (which reads Published once the survey is live, next to the alert Your survey is live and accepting responses.), and four tabs sit below it.

Setting	Where it lives	What it does
Restriction	Publish > Restriction	A popup listing your restrictions (Restricted By, Value, Provider, Actions) with Save, Add and Upload. Add offers five types: Email Domain, Email, Location, Registered, Mobile Phone. Email Domain and Email also take a Login Option provider; Location takes a radius (default `20`) around a place picked with Search Location; Registered puts a login prompt in front of the survey. Restrictions save with the survey.
Survey End Page	Publish > Survey End Page	Read-only: a Current End Page chip and the notice End Page designer has moved!, pointing at Design tab → Right toolbar → End Page. See Survey End Pages and Thank You Screens.
Schedule	Publish > Schedule	Schedule Settings, with Select Start Date and Select End Date — the only close-date control. A survey whose end date has passed cannot be published, and submissions outside the window are rejected.
Options	Publish > Options	Response Options holds one toggle, Allow Response Download. Feedback Collection holds Feedback, which adds a yes/no question after completion; an Add Question button appears once Feedback is on and a feedback question exists.
Response Goals	Publish > Response Goals	Section Response Limit: Set maximum responses (it seeds a target of 100), the field Maximum Responses (minimum 1), a Use sample size calculator link, and Auto-close survey when limit is reached. Published surveys also show a Current Responses counter. Turning the toggle off clears the target and the auto-close setting.
Sample Size Calculator	Publish > Response Goals	Confidence level 90, 95 or 99 (default 95), margin of error (default 5), expected proportion (default 50); population size may be left blank for infinite. Apply as Target writes the result into Maximum Responses.
Rewards	Publish > Response Goals	Enable rewards for respondents reveals Number of vouchers to award, a reward description, and a choice of Upload My Codes (a `.csv` or `.txt` file) or Generate Codes.
Allow Multiple Responses	Design > Settings	Lets a respondent submit more than once. Off by default.
Track Location	Design > Settings	Records the respondent’s geographic location with each response; the survey page then asks the browser for a location before submitting.
Collect Partial Responses	Design > Settings	Switches on collection of partial responses. The same toggle appears in the Settings dropdown and in the full Survey Settings dialog.
Allow Response Editing, Edit Window (hours)	Design > Settings > Open Full Settings	Lets a respondent change a submitted response. The window takes a minimum of 1 hour; its helper text reads Leave empty for unlimited editing time.
Max Attempts	Design > Test Configuration > Attempts & Retakes	Caps retakes between 1 and 100; empty means unlimited. It applies only when Allow Multiple Responses is on, and Test Configuration only appears when the survey’s category is Test or Quiz.

To reach the Design-step settings in that table:

1Go to the Design tab.
2Open the toolbar Settings dropdown, headed Survey Settings. It carries eight toggles, among them Track Location, Allow Multiple Responses and Collect Partial Responses.
3Click Open Full Settings. The Survey Settings dialog is the only place Allow Response Editing and Edit Window (hours) appear. See Survey Settings.

Note: Response Limit and Rewards are read-only on the Standard plan, where both sections are replaced by a card headed Professional Plan Required. On a narrow screen the step tabs collapse into a dropdown, and on the Design and Preview steps a Settings item in the mobile actions menu opens the Survey Settings dialog directly.

Response editing and retakes

Allow Response Editing does not produce a link you can send. The respondent asks for one themselves, from their responses list in the participant portal, where an Edit response action opens the survey for editing inside the portal; after the window closes it reads Edit window has expired.

That link is single-use and lasts two hours by default, or less if the survey’s edit window ends sooner. It is marked used only when the edited response is submitted, so reloading part-way through does not burn it, and it is tied to the device that requested it — opened elsewhere it is refused with This edit link can only be used from the device that requested it. Leaving Edit Window (hours) empty removes the deadline for requesting a link, but each link still expires.

What a re-submission does to the original depends on Allow Multiple Responses. With it off, the response is keyed to the respondent, so a second submission from the same identity replaces the first. With it on, each submission is stored separately. For anonymous respondents that identity is an id the survey page keeps in a cookie for 365 days, so clearing cookies or switching browser produces a new one, and a new response.

The response goal itself is enforced at submit: past the maximum, the survey answers This survey has reached its response limit and is no longer accepting responses. Auto-close survey when limit is reached additionally takes the survey out of the published state at that point.

Settings that do not exist

There is no survey password or passcode.
There is no IP allow-list. A response records the respondent’s IP address, but nothing restricts access on it.
There is no one response per device setting. The nearest behaviour is the default state of Allow Multiple Responses, which works per respondent identity, not per device.
There is no in-product button for you to issue a response-edit link; only the respondent can request one.

13. Tracking and attribution

A response is attributed to a collector by the share code in the link the respondent opened, which is stored on the response as a single field. This one mechanism explains what the counters on the Share tab mean and how far per-channel reporting goes.

The code after /s/ in a collector URL is the collector’s own id. When someone opens that URL and submits, the survey page reads the code out of the address and stores it on the response. That has one practical consequence: create a separate collector for each channel or campaign you want to tell apart. Two channels sharing one link produce responses you cannot separate afterwards.

Note: Deleting a collector does not change responses already collected through it. Those responses keep the deleted collector’s code.

Each collector row carries two counters. They are independent of each other, and neither is a survey-level figure.

Column	What it counts	What it does not count
Opened	One for each load of the survey page through that collector’s link.	Previews and print views. The count is sent in the background, so an open that never reaches the server is dropped silently and the respondent sees no error.
Responses	One for each submitted response carrying that collector’s code.	Opens that did not end in a submission. It is a stored counter kept up to date as responses arrive, not a live query over your response data.

Passing your own data in the link

Custom variables let a link carry extra data — a contact id, a source, a campaign name — that is saved with the response. They are defined per survey, not per collector, and not on the Share tab.

1In the Design step, open Settings and choose Variables, whose subtitle reads URL parameters.
2In the Custom Variables dialog, under Add Variable, type a Variable Name and an optional Description, then add the row. Names are lowercased, and anything that is not a letter, number or underscore becomes an underscore.
3Click Save Variables.
4Go back to Share and open the collector. Web Link, QR Code and Email collectors now show the URL with literal placeholders, for example https://surveys.surveyanalytica.com/s/<collector code>?name=[name_value]. Replace each [name_value] with a real value before you send the link.

Only parameters whose names match a variable you declared are captured; any other query string you append is ignored. Captured values are stored with the response alongside its answers. Saving custom variables is plan-gated: on Standard, Save Variables opens an upgrade prompt instead of saving.

Warning: To display a variable’s value inside a question, write it in single braces, as in {name}. The tip inside the Custom Variables dialog says to use {{variable_name}}; the renderer resolves the inner braces only, so that form prints the value wrapped in a stray pair of braces.

Note: If you declare a variable named name and distribute through a contact list, the contact’s name from the list replaces whatever the link passes.

Where per-collector numbers can be analysed

The Opened and Responses columns on the Share tab are the only place per-collector counts appear. Analytics has no collector dimension: you cannot filter, group or break a report down by collector, and no report column shows one. The collector code does travel with exported data in the OData feed, where each response row carries it in a field named link, so grouping responses by collector is work you do in your own tool. See Run Analytics.

Share API. A read-only endpoint over your survey or data records, created from Analytics rather than from the Share tab: open the download menu on Responses (or Data) and choose Share API. Give it a Share name, a Scope, an Authentication mode and an Expires date, then click Create share endpoint; the overlay hands back an Endpoint URL and, for key-based access, an API token. It reads records only — 50 per page by default and at most 500, with sorting and per-field filters. Nothing can be written back through it.

Flow webhook trigger. A flow can be started by an inbound webhook. The flow designer shows a copyable curl snippet containing that flow’s own webhook URL and a code header, and any system you control can post to it. This is the one surface an outside system can call to push data into the platform. See Flows and Automation.

OData feed. From the same download menu, OData Endpoint gives a BI tool an OData v4 feed of your surveys and responses, behind your SurveyAnalytica sign-in. Its flattened response rows are the export that includes the collector code.

Commonly asked for, and not available

No public API for creating collectors or sending a survey. The interfaces above are read-only or inbound-only. Collectors are created inside the product by a signed-in user with the right role on the workspace, never by an outside system.
No Zapier app. Zapier is reachable only as an outbound action inside a flow: you paste a Zapier catch-hook URL and the flow posts to it when it runs. There is no SurveyAnalytica app for Zapier to trigger or read from.
No respondent panel. You cannot buy responses through SurveyAnalytica. There is no panel or audience marketplace in the product — you bring your own respondents through the collectors you create.

14. Quick reference

The eight collectors at a glance, in the order the Create Collector menu lists them.

Collector	What you get	Configured in	Worth knowing
WhatsApp	A sent WhatsApp campaign, delivered from a connected WhatsApp Business sender.	The full-screen WhatsApp Campaign dialog: a six-step wizard through Setup, Method, Template, Audience, Mapping and Review.	Save Draft is not a draft; like Send Campaign, it submits the campaign for sending.
Email	A sent email campaign, tracked against the collector.	The full-screen Email Campaign dialog: choose a template, then one configure-and-send form.	Merge tokens reach the body only, so `{name}` in the subject line arrives as literal text.
Web Link	One public URL, in the form `https://surveys.surveyanalytica.com/s/<collector id>`.	The Web Link popup, which opens as soon as you pick the channel.	The URL is shown only inside that popup, never in the collector table.
QR Code	A PNG named `QR_Code.png`, roughly 266 × 266 pixels.	The QR panel, with a live preview of the code.	Save and Download keep different settings, so click both before you close it.
Download Survey	A PDF of the questionnaire, one PDF page per survey page.	Nothing opens. The collector is created and the file downloads straight away.	Each click creates another collector, and answers written on the printed sheet never come back.
Website	A single script tag to paste into your site, or WebView source code for a mobile app.	The Embed Survey dialog: Embed Mode, Target Platform, Design, Trigger & Rules, Get Code.	The collector is written only when you click Generate Code; close the wizard first and nothing is kept.
Social Media	A published post, or the platform’s own share window opened with your survey link in it.	The Share on Social Media dialog, on either the Quick Share or the Advanced Post tab.	Only Advanced Post on Facebook, Twitter / X or LinkedIn reports engagement back.
Shopify	A survey on your storefront: a script on every page, or an app block you place yourself.	The four-step Shopify window: Connect Store, Integration Type, Configure, Deploy.	There is no undeploy control, so switching the collector to Inactive or deleting it leaves the script running.

Several things people expect on the Share tab are set elsewhere in the survey. This is where each one lives.

If you are looking for…	Go to…
A response limit or quota	Publish > Response Goals, section Response Limit: Set maximum responses, Maximum Responses and Auto-close survey when limit is reached. Read-only on the Standard plan.
Access restrictions — who may answer	Publish > Restriction, which offers Email Domain, Email, Location, Registered and Mobile Phone.
Start and end dates	Publish > Schedule, under Schedule Settings. This is the only close-date control.
Allow multiple responses	Design > Settings, in the toolbar Settings dropdown.
Allow response editing, and the edit window	Design > Settings > Open Full Settings. The Survey Settings dialog is the only place these appear.
The survey end page	Design > Right toolbar > End Page. Publish > Survey End Page is read-only and points you there.
Custom variables — URL parameters	Design > Settings > Variables, then Save Variables in the Custom Variables dialog.
A sending domain or a verified From address	The Email collector’s From Email field: + Add email account to pick a verified domain, or Manage sending domains to set one up.
SMS	There is no SMS collector. SMS is a flow action, and your own connected number lives under Domains.

15. Troubleshooting

The behaviours people most often report on the Share tab, and what to look at first.

Symptom	What to check
“The Create Collector button is greyed out and I cannot click it.”	The survey is not published. The tab shows Survey is not active, please publish before sharing this survey. Publish it from the Publish step, one to the left, then come back — existing collectors load either way, only the create buttons are switched off.
“A collector appeared in my list before I had configured anything, and I have two rows for one PDF.”	WhatsApp, Email, Web Link, QR Code and Download Survey write the row the moment you pick them, with no confirmation. Close the panel and the row stays behind, switched on, so delete it from the row’s ⋮ menu. Each click of Download Survey creates another collector.
“Every row is called Link, QR Code or Website instead of the name I wanted.”	A collector with no name of its own falls back to its channel label. Name a Web Link or QR Code collector in the Name field of its own panel; the Website and Shopify wizards have no name field at all, so note each Collector ID against the page you used it on. You cannot rename from the list.
“I cannot see the survey URL anywhere in the collector table.”	The table never shows the link, and there is no copy action on a row. Open the collector — click the row, or Edit in its ⋮ menu — and copy the URL inside the Web Link popup.
“I set the QR colours and a background image, clicked Save, and they were gone.”	Save keeps only the name and Disable Response Override; the colours, background image, language and custom-variable value are kept by Download instead. Click both before closing the panel, and note that Download discards a name you have only just typed.
“The printed QR code does not look like what I saw on screen.”	The background image belongs to the preview, not to the code. Open the downloaded `QR_Code.png` and check it there, scan the file with a phone, then scan a printed proof before committing to a print run.
“Respondents received a link with [name_value] still in it.”	Those are literal placeholders, shown because the survey defines custom variables. Nothing fills them in for you and the popup has no field for values — replace each one with a real value yourself before you send the link.
“I added parameters to the link but they are not stored with the responses.”	Only parameters whose name matches a Custom Variable declared on the survey are captured; everything else in the query string is ignored. Declare them at Design > Settings > Variables, remembering that names are lowercased and any character that is not a letter, number or underscore becomes an underscore. On the Standard plan Save Variables opens an upgrade prompt instead of saving.
“I cannot tell which channel a response came from.”	Attribution is the collector code in the link the respondent opened, so two channels sharing one link produce responses you cannot separate afterwards. Create a separate collector per channel or campaign. Analytics has no collector dimension; the code travels with exported data in the OData feed, in a field named `link`.
“I pasted the embed code and nothing shows on my site.”	Paste the script tag into the head of every page the survey should appear on, or into your platform’s site-wide header — the blue alert on Get Code names the exact place. The `[surveyanalytica]` shortcode in the WordPress snippet has no handler in the product, so use the script tag. If you walked past Trigger & Rules without clicking a card, no trigger was recorded and the survey opens only when a visitor clicks the launch button. In Standard mode the survey is appended to the end of the page body, and reopening a saved website collector resets the platform to Generic HTML, so re-pick yours before copying the code again.
“The {name} token worked in the email body but arrived as text in the subject line.”	Tokens are merged into the body only. The Email Subject is sent exactly as typed, so personalise the body and keep the subject generic.
“Send Campaign is disabled on the WhatsApp Review step.”	The template is not approved. The warning above the buttons names the current status and the tooltip reads Template must be approved by WhatsApp before sending. Wait for Meta’s approval or pick an approved template. For Native Flow, the checklist also needs the flow synced from the Template step.
“My social post published but reports no engagement.”	Metrics come from the platform and only Advanced Post produces them, on Facebook, Twitter / X and LinkedIn. Instagram, Slack and Microsoft Teams publish, but the response carries no post identifier the product can track, so no metrics panel and no badges appear. Quick Share posts nothing on your behalf at all.
“Shoppers see a recommend question on my Shopify store, not my survey.”	That is Auto-Deploy. It puts a bubble on every storefront page that expands into a built-in How likely are you to recommend us? question, and your own questions appear only when the shopper clicks More questions →. For your survey itself, use the Manual Setup tab and place the app block with the survey URL.

The settings and features this article points at, in their own guides.

Survey Settings — where the response behaviour toggles and the custom variables that Share links carry are defined.
Contact Lists — the recipients an Email or WhatsApp collector sends to, and the fields its merge tokens read.
Sending Domains — verifying a domain so you can send from your own address rather than the platform default.
Run Analytics — reading the responses your collectors bring in, and the OData feed that carries the collector code.
Custom Domains — adding the hosts that appear as extra URLs in the Web Link popup.
Survey End Pages and Thank You Screens — what a respondent sees after submitting, designed on the Design step.
Flows and Automation — sending off events such as a Shopify order, plus the inbound webhook trigger and the SMS action.
Conversations — Omnichannel Messaging — handling the replies a WhatsApp campaign brings back.
Cross-Channel Campaign — Design Capabilities — the drag-and-drop designer behind the Email collector’s templates.
Connect Your Own SMS Number (Telnyx or Twilio) — the SMS route, which is a flow action rather than a collector.

Help

1. What the Share tab is

What a collector is

Where the tab sits

Publish the survey first

What is on the tab

Which collector to use

What is not on this tab

2. The collector list

Filter tabs

What each column means

Opening a row and its ⋮ menu

Empty state and pagination

What the list does not do

3. Creating a collector

4. Web Link

Name and Disable Response Override

Passing data in the link

What a Web Link does not do

5. QR Code

The controls on the QR panel

What Download gives you

Printing the code

What the QR collector does not do

After the code is printed

6. Download Survey

What is in the PDF

There are no options

The collector row

Answers written on paper do not come back

7. Website

The eight embed modes

Building the embed

Target platform

Design

Trigger and conditions

Getting and pasting the code

What the Website collector does not do

8. Email

The campaign form

Personalising the message

Reminders

Save for later, or Create Campaign

Tracking what happened

What the Email collector does not do

9. WhatsApp

What the wizard requires

Native Flow or Survey Link

Build the campaign

Review and send

Flow status, Re-sync and Delete

What this collector does not do

10. Social Media

Quick Share

Advanced Post

Engagement metrics

What this collector does not do

11. Shopify

Connecting a store

The two integration types

What the Configure step controls

Auto-Deploy compared with Manual Setup

What this collector does not do

12. Response settings, restrictions and goals

Response editing and retakes

Settings that do not exist

13. Tracking and attribution

Passing your own data in the link

Where per-collector numbers can be analysed

Commonly asked for, and not available

14. Quick reference

15. Troubleshooting

16. Related articles