Importing in-store collection data to Klaviyo

Question

My client is beginning to implement in store email collection for customers. They’d like to use the data to send them flows to nurture the relationship with the customer.

For context the brands sells wollen jumpers, mainly to American tourists visiting Europe.

When the customer makes a purchase they choose from three exclusive options. They will only be in one of these three paths

Ship the items home from the store for free. So they don’t have carry abound bulky jumpers for the rest of their travels. Their details are received from a third party and uploaded via a csv to klaviyo every couple of months
Get a tax back option when the go through customes. Details are collected immediately in-store via iPad sign up
Get a voucher for other store locations while on their travels - there are many store locations in the tourist areas of the country. Details are collected immediately in-store via iPad sign up

What is the best way to align the data collected in-store so that the flows can easily be created in Klaviyo?

Can we create columns in the csv files that will later become custom properties in Klaviyo? For example, demographics, items, purchased, location purchased etc.

Thanks a million!

JessFosnough · Accepted Answer

Hi @GV123!There are a few ways you can approach this. You can have 3 separate lists for the 3 separate paths, but I would suggest using segments.For paths 2 and 3, if you use a Klaviyo sign up form, you can have a hidden property field that will allow you to segment the cusomers. For example, for path 2, you can create a hidden profile property named Tax Back and have it pre-filled to Yes.You could also segment the customers by property fields that the other two paths would not have; for example, for customers in path 1, create a segment where Shipping Address (or Street Address) is not set.You can create colunns in the CSV file that will later become custom properties - here is an article about Understanding Custom Properties. Also, this article about Understanding Data Types is really helpful!Note, once you create a property, the name of the property has to be exactly the same for each import, or it will create a second property if not mapped correctly - for example, if one of your properties is named Street Address and you add a property name named street address (lower case first letters), it could create a brand new property.Hope this helps!

GV123 · Answer

@JessFosnoughthanks for such a detailed response. I really appreciate it!

Reply

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Scanning file for viruses.

This file cannot be downloaded