Skip to main content

Attributes and referentials

Add context to your feedback with attributes, set their visibility, protect sensitive data and automatically enrich your data with a referential.

F
Written by François Forest

Menu → Settings → Attributes and Settings → Referentials

In short: an attribute is a piece of context attached to a feedback: store, region, customer type, order number… It's what lets you filter, compare and break down your results.

A referential automatically derives other attributes from it.

Who can manage attributes?

Role

Access

Admin

Full access

Editor, Viewer, Restricted Viewer

Read-only

The Attributes and Referentials modules are enabled per role in Settings → Access management.

Best practices:

Attributes are essential to get actionable insights from Feedier.

  • We recommend keeping a maximum of 20 visible attributes. Otherwise, the interface becomes complex for users. Feedier lets you hide non-essential attributes (IDs, for example).

  • We recommend setting up favorite attributes. This makes analysis easier for end users.

Name, label and values

Element

Role

Can it change?

Name (for example store_code)

The key used in links, files, filters and the API

No, never

Label (for example "Store code")

What's displayed in the Feedier interface

Yes, at any time, with no risk

Values

The values received (a feedback can have several)

They come from your data

⚠️ Always use the name, never the label, in your links, files and integrations.

Add attributes to your feedback

Channel

How

Example

Survey link

URL parameters

…/f6o4Ye?store=Chicago&client_id=123

Email or SMS campaign

Columns of the recipient file

A store column

Widget

Script or SDK parameters

user_role=Premium

Import

File columns or connector fields

The country of a Google review

Survey

Attributes question (text, list, date or number)

"Which store did you visit?"

Tip: an Attributes question is only shown if the attribute hasn't already been provided by the link or the campaign. So you never ask for information you already know.

Configure an attribute

In Settings → Attributes, open an attribute to see its values, the number of feedback per value, and configure it.

Favorite attributes

You can mark attributes as "Favorites" ⭐️. This makes them show up first in reports and in the platform's various analyses.

Visibility

Visibility

Effect

Public (default)

Visible to everyone, usable in filters and reports.

Visible to assigned users

Visible only in the feedback feed, to the user assigned to the feedback, and for a set period if you define one. Ideal for an email or phone number to call back.

This is useful for Close the loop (also called customer callback).

Hidden

Never displayed, on any page.

An attribute's visibility on the platform is configured for each attribute in the Visibility tab:

Sensitive attributes

A sensitive attribute is encrypted (AES-256-CBC) and can no longer be filtered, displayed in reports or exported. It remains usable via the API, in an email template, and with the Visible to assigned users visibility. It's set in Settings → Advanced settings → Attribute security.

Irreversible: an attribute made sensitive can't be restored.

Attributes detected by AI

AI automatically spots certain information in verbatims. It becomes nlp_… attributes and is masked with *** in the text.

Attribute

What it contains

nlp_personal_name

People's names

nlp_localisation

Places

nlp_product

Products

nlp_brand

Brands

nlp_number

Numbers (phone numbers, amounts…)

Enrich your data with a referential

A referential links a key, already present on your feedback, to other attributes. You define it once; Feedier applies it to all your feedback, past and future.

store_code (key)

store_name

region

manager

CHI-01

Chicago Downtown

Midwest

Mary Smith

ATL-04

Atlanta Midtown

Southeast

John Miller

A feedback that arrives with store_code = CHI-01 automatically receives the store name, its region and its manager.

Behavior

Details

Retroactive

Any change immediately updates all existing feedback.

Scope

The whole workspace, not a single team.

No effective date

A change applies to the entire history, not from a given date.

Automations

Feedback already received doesn't go through automations again after a change.

One value per key

A key can't point to several values of the same attribute.

Typical use case: your Google reviews arrive with each location's store_code. A referential adds the region and the manager: you can then send each manager the report for their scope.

FAQ

Can I rename an attribute?

Change its label. Its name doesn't change: it's used as the key everywhere.

An import created a duplicate attribute. What should I do?

Names are normalized (Store Code, store-code and store_code all become store_code), but store and store_code are two separate attributes. Fix the name in your source, and contact support to merge the existing data.

Why doesn't an attribute appear in my filters?

It's hidden or sensitive, or it was created in a sub-team: in filters and reports, a sub-team's attributes aren't visible to its sister teams.

Can I date a referential change (a store that changes region)?

No, the referential applies to the entire history. To keep the history, add the region directly on each feedback, at the time it's sent.


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?