How to use the Account Data?

Sending attribute values in the account data - via API or FTP - allows attributes to be collected via a unique identifier.

Why use account data?

The account data functionality allows you to collect attribute values via a file repository or an endpoint API.

Traditional attribute collection solutions via the URL (URL, Email or SMS via a third party tool deployements) or the JavaScript tag of your website (Website or Inpage deployments) are not completely suitable for your project because :

  • Some attributes are not available in the tool that manages the solicitation (the email tool or the website for example in the case of a product catalogue);
  • You wish to limit the size of the URL;
  • You do not want to pass attributes in the URL even if the Skeepers solution offers URL encryption solutions.

Warning: Do not confuse Account Data which allows you to create attributes at the time of the response and Linked Attributes which allows you to manage a system of dynamic linked attributes on a defined value list.

How does Account Data work?

 It is currently possible to import data via 2 sources:

  • via CSV file transfer on FTP, SFTP, FTPS repository see article How to set up an FTP repository?
  • via the Skeepers API see the API documentation

In both cases the logic is the same:

  • Skeepers creates a new instance of "Account data" and its associated columns (receptacle to your data) on your Skeepers account. One column is designated as the unique ID.
  • This instance is fed with data by file import or API at the frequency you wish.
  • Then a mapping is built at the segment or object type attribute level, to each column and the corresponding attribute, from the back office.

Warning: The data must be present in the account data before respondents access the questionnaire. 

The account data does not allow the creation of an attribute or the recovery of one after the response but the collection of attributes at the time of the response.

The deployements url will have this unique identifier as a parameter: https://urlduquestionnaire.com?d:id_unique=valeur_unique...

When a respondent accesses the questionnaire, the mapping is applied and the attributes are fed with the imported data associated with the unique ID.

The functional exploitation of the attributes is then similar to what you already do on the solution.

Tip: You can collect only part of the attributes via the account data. If the attribute is in the URL and in the account data, the value in the URL will be retained.

 

How do set up the account data?

1. Initial configuration by the Skeepers technical team

The Skeepers technical team does the initial configuration of the account data to create a new instance. Please ask your CSM for the configuration worksheet. 


2. Configuration of the mapping

An account data instance can either enrich attributes via a mapping on the segment level or properties on an object attribute.

Mapping on a segment

  1. Select the instance to be used and the attribute to be used as identifier.
  2. Perform the mapping between the account data columns and the segment attribute
  3. Save

mceclip0.png
Mapping on an attribute of type Object

  1. On the attribute of type Object select Account data the relevant instance
  2. On the properties, select the property which will be the identifier, i.e. the one which will transit in the classic way via URL or Tag and will allow to deduce the other information to be attached to the response

mceclip1.png

3. On each property (other than the identifier) specify which field corresponds to this property.

mceclip2.png

4. Save

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