Feedier Manual

Feedier Manual

Context attributes

Introduction

Context Attributes in Feedier represent data which are not answers but attributes about the participant and Feedback. They bring context to your answers. They are also known as metadata. Here are a couple of examples:

  • Product ID
  • Gender
  • Region
  • Manager name
  • Building
  • Division
  • Location

It very much depends on your use case and they are entirely flexible. Reasons to attach Context Attributes are:

  • Segmentation: Segment your data based on Context Attributes to retrieve all information for a given location or a manager.
  • Context: Get all the context for a given individual Feedback, so when a bad Feedback is received, you can understand exactly what are the correlations.
  • Benchmark: Using the benchmark mode, you can compare dataset A vs dataset B and see which one is performing better.

Manage Context Attributes

There are two kind of Context Attributes, visible ones: you do not know the information, and invisible ones: you do know the information already.

Visible Context Attributes

The visible Context Attributes can be edited and managed for every form individually:

  • Settings
  • Click “Context Attributes”

Then, you can create new Context Attributes fields and make them “visible” (Figure 2), they will be displayed at the end of the form (Figure 3)

Figure 3

Invisible Context Attributes

When you already know the information, do not ask for it and create useless frustrations, provide it automatically:

  1. In the links, with enriched links.
  2. In the emails/sms with enriched pushes.
  3. With automated workflows.
  4. By attaching to the web widget as a data-custom-fields string.
Pro tip!

Context Attributes passed in the emails/sms or links are automatically created and attached to the Feedback. Nothing to do on your end except provide the data in the first place.

Use Context Attributes to get Insights

Once attached to the Feedback, Context Attributes can be used in different places:

Figure 4