Getting started with Spotler

This article covers connecting Faslet to Spotler Activate so existing shopper profiles receive sizing data from the Faslet popup.

Requirements

You need a Faslet account, a Spotler Activate account with an account ID and API key, and access to create or manage profile fields in Spotler. Spotler tracking must be installed on your storefront so the shopper's sqzllocal cookie is available to Faslet.

Profile field setup

Before connecting Faslet, you must configure the custom profile fields that will receive Faslet data in Spotler Activate. Faslet does not create these fields for you. To sync all five properties, create all five fields in the table below. If you only want to sync some properties, create those fields and leave the other mappings blank in Faslet.

1. In Spotler Activate, open Data > Data Overview and find the Fields overview.
2. Choose Add custom field below the fields list.
3. Set the name and data type using the table below. Spotler supplies the custom prefix when creating a field; check that the resulting API name matches the full name shown in the table.
4. Configure the field as a profile custom field so it stores the latest value on the shopper profile.
5. Save the field and confirm that it has a green check mark in the Profile field column of the Fields overview.
6. Repeat for each property you want to sync. Ask your Spotler account administrator if you do not have permission to create fields.

Property	Suggested field API name	Data type
Height	custom_faslet_profile_height	Number
Weight	custom_faslet_profile_weight	Number
Fit preference	custom_faslet_profile_fit_preference	Text
Latest size recommendation	custom_faslet_last_size_recommendation	Text
Serial returner	custom_faslet_serial_returner	Text

Fit preference contains one of these text values: tight, slightly-tight, average, slightly-loose, or loose. Serial returner status contains the text true or false; configure its data type as Text.

You can reuse existing profile fields with the matching data types. Copy their exact API names into the Faslet mappings in the next section.

For illustrated instructions, see Spotler's Data article, including Add custom field. Its profile, product, and event fields article explains how profile fields store values and how to identify them in the overview. See the Spotler data reference for Faslet field descriptions and sync behavior.

Account connection and field mappings

1. Go to the Faslet App Marketplace.
2. Change All stores, at the right side of the top bar, to the store being integrated.
3. Find Spotler and open the integration.
4. Enter the Account ID and API key from your Spotler environment.
5. Under Profile field mappings, enter the exact Spotler field API name for each value you want to sync, including the custom_ prefix. Replace the suggested names if your fields use different names.
6. Clear any mapping you want to skip. Each configured mapping must use a different Spotler field name.
7. Save the configuration.

Saving mappings in Faslet does not create fields in Spotler. Create the destination fields before testing the integration.

Storefront setup

Faslet reads the shopper's sqzllocal cookie automatically when the Spotler integration is configured. Make sure Spotler tracking is running on the storefront and that this cookie is available when the shopper completes the Faslet popup.

Spotler does not support the cdp-contact-id attribute. A contact ID cannot replace a missing Spotler cookie. If the cookie is unavailable, Faslet cannot sync data for that session.

Verify the installation

1. Use a storefront session that Spotler can match to an existing profile, and confirm that the browser has the sqzllocal cookie.
2. Open the Faslet widget on a supported product page and complete the popup sizing flow.
3. Allow time for Spotler to resolve the profile and for Faslet to update it. The sync is asynchronous, so fields may not appear immediately.
4. Open or refresh the matched profile in Spotler and check the fields configured in your mappings.
5. Confirm that height, weight, fit preference, latest size recommendation, and serial returner status match the expected values for the fields you enabled.

If fields do not appear, check the account ID and API key, cookie availability, and the exact API names and types of the destination fields. Blank mappings are skipped. An empty size recommendation leaves the existing recommendation unchanged.

See the Spotler data reference for the values to expect.