Skip to main content

Customer Data Platforms

This article provides a platform-agnostic overview of how Faslet integrates with customer data platforms (CDPs) to send shopper profile data. If you want to connect Faslet and your CDP, start here.

Supported platforms​

For setup instructions, see Getting started with Klaviyo, Getting started with Voyado, or Getting started with Spotler.

Missing a platform?

If you're interested in additional platforms, contact us to have it supported.

Why connect?​

Connecting Faslet to your customer data platform lets you get up-to-date sizing-related data about your shoppers whenever they use one of Faslet’s features. These enriched profiles can be used for more granular analytics, to further personalize your marketing and more.

Available data​

The table below outlines shopper data we provide. Visit the data reference article of your particular platform for details.

NameDescriptionKlaviyoVoyadoSpotler
HeightThe shopper’s height in centimeters.

Examples: 175, 160, 182
✓✓✓
WeightThe shopper’s weight in kilograms.

Examples: 70, 55, 90
✓✓✓
Fit preferenceThe shopper’s preferred fit, ranging from tight to loose.

Values: tight, slightly-tight, average, slightly-loose, loose
✓✓✓
Latest size recommendationThe label for the size which Faslet recommended to the shopper.

Values: Your size options
✓✓✓
Serial returnerA flag that indicates whether the shopper is currently classified as a serial returner in Faslet.

Examples: true, false
✓✓✓

Spotler syncs the fields you map in the Faslet portal to custom profile fields in Spotler Activate. See the Spotler data reference for field names, types, and sync behavior.

How shoppers are matched​

PlatformShopper identification
KlaviyoUses the shopper identifier supplied through cdp-contact-id, with a Klaviyo cookie fallback when available.
VoyadoRequires the existing Voyado contact ID through cdp-contact-id.
Spotler ActivateUses the sqzllocal browser cookie. The cdp-contact-id attribute is not supported for Spotler.

For Spotler, profile updates arrive asynchronously after Spotler resolves the cookie to a profile. If the cookie is unavailable, Faslet cannot sync data for that session.