My recommendation is to first build a segment of these user groups, if by “new” you mean never placed an order, then I would use the definition: What somebody has done > Placed Order > Zero Times over all time. And if by returning you mean placed at least one order: What somebody has done > Placed Order > At least Once > over all time.
Optionally, if you want to include the date the profile was created, you can bake that into the segment definition as well, to limit the segment to users created before X day or between dates X and Y. Here’s an example of someone who placed an order at least once between 30-60 days ago and was created before today (I picked today’s date arbitrarily).
Once you have those segments set-up, you can simply export them directly from the “Placed Order” metric, (more instructions on how to achieve that here) which will contain all profiles in those segments with their revenue data over all time. I recommend just exporting the email address field for these profiles.
From here, if you’d like, you can add a custom property to these groups in the exported .csv file (new vs. existing) and re-upload them to Klaviyo. The reason I’m recommending segments first (rather than build the report outright) is because we’ll only track events in the reporting tool for events that take place after the property is added. So until you have those custom properties added to those profiles, you won’t be able to filter these users as you wish using the reporting tool. That’s why building the segments is handy (in it’s own right) and then subsequently re-uploading these users will allow you to use the reporting tool for these profiles moving forward.
My recommendation is to first build a segment of these user groups, if by “new” you mean never placed an order, then I would use the definition: What somebody has done > Placed Order > Zero Times over all time. And if by returning you mean placed at least one order: What somebody has done > Placed Order > At least Once > over all time.
Optionally, if you want to include the date the profile was created, you can bake that into the segment definition as well, to limit the segment to users created before X day or between dates X and Y. Here’s an example of someone who placed an order at least once between 30-60 days ago and was created before today (I picked today’s date arbitrarily).
Once you have those segments set-up, you can simply export them directly from the “Placed Order” metric, (more instructions on how to achieve that here) which will contain all profiles in those segments with their revenue data over all time. I recommend just exporting the email address field for these profiles.
From here, if you’d like, you can add a custom property to these groups in the exported .csv file (new vs. existing) and re-upload them to Klaviyo. The reason I’m recommending segments first (rather than build the report outright) is because we’ll only track events in the reporting tool for events that take place after the property is added. So until you have those custom properties added to those profiles, you won’t be able to filter these users as you wish using the reporting tool. That’s why building the segments is handy (in it’s own right) and then subsequently re-uploading these users will allow you to use the reporting tool for these profiles moving forward.
I was about to suggest the same but I wasn’t sure whether the segment would contain all previous purchase data or just for the chosen period. That being said, when exporting the segment, should “Historic Customer Lifetime Value” be exported along with email for this kind of a report?
Also, for repeat customers, shouldn’t the correct segment be What somebody has done > Placed Order > is greater than 1/is at least 2 > over all time.
I created the segments, exported, reimported into Klaviyo with the custom property:
Customer: No First Time Repeat
Then updated the flows relating to thank you to update these segments so if they join any segment through the welcome series and haven’t placed an order the profile is updated to: Customer: No
Thank you page Customer: First Time
Repeat customer: Customer: Repeat
Now to filter the original segments through the event page to see how much they’re bringing in. Thanks again so much!
Actually I must be doing something wrong in these settings, filtering by the new profile property but the value of ordered product is showing up as $0 for the whole date range..
Hi @NJVasic! Good questions - let me jump back for a second to clarify a couple of things. First, you’re totally correct that the revenue from the profiles directly through the segment export would be over all time rather than just during that 30-60 day period. I updated my original reply to reflect that -- my mistake. The purpose of creating and exporting these segments were twofold: 1) to establish the email addresses for both “new” vs “returning” customers within that timeframe which is helpful in its own right (to know who they are). And also for purposes of later sending campaign(s) to these users or putting them through a flow 2) It’s the first required step (followed by export + re-upload) to allow Michael to begin using the filtering function in the reporting tool for “new” vs “returning” users.
While it’s not necessary for the purpose of this thread, I’m curious to better understand where your thinking is going for exporting Historical Lifetime value?
In terms of the segment definition itself, since Michael mentioned “returning” (rather than repeat) that typically refers to someone who has purchased at least once, but of course you can adjust the segment definition to accommodate the target audience, if the intention was really “repeat” rather than returning updating Placed Order to at least twice would be the right move, as you suggested.
And @Michael, glad to hear you’ve got these profiles updated in Klaviyo with their new custom properties. Let me clarify something from the original reply (also worth noting it’s called out in our documentation under Add Group By: “Note that reports only include events filtered by a profile property starting after that property was created. Even if a property was retroactively applied, if it didn’t exist on profiles at the time the event takes place then it won't appear in the report.”) In other words, we’ll only track events in the reporting tool for events that take place after the property is added. So you’ve got the first part down of getting the filter available in the reporting tool by segmenting, exporting and re-importing these users with the properties. So moving forward, as they log net-new order metrics, you’ll be able to use reporting for profiles with these properties but it won’t apply retroactively for past placed order events.
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).