Data Sync

High level overview of how the solution syncs data

Customers

Once the preferred frequency is determined by the merchant, the timings in Apparel21 must be configured accordingly. This automated scheduled process operates seamlessly in the background, where the SFTP service, integrated with the DotCustomerHub app, efficiently exports the necessary files and promptly triggers the import task into Klaviyo.

Based on the determined schedule, the 2 CSV files containing Apparel21 customer and order data are uploaded to the SFTP of each DotCustomerHub instance and then instantly flow through to Klaviyo. Customer attributes are synced to a Klaviyo profile with a matching Apparel21 email. If a matching profile is not found, a new profile is created.

Profile Creation

When a profile cannot be found by email as a result of Apparel21 to Klaviyo sync, it is created and added to a “Klaviyo List”. The profile will not be subscribed if Privacy is set to Yes during sync. The profile’s source will be set to the name of the retail store at which the customer signed up.

Apparel21 Privacy is set to No = Customer will receive emails

Apparel21 Privacy is set to Yes = Customer will not receive emails

Segment Setup

Once the solution is configured and the customer and order data is flowing through to Klaviyo successfully, there are a few steps to ensure that the data populates the respective customer segments correctly. By using the mapping tool, customers can be assigned to a default list, such as "{branch name} Retail Customers." However, for more specific segments or groups, it is necessary to set up rules within Klaviyo based on the properties of the Klaviyo profiles. These properties could include information like the joined store code, which helps differentiate customers who signed up in-store versus online.

Orders

Once the required customer profile has been created within Klaviyo, we are able to send through "In-Store Order" events that include all the related information for the transaction, include amounts, store, staff details, and the specific item details.

Event will be added to the customer profile and can be used to trigger various flows.

Rewards

An additional feature that we support is syncing across information from your reward program. This information includes top level details like program, points, tier that are saved to the customer profile as custom properties and also specific information about the reward event like date, reason, description, points gained/redeemed and gifts.

Bulk Sync

The bulk sync is a one-time task designed to seamlessly sync historical data and persons from AP21 into Klaviyo. This is needed to ensure that all customers (not just online) actually have a profile in Klaviyo.

Before generating the bulk file, we must be informed of the specific date you wish to have the data from (i.e., from Jan 1, 2023 to present).

It's crucial to note that with the Bulk Sync, marketing preferences within Klaviyo will remain unchanged for existing Klaviyo profiles.

Following the successful import of the bulk file and the initiation of automations, any subsequent modifications to an individual's record in AP21 will seamlessly update Klaviyo, including privacy status. This sequence guarantees that historical data takes precedence, and any subsequent "events" will be accurately reflected in the Activity Log section in Klaviyo.

Importing Bulk Files

Bulk files encompass historical data from a specific predetermined date extracted from customers.csv, orders.csv, and rewards.csv (only applicable if rewards are enabled).

As a standard procedure, bulk files are imported during the initial step, allowing all historical data to be utilised for segmentation rules.