Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledisc
typelist
printablefalse
Info

In regards to the Feedier widget,

  • The widget supports any question types, conditions, and design as does the regular surveys when they are not loaded through a widget.

  • The widget’s script is 100% cached and served through a CDN (Cloudflare). Also, the requests to Feedier’s backend to load the survey data are cached.

  • The widget options in Feedier are designed to remove as much developer resource as possible from the process.

  • When possible, we recommend using a Tag Manager system to load the Feedier widget.

Where to find the widget’s JS code?

...

Select the button and click to copy to select the widget code.

...

Info

Click the button 'Save and Preview' to view your changes and Preview the widget.

...

  • browser

  • user_id

  • geolocation

  • locale

  • user_role

  • version

  • screen_size

  • page_url

  • etc.

Note

Feedier never automatically imports any user data, or data from the page where it is loaded automatically.

Method 1: adding attribute through the widget code URL

...

Make sure that jQuery is loaded on the page. It's a common error. If your widget isn't loading, and you have no idea why, you can easily determine if jQuery is the culprit. Open the console (right-click on the page > "Inspect the page"). You will see the error that jQuery isn't loaded. 

Use-Case 4: Showing the widget only once based on a specific attribute value

It’s possible in the Feedier Platform to restrict the widget visibility based on advanced ruled. One of the most common use case is to restrict the widget based on an attribute value.

So for example,

  • If the widget is loaded with user_id=123, and user_id=123 replies, the widget for this specific survey will never show up again.

To do this, go to Advanced settings and select the attribute in “Restrict access by attribute value“.

Note

This rule is only based on the matching survey x attribute value.

...

Info

If you want to add a specific timeline, we recommend concatenating attribute values with a time element.
For exemple, to display it every month :

  • Add an attribute in the widget URL like widgetuid={{userId}}-{{month}}{{year}}

  • This will create something like widgetuid=123-0225

  • If you select widgetuid in the Advanced Settings option, user id 123 will only be able to reply once a month.