Version 1.10.3 - 11th October 2021

Another big update on the Feedier Dashboard this week. We just added our new ‘Attributes’ page on our dashboard. This is a big change is how we present and manage attribute data.

So first, let’s do a recap on what are attributes ?

Technically speaking Attributes are a Name & value that are attached to each feedback. Essentially this is a meta data that is collected at the same time as the feedback. A attribute could be any operational data about the responder that is coming from your CRM or collected directly from the responder. Once this is attached to your feedback it can be used later for analysis such as benchmarking or creating reports within Feedier.

When done correctly, this is powerful stuff !! And that’s why here at Feedier we place such a big emphasis on this.

In Feedier there are multi ways of adding Attributes:

Automatically via a CRM/ERP or inhouse database
Via a link
Via a Email/SMS campaign
Via a QR Code
Via a Widget/iframe

Once collected these attributes are shown in many parts of the platforms and can be used for analysis and reporting.

So what’s the new update ?

The new update is a dedicated page in the dashboard to managing your attributes. This means for large organisations who manage a large amount of attributes for each feedback can easily organise their attribute data for their ORG.

The main table view above shows a few key things:

Primary attribute; This is the attribute on the far left side with a little key icon next to it. This is your main attribute that helps you organise your attribute data. Primary attribute that you select must be a unique value. This means that if you primary attribute is Employee ID, then each value attached under this attribute must be unique to only one person i. Employee ID = 1234 is only used for John Doe. This is important to keep in mind as this will affect the editing and updating rules (But more on this later).

Secondary attributes are also shown in this table attached for the same contact. This can be any other operational data such as name, Age, location, city etc etc. Again you get to define this from your CRM or custom.

Satisfaction Ratio for each attribute is also shown on this table.

Feedback Count per attribute. All feedback collected for this attribute. Please note as the data on this table is aggregated there might be multiple feedback with the same Primary attribute who do not have the same

Push count per attribute: All the pushes that have been sent for this attribute.

Editing & Updating attribute values:

When updating any secondary attribute value from the new attribute page, you always have 2 options:

Updating attributes on the Attribute main page

Updating attribute value for that attribute for ALL FEEDBACK to this new value or
Updating attribute value for that attribute for ALL FEEDBACK only for the primary attribute in that row.

So in this example above I can update all Location=Toyko to New York or I can update all Location=Toyko to New york only for Name=john.

If you are not sure you can always click the Hyperlink on the text ‘All Feedback’ to see which feedback data your changes will effect.

When updating any attribute value from individual feedbacks view, you always have 2 options:

Updating attribute value for that attribute for this specific feedback to this new value or
Updating attribute value for that attribute for ALL Feedback that have the same primary attribute.

So in this example you have the option to update Jack to Tony for Feedback ID #69077 or you can update all feedback from Jack to Tony where primary attribute equals to Jack.

Again for ALL Feedback option you have a FQL you can click to see which feedback will be affected.

Start using attributes today by selecting a primary attribute by switching to Setting tabs:

Please note the Primary attribute you select MUST BE UNIQUE. This means that the value you collect for each the primary attribute name is only used for 1 contact, such as client id, employee id, reference number etc. This is really important as to not merge attribute data across your feedback data incorrectly when updating.

In the next release we will talk about a few more points related to attribute functionalities:

Merging & Deleting Attributes names ( coming soon)
Marking attributes as Sensitive Data

We know this is a lot of information to digest, our CS team is here to help and make sure you use the best attribute as your primary and help you organise this for you. So please contact your dedicated account manager if needed.

Thanks

- Team Feedier