Skip to main content

Share a survey: email, SMS, link and widget

Send an email or SMS campaign, share a link or QR code, embed the widget on your website, track sends and manage unsubscribes.

F
Written by François Forest

Surveys → your survey → Share

In short: the Share tab brings together every distribution channel. Email and SMS campaigns sent by Feedier are tracked in Pushes. In every case, pass attributes to enrich each response.

Which channel should you choose?

Channel

Best for

Send tracking

Email campaign

Surveying a list of known customers, with reminders.

B2B and B2C.

✅ in Pushes

SMS campaign

Reaching people quickly, for example after a service visit.

B2C.

✅ in Pushes

Survey link

Sending from your own email tool, or posting a link.

B2B and B2C.

🚫 in your tool

Dynamic web widget

Collecting feedback on your website or in your app, at the right moment in the journey.

B2B and B2C.

—

Webview

Embedding the survey in a mobile app.

—

QR code

Stores, posters, receipts.

B2B and B2C.

—

Before any send, test the survey with the Test link.

Send an email or SMS campaign

SMS campaigns are only available on request (email for requests: [email protected]). Once enabled, Feedier bills SMS at cost.

  1. In Share, choose Email campaign or SMS campaign, then create a new campaign.

  2. Import your recipients (CSV file) or trigger the campaign through the API.

  3. Write the message. Personalize it with attributes, for example Hello {name},.

  4. Add reminders and choose their delay, with the "only to those who haven't responded" condition.

  5. If needed, choose the days to skip (for example weekends), then schedule the send.

A reminder's delay starts from the previous send, not from the first one. Example: sent on January 1, reminder at 3 days (January 4), then reminder at 5 days (January 9).

Prepare the recipient file

Column

Required?

Content

email

⚠️ Yes, for email

The recipient's address.

phone

⚠️ Yes, for SMS

In E.164 international format: +33612345678 (15 digits max).

locale

No

The survey language (fr, en…). See Multilingual surveys.

Any other column

No

Becomes a feedback attribute, which you can also use in the message.

Trigger a campaign through the API

Set up the campaign in advance, then call the Feedier API with the campaign ID: each call sends the survey to one contact, with their attributes. This is the recommended method for sending after every purchase or every ticket. See API, MCP and widget and the Salesforce connector.

Customize the sender and the email (Options → Push)

Setting

Effect

Email header image

A banner at the top of the emails.

Custom sender name

The name displayed as the sender.

Custom sender email

Your sending address. Requires domain verification: see Custom domains.

Custom reply-to email

The address that receives replies to the email.

Hide the call-to-action button

Removes the main button from the email.

Post-unsubscribe redirect URL

The page displayed after someone unsubscribes.

Custom email header / footer

Your own HTML at the top and bottom of the email (legal notices, social networks…).

Number of days push links stay active

The email link expires after this number of days.

Sender name (SMS)

The name displayed as the SMS sender (depending on country and carrier).

For a better response rate: a short subject line, a brief message with the estimated response time, the first question embedded in the email, and two reminders (at 48 hours and 7 days). In B2B, send during business hours; in B2C, after 6 p.m.

Track sends

In Feedier Surveys, the Pushes menu lists every send with its status. You can edit or block an individual send there. To start over, cancel the campaign: all pending sends are deleted.

Status

Meaning

Requested

The email has been sent, with no delivery information yet.

Delivered

The email reached the inbox.

Opened

This status is no longer tracked: Feedier emails don't contain a tracking pixel.

Clicked

A link in the email was loaded. Note: corporate security gateways (Microsoft Safe Links, Mimecast, Proofpoint…) test links automatically, which creates non-human clicks.

Bounced

The email couldn't be delivered (address doesn't exist or was rejected).

Dropped

Feedier didn't attempt the send. See the causes below.

Unsubscribed

The recipient clicked the unsubscribe link in this email.

Why is a send "Dropped"?

Cause

What to do

The recipient unsubscribed from a Feedier email sent by your organization.

Remove the contact from the unsubscribe list (see below), if they ask.

The address is on our email provider's suppression list (previous bounce, spam report, invalid address).

Check the address.

The contact already received an email for this survey in the last 12 hours (over-solicitation protection).

Nothing: only the first email is sent. This rule doesn't apply to users in your organization.

The contact has been anonymized.

Nothing.

Manage unsubscribes

  • Every email contains an unsubscribe link, added automatically.

  • Unsubscribing applies to your whole organization, not to a single survey: the contact no longer receives any Feedier email from you.

  • Feedier doesn't read the opt-out flags in your CRM: filter contacts before sending them to us.

  • You can view and manage the unsubscribe list through the API or directly from the pushes page in the platform.

To change the unsubscribe text, go to the survey's general content and keep the [unsubscribe] tag, which is automatically replaced by the link:

<a href="[unsubscribe]">Unsubscribe here</a>

Send from your own tool (survey link)

You can insert the Survey link into an email sent by Brevo, Mailchimp, HubSpot, Salesforce Marketing Cloud, etc. Each parameter added to the link becomes an attribute:

https://feedback.yourbrand.com?email={{contact.email}}&customer_id={{contact.id}}&locale=en

Rule

Details

Syntax

The first parameter starts with ?, the following ones with &. Replace {{…}} with your tool's merge tags.

Attribute names

Normalized to lowercase with underscores (Store Code becomes store_code). Reuse the exact name of an existing attribute.

Reserved names

phone, preview, step, completed, feedback_id, satisfaction, subject, no_header, organization don't become attributes. For a phone number, use mobile, for example.

Encoding

Spaces, accents, & and # must be encoded. Check with a test send.

With your own tool, send statuses, unsubscribe management and the 12-hour rule are handled by your tool, not by Feedier.

Embed the widget on your website

  1. In Share, open Dynamic web widget.

  2. Set the design and visibility, then save and preview.

  3. Copy the code and add it to your website, ideally through a tag manager (Google Tag Manager): no development is needed.

Design settings

Setting

Effect

Layout

Horizontal: flat button at the bottom of the screen. Vertical: rotated button on the edge of the screen.

Alignment

Left or right.

Button text

Default: "Give your Feedback".

Button style

Tag: a button that opens the survey. Ratings: the survey is embedded in an element of the page (Mount field), then expands after the first answer.

Colors, width, height

Button, background and progress bar colors, and window size.

Custom CSS

Your own styles, for example .feedier-widget__caller { background:red; }.

Visibility settings

Setting

Effect

Show on initialization

The widget opens on its own when the page loads, after the chosen delay (in seconds).

Exit Intent

The widget opens when the mouse leaves the window.

Manual target

The widget opens when someone clicks an element on your page (CSS selector, for example #btn-feedback).

Reappear on close

If closed without a response, the widget comes back on the next page load.

Expiration (days)

After a response or a close, the widget doesn't reappear for this period (30 days by default).

Included / excluded pages

The URLs where the widget can or can't appear. Exclusions take precedence.

Custom JavaScript

Code run after initialization, for example FeedierWidget.toggle();.

Pass attributes to the widget

Feedier never collects your users' data automatically. Pass it in the script URL:

<script id="feedier-widget-script" src="{endpoint}/js/widgets/v2/widgets.js?form-id={form}&public-key={public_key}&no_header=true&user_id=1234&user_role=Premium" async></script>

Or at initialization, with the JavaScript SDK:

FeedierWidget.init({  form_id: 123,  attributes: { user_id: '1234', page: window.location.href },  forced: true});

Method or event

Role

FeedierWidget.toggle() / show() / hide()

Open or close the widget. show(true) ignores the expiration.

forced: true

Show the widget even if the user has already responded.

question_answered

Event sent on each answer.

feedback_completed

Event sent at the end of the survey.

feedier_widget_closed

Event sent when the widget is closed.

To test without waiting for the expiration: add preview=true to the script, or clear the feedier.widgetV2 entry from the browser's local storage.

To show the widget only once per user, pass an ID as an attribute and select it in Options → Settings → Restrict access by attribute value. For once a month, concatenate the ID and the month (for example widgetuid=123-0226).

FAQ

My campaign is pending. Why?

Check the scheduled date and the days to skip. A send scheduled on a skipped day goes out the next day.

How do I remove a contact from the unsubscribe list?

Through the API (see Manage unsubscribes). Only do this at the contact's request.

A contact has a partial response and can't start over. Why?

The campaign link is tied to that feedback. If Allow multiple responses is turned off, the device can't respond again. Contact support if a response needs to be reset.

Why does the pushes export have one row per email rather than per person?

Each reminder is a separate send. The feedback ID only appears on the send through which the person responded: don't count the other rows as non-responses.

The widget doesn't show up. What should I check?

Check the included and excluded pages, the expiration (test with preview=true), and in the browser console that no error is blocking the load.


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?