I’m trying to create a saved search to use as a KP...
# suiteanalytics
k
I’m trying to create a saved search to use as a KPI to show the repeat customer percent (customers with 2+ orders compared to customers with only 1 order), but I can’t seem to wrap my head around it. Anyone have any ideas?
k
I'm not sure this can be done without some level of scripting.
I'd be inclined to put a checkbox on the customer record when they place their second order. Then my formula becomes
count(decode({customer.customfield},'T',{internalid}))/nullif(count({internalid})
k
That’s what I was leaning towards as well
t
this would be better off as a scorecard
one search with customers that have orders =1
one search with customers that have orders > 1
and divide the two
👍 1
k
I mean, sure - that gets a KPI - but I don't think it's a meaningful KPI.
If the ask was "show me a % of repeat customers forever" that does it. - but that percentage isn't likely to change drastically. It's not really actionable
Where as if you try to say "what was our % of repeat customers in the last month" - with that checkbox you can then do a transaction search and look at your flow/change over time. You'd also be able to establish some relationship with marketing efforts if one month had a higher percentage than others.
But as a straight percentage strictly on a customer search means each time you add a new customer, it goes down, and each time a customer orders for the first time as a repeat it goes up - when you have hundreds of customers you may notice it moving some, but if you have thousands? I wouldn't expect it to shift more than small fractions of a percent from month to month.
You also wouldn't get credit for a repeat customer becoming a 3 peat, or 4 peat or whatever frequency they have ordered with a straight customer search.
t
I don't disagree that's what it does, I do disagree it's not a meaningful KPI. "How many of my customers have ordered more than once from me" is a pretty standard metric to look at and improve. Whether that is something you want to look at on a period by period basis could be done on the transaction level / order date (or some other customisation, as you suggested).