What are attributes?

Attributes in Feedier represent data that gives extra details about the recipient and are directly attached to feedback. They bring context to your answers. They are also known as metadata. Here are a few examples:

Product ID
Gender
Region
Manager name
Building
Division
Location

Attribute name, label and values

Attributes do have a name and a label:

the name is the key that will never change usually in snake_case. It has to be used in survey links, filters, push recipient files, widget setup…
the label is the way you want to display it in the UI, that can change with time. It is never used as a key.

Both can be the same or different, but your conditions, filters, etc will rely on the attribute name to avoid breaking anything to just update the displayed label. Feel free to change the label anytime without risk.

A given feedback can have one or multiple values of one attribute.

When checking the details of an attribute, you can see the different values that exist and the number of feedback with this value attached

Why are attributes important?

By attaching to your feedback, attributes can be searched and viewed at a later date in order to build cohorts to measure patterns and trends. What you choose very much depends on your use case and what your KPIs are.

Attributes help:

Give Context: Get all the context for a given individual Feedback, so when bad Feedback is received, you can get a much better understanding of correlated data. You can also use it to search for individual feedback. ie. Employee ID.

Compare Segments: You can have certain Segments track incoming context attributes in order to be alerted in real time. You could also use it as a measuring tool to group your data based on specific Attributes eg. Department, Client Name etc.

Provide Reports: Using the benchmark report, you can compare dataset A vs dataset B and see which one is performing better.

How to embed attributes into your survey

In the links, with enriched form links.
In the emails/sms with enriched pushes.
Picking up website meta data and attaching to the web widget as a data-custom-fields string.
Collecting Attributes by asking in a survey.

1. Adding attributes to a URL

If you want to add attributes directly to a link, you can do so by adding ?[attribute name]=[attribute value] to the end of the URL. You can stack multiple attributes by adding an ampersand.
For example: clicking http://feedier.com/1234?department=project_delivery&client=Pepsi and answering will create a feedback with attributes

department = project_delivery
client = Pepsi

Attribute names that do not already exist will lead to the creation of a new attribute with this name automatically.

Make sure to use the attribute name and not the label

2. Adding attributes to an email or SMS campaign

When uploading a .CSV, the file must have at least a column email or phone depending on the campaign.

Any other column will be attached to the Feedback as Attributes and can even be used in the campaign message body.

Make sure to use the attribute name and not the label as column headers.

3. Adding attributes to a web widget

You can dynamically build the link if integrated into your systems with variables that you already know.

Example: Widget code with context attributes 'user ID', 'Role', 'Signed up' added:

<script id="feedier-widget-script" src="https://feedier.com/js/widgets/v2/widgets.js?form-id=13&public-key=abcde1234&no_header=true&user_id=1234&role=Premium&browser=chrome" async></script>

Attribute names that do not already exist will lead to the creation of a new attribute with this name automatically.

Make sure to use the attribute name and not the label

4. Collecting Attributes by asking in a survey

Sources → Survey → New Question

In the form builder, add a new question and choose the “Context Attributes” type

Here you can ask the information that you need from the respondent. You can choose from a text field, dropdown, date, and number field.

The input field will only be shown if no value for the attribute is already provided in the url or in the push (1,2,3). No value is considered the the same as empty value.

Attributes questions work better than using a text answer question as you're able to filter the data by attribute values and get deeper insights.

If there's no integration with Feedier, and you want to ask an attribute question, you must add attributes in advance via the attribute page.

If the attributes exist already, then there's nothing you need to do.

Attribute Management

Settings → Attributes

Visibility of attributs

There is 3 visibility types

Public (by default) : attributes are visible by all logged in users, and can be used as filters or in reports.
Hidden : The value will not be shown whatever the page (live feed, reports,…).
Visible for assigned users : The value will only be shown
- From the live feed
- If the user is assigned to the feedback
- If the delay is not expired (if exists)

The visibility applies to the current team and all its sub teams, except if it was explicitely changed for one of the subteams.

Sensitive attributes

Sensitive attributes are encrypted in our database with the AES-256-CBC algorithm. You cannot filter on their value, but you can retrieve it

through the API
in an email template (in order to insert the attribute value in an email campaign)
when the visibility setting is Visible to assigned users (see above).

In those situations, the value is decrypted only at the moment it’s needed—it is never stored in decrypted form in the database.

Favourite Attribute

The “Favourite” attribute type makes your attribute usage across the platform more efficient.

Current behaviour of favourite attributes

They are first in the positioning in filters and drop downs, and in feedback cards
When creating graphs the favourite attribute is the one selected by default
1. Creation of benchmarks in Dashboards
2. Score Tables and Correlation Matrix in reports
Default selection on Attributes tab in Topics individual view (text analysis)
The anomaly detection agent identifies anomalies for values of favourite attributes only

🔹 Attribute Value Ownership

The “Ownership” attribute type allows you to assign email owners to attribute values.

✅ New Ownership Attribute Type

You can now define ownership at the attribute level.
Each attribute value can have multiple email owners assigned.
Owners will automatically receive reports for the values they are assigned to in Autopilot.