Hi Jingze,
There a few a options you can manage when I did take a look at your site.
1. Click Tracking - This could pull the data from the clicked items. Using the selectorPath identification you could use div#refine-group > ul > li > a for the selector path. That should only gather clicks from the filter areas. It would be a good idea to create different click rules for each category of clothes to make it easier to parse the data later.
There could be issues related to pulling the correct data but the HTML does specify an HTML5 attribute (which can be chosen in the click custom event custom attribute section). The label is aria-label which would return things like "size 15-33 17 Products". This attribute is generally used for assistive technologies and should be relatively stable.
2. URL parsing - currently if you have a page load rule, you could parse the URL to see what is currently being selected. This has the added benefit that if you already have setup everything, you could go back and pull the data. For example:Your URL is https://www.paulfredrick.com/shop/dress-shirts/color=grey%5Egreen/size=15-32%5E15-31%5E14,5-33/collar=spread and you've created page load rule for dress shirts. You could then parse it to pull out that you have color: grey, green ; size: 15-32,15-31,14,5-33 Etc.selected. Each page load would give you more or less items, and this allows for a more robust picture of what users are interested in. You could also combine this with a product view and then use the previous page view with the filters to then track the user journey more easily as well. Setting up a new rule for each category (pants, shirts, etc.) would make it easier for data processing later but not a requirement!
3. JS API. This would require additional dev work, but it could be done. You would have to direct developers to add in click events to send data back to ci360. The config would be a bit more specific and in depth than I can go into here but more customization for data sent to ci360 in the end.
4. It might be possible with a good amount of work to pull all the filtered values from the page itself. I think the hardest part of this would be that some of the filtered values are defined in div that aren't very unique or don't have unique values so this might be a bit harder to manage without a bit of change to the html generated. It would be possible if all <a> values were returned, but I would need to test it and likely would return many values that you're not interested in.
Out of all these options, click tracking would be the easiest to implement. But there are some downsides including the tracking of deselect clicks within the filter areas.
URL has the benefit of older data if that matters to you but requires you to parse the data outside of ci360 which may not be viable. This one would already be setup from a data collection viewpoint as well.
If you have any questions let me know! Happy to help or clarify anything.
Cheers,
Jeffrey Stroud
... View more