Personalized Messaging Recommendations are now available to all sites using Klaviyo or Dotdigital as their marketing automation provider.
To enable personalization of these messages, we must pull customer data to connect email addresses and phone numbers to the ecommerce platform shopper ids. Sites using Shopify, Bigcommerce, or Magento as their ecommerce platform can take advantage of our native data extractors to pull this data into our system. All other sites can provide this mapping through a custom feed.
New settings for the related data feed have been added in the Searchspring Management Console (SMC). The feed credentials will be encrypted in our database, and all email addresses and phone numbers will be hashed before storage in our service.
Note: This feature is available only for sites with Personalized Messaging Recommendations enabled. If you do not have this feature enabled, please contact your Customer Success Representative or email success@searchspring.com to find out more.
Feed Access Parameters
The configuration for the access credentials appears below the DotDigital credentials entry point on the Personalization Settings page. In the Searchspring Management Console (SMC), navigate to Site Customizations and then Settings. Scroll down to "Feed Access Credentials".
In the Site Customizations\Settings form, the following fields must be populated. These parameters allow Searchspring to integrate with your customer feed for the enhanced functionality of personalized messaging recommendations.
Note: The credentials provided above are encrypted and securely stored. In addition, the customer email addresses and phone numbers are hashed before they are stored in our service. We do not export or save any other personally identifiable information (PII) such as names, addresses, or billing information. Searchspring only requests access to the specific fields mentioned in order to map the message recipients to their site activity, so that we can power Personalized Messaging Recommendations. If you discontinue use of our personalization service, we will delete all customer records related to your store. To learn more about Searchspring data protection policies, click here.
Formatting the feed data
Feed Location
Feed URL
This value is required. It must be a valid URL and include https:// before the web address. Our service will also pass startDate and endDate query parameters, which you can choose to implement or ignore. If your feed URL is able to handle this date range, it will optimize our ability to stay in sync while pulling the minimum amount of data each time. Dates use the ISO standard “yyyy-MM-dd”. An example of this request is:
https://yourfeedurl.com/path/customers.csv?startDate=2024-01-01&endDate=2024-04-05
Note: If the server where your feed file is located is IP-restricted, all Searchspring IP Addresses must be allowed access.
Feed Type
Click the drop-down menu to select a feed type. Options include the following:
- .csv
- .tsv
- .json
All three feed types utilize one row of data per unique shopper.
CSV / TSV
For .csv and .tsv files, columns are delimited by a comma, or a tab. Column entries are to be wrapped in double-quotes to contain the data within; all double-quotes within that data entry must then be escaped. In both cases, the header row must identify the order of the data in all other rows, and include the three column names: “shopperId”, “email”, and “phone”.
JSONL
For .json files, each product object representation must exist in a new line of its own. Each data row must contain the tag/value pairs for shopperId, email, and phone, as in
{ “shopperId”: “abc123”, “email”: “name@domain.com”, “phone”: “0011234567890” }
Credentials
The feed endpoint should be secured using basic authorization. Enter the username and password in the SMC form.
Username
This value is required. Provide the username associated with the feed credentials.
Password
This value is required. Provide the password associated with the feed credentials. Click "Show password" to reveal the password.
Collected data
The following data will be collected by the feed:
- ShopperId
- Email address
- Phone number
Note: The phone number must be formatted using the E.164 International Standard; more information about that standard is available here.
Comments
0 comments
Please sign in to leave a comment.