What is an attribute ?

Attributes allow you to automatically associate information and contextual data with each of your responses when distributing a questionnaire.

 

They will also be useful for exploiting your responses more precisely using your daily tools (CRM, DMP, email database).

Specifically, an attribute can be: your client's first name, client ID, client's age, the type of subscription your client has, etc. 

 

Why use attributes? 

 

  • Add context to the obtained responses 

If you want to automatically associate your contextual data with the obtained responses, attributes are very useful. This can be particularly for statistical purposes or to enrich your CRM. 

  • Customize your questionnaire 

Attributes can also allow you to customize your questionnaire. You can trigger it or display certain questions based on specific targeting. 

  • Implement targeted actions

Attributes enable you to implement targeted actions based on the obtained responses.  

  • Conduct more detailed analyses 

With attributes, you can conduct more detailed analyses. For example, if you have multiple stores, an attribute allows you to access satisfaction scores by store rather than just the overall satisfaction score.

 

All the attributes needed for a campaign should be grouped into a segment. Attributes and Segments are closely linked, to simplify:

  • The Attribute qualifies your respondent population (like an adjective).
  • The Segment defines a population of respondents (a precise description).

Want to learn more about segments? Check out: segments and segment groups

Attributes and Segments are therefore the best way to attach contextual data to feedback. Thanks to them, you can:

  • trigger targeted actions upon questionnaire validation 
  • create customer experience management indicators
  • trigger the questionnaire at the best moment in the customer journey.

A concrete example 

 

Let's take the (fictional) example of Claire. She is part of a segment with the following relevant attributes: client_ID, first_name, order_channel, first_order, client_email.

 

 

  • client_ID, here "1234567A" is the client number that will help us identify that the respondent is indeed the correct user of your services (e.g., reconciling data with your CRM).
  • "first_name" and "client_email" as their names suggest are respectively "First Name" and "Email", here "Claire" and "claire@company.com".
  • "first_order" to identify the date of the first order (e.g., for offering discovery or loyalty offers, or for statistical analysis), here the date is "06/09/2022".
  • "order_channel" is the channel through which your respondent accesses your questionnaire, for example, on your website (if you notice that most respondents browse via mobile, it would be essential to focus your technical choices on this platform), here "Mobile site".

Reconciling the collected data in your CRM will depend on the naming of these attributes in your own tools. The concepts of Internal Entity and Remote Field will help you create a mapping between your tools and Skeepers. Want to learn more? Check out the article on how to create a mapping.

 

Using Collected Data 

 

Collected data can be used as an attribute in a future questionnaire sent to your contacts.

For example: You have your contact's email and first order date, but you want to ensure the first name in your database is correct. In your Skeepers questionnaire, you can ask your client to enter their first name, then indicate in your settings that the response field for this question will correspond to the "First Name" attribute. It's that simple.

 

Go further

To add parameters (variables) in a distribution URL, check out the article: attaching attributes to a distribution URL.

When distributing your questionnaire via "Website", remember to match it with the data available in your data layer.

Distributing your questionnaire via email or SMS? You need to match your contact database fields with those in Skeepers. Check out the articles: how to create an attribute and create a mapping.

 

Want to try? Click here

Was this article helpful?
0 out of 0 found this helpful