Im looking for advice on how to effectively segment my lists -
I have a store that sells kimonos and jewellery. I have created segments for people who have viewed product or bought product from each category. However I have the issue of people coming onto the website and viewing the category page but not viewing a specific product meaning they dont get segmented. Now as far as I can tell, I can create a rule to segment for viewed product contains xyz but I cannot create a rule for viewed category page.
I should also mention that they are being subscribed to a single main list and then being segmented from that list.
One solution I have is if i want to send a newsletter about kimonos, I can send to my list and then exclude jewellery buyers/ viewers. However, the issue with this is that I have people who still come onto the jewellery category but dont view products, and thus dont get segmented. So then these people still end up recieving my kimono newsletter when they arent interested. (Also the issue of people viewing both categories!)
I could send the newesletter to only kimono product viewers/buyers, but I miss out on the customers who only viewed my category! Bit of a catch 22
Is there a more effective way to get around this issue? What I really need is to segment to people when url contains /jewellery or /kimono, but as far as I can tell I cannot segment by url.
This also leads on to my welcome flow - people sign up and recieve my generic welcome series, but I want them to have speficic flows for jewellery/kimonos. Again, I can create a conditional split where if viewed product contains xyz then split - but for those that havent viewed a product (and only viewed a category page), is there a way to also split for these people?
Thanks and hope this makes sense. I guess essentially the issue is how do you segment for people who have just viewed a category page only…
I am aware that I can use custom code to talk to klayvios API, but I am not that savvy and would much prefer it if there was some clever sementation tactic that I could employ as opposed to having to write custom code. ( Although if this really is the reccomended solution then I can put some time in to figure it out or hire a web developer)
Best answer by Taylor TarpleyView original