Spotler data reference
This article describes the shopper data Faslet syncs to Spotler Activate and how to map it to custom profile fields.
If you have not connected Faslet to Spotler yet, start with Getting started with Spotler.
What syncs to Spotler
After a shopper completes the Faslet popup sizing flow, Faslet uses the sqzllocal browser cookie to request a profile match from Spotler. Spotler returns the matching profile information asynchronously, after which Faslet updates the mapped fields on the returned profiles and their entities.
These fields store the latest known shopper values. They do not create a separate event history. Matching requires the Spotler cookie; the cdp-contact-id attribute is not supported.
Synced Spotler profile fields
The API names below are the suggestions shown in the Faslet portal. The destination names are configurable, so use the exact API names of the fields in your Spotler account, including the custom_ prefix.
| Property | Faslet key | Suggested Spotler field API name | Spotler type | Description |
|---|---|---|---|---|
| Height | fasletProfileHeight | custom_faslet_profile_height | Number | Shopper height in centimeters, such as 175. |
| Weight | fasletProfileWeight | custom_faslet_profile_weight | Number | Shopper weight in kilograms, such as 70. |
| Fit preference | fasletProfileFitPreference | custom_faslet_profile_fit_preference | Text | Shopper fit preference, using one of the values below. |
| Latest size recommendation | fasletLastSizeRecommendation | custom_faslet_last_size_recommendation | Text | Most recent recommended size label, such as M. |
| Serial returner | fasletSerialReturner | custom_faslet_serial_returner | Text | The text true or false, indicating whether Faslet currently classifies the shopper as a serial returner. |
Create these as profile fields that store the latest value in Spotler before mapping them in Faslet. Follow the profile field setup instructions for the creation steps and links to Spotler's illustrated articles. Saving a mapping does not create its destination field. Each configured mapping must use a distinct field name; leave a mapping blank to skip that value.
Fit preference values
fasletProfileFitPreference is sent as one of these text values:
tightslightly-tightaverageslightly-looseloose