Hi, I would like to add a custom field in the profile of each customer that purchase.
For example, if he buys a top then categorize this customer with a custom field that says "top".
If he buys a legging, then categorize this customer with a custom field that classify as come from “legging” colecction.
Same for sizes. If he buys a XS, then a custom field that categorize this customer with a custom field that says XS.
I use shopify plus.
Best answer by retention
@jorgehostalet - One approach is to use the “Update Profile Property Action” in a Flow. It seems a bit unconventional, but you can have a Flow that doesn’t send any emails!
Here’s how I would do it:
Setup a Flow based on an “Ordered Product” event and then do a “Trigger Split” based on the Collection(s) of the product. Then, for each “Collection” path, use the “Update Profile Property” action and set the Custom Profile Property to a specified field name and value.
Here’s an example, where I check if the product is from the collection “Accessories” and set a profile property called “skin_tone” to “fair.” Of course, you would use something like “legging” to “XS” etc.
You can continue to add additional Trigger Splits for each of your Collections and what field name and value you want to set. Notice, this Flow does NOT send any emails!
Hope this helps!
Here’s some additional Klaviyo Documentation that might be helpful!
@jorgehostalet - One approach is to use the “Update Profile Property Action” in a Flow. It seems a bit unconventional, but you can have a Flow that doesn’t send any emails!
Here’s how I would do it:
Setup a Flow based on an “Ordered Product” event and then do a “Trigger Split” based on the Collection(s) of the product. Then, for each “Collection” path, use the “Update Profile Property” action and set the Custom Profile Property to a specified field name and value.
Here’s an example, where I check if the product is from the collection “Accessories” and set a profile property called “skin_tone” to “fair.” Of course, you would use something like “legging” to “XS” etc.
You can continue to add additional Trigger Splits for each of your Collections and what field name and value you want to set. Notice, this Flow does NOT send any emails!
Hope this helps!
Here’s some additional Klaviyo Documentation that might be helpful!
Okey it works but for size I think is different. How can I set up a trigger split like: If he has purchased an item with size XS, create property: Size - XS
@jorgehostalet - You can create another “Utility Flow” like the one above except that it splits based on the variant of the Size field instead of the “Collection” like my example above.
What if I’d like to create a user profile attribute that is an array
Use case a person can buy a shirt from multiple teams and I’d like to have an array that is just “purchased teams”
"Purchased": [
"Auburn",
"Alabama",
"Texas"
]
But I want to add a new team if they purchase a new team, not just a single value.
I know i could do a value for each team like hasPurchasedTexas=true but there are over 200 teams, and thats a lot of extra attributes to add to a rpofile
Seems like an array I could update would be much more useful in that I could do show/hides based on a contains or something
Update Existing Property This option allows you to update the value of an existing custom property. If the property you select is a list of values, you can choose to add or remove a value from the list. If the property doesn’t yet exist for a recipient profile, the property will first be created and then the value will be updated. Klaviyo automatically detects and validates the data type of the property you choose. For example, if you have a property like "Age" and all the existing values are numbers, then you try to update the value to "tom" we'll display an error because "tom" is not a number.
The key here is to ensure that the property you’re updating is a list data type. Else, the data type will be understood as text type which would override the existing property.
“Note that when you add a button or link that can update a profile property, recipients can only select one value. If they already have a value for the property set, their selection will overwrite the existing value. This includes properties with a list data type: the entire list will be overwritten, and it is not possible to simply append a list item to an existing list.”
Are we to understand Klaviyo treats the “update profile” action differently for “flows” (your example) vs. when “someone clicks a link to update a profile property” (the article I provided)?
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).