Expand my Community achievements bar.

SOLVED

Query on segmentation usecase

Avatar

Community Advisor

Hi,

 

We have a usecase where we need to create a segment of premium customers. Premium customers to us meaning the top 5% of maximum purchasers on the website. 

 

Is there a way to achieve this via segmentation because the top 5% is a relative number and will change as more and more customers purchases the product.

 

Also I have one more question. I am trying to create a segment by comparing two date time field using the below logic . While doing this i get this the below error. Any idea what i am doing wrong

arpang16406580_0-1690231417719.png

 

Thanks in advance.

 

 

@Danny-Miller @Anil_Umachigi @ChetanyaJain @arijitg 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Danny-Miller @NimashaJain  - I was able to fix this using the following approach . I wrote a scheduled query that is calculating the price and later putting that directly as a new attribute to the linked profile. For now i am running the query every 6 hours and its serving the purpose of our client.

 

Thanks,

Arpan

 

 

 

View solution in original post

4 Replies

Avatar

Employee Advisor

@arpan-garg I missed this one, but saw it today.

If you have Purchase stored on the Profile (not EE), I would use Audience Composer (Rank), keep in mind this is a raw count, not percentage.

 

If you don't, then use Data Distiller and either:

  1. Put Purchase Amount onto Profile and use Audience Composer OR
  2. Do the Rank in your SQL and store Purchase Amount and Ranks (asc and desc) onto Profile.  Then build your Audience as normal filtering on Purchase Amount Asc less than 10.
    1. Note: You might want to store both raw rank and percentage

I'm not sure what that error is you gave in the screenshot.

Good luck

Avatar

Correct answer by
Community Advisor

Hi @Danny-Miller @NimashaJain  - I was able to fix this using the following approach . I wrote a scheduled query that is calculating the price and later putting that directly as a new attribute to the linked profile. For now i am running the query every 6 hours and its serving the purpose of our client.

 

Thanks,

Arpan