Woocmerce with klaviyo

Hi ​@Saira Nawaz , 

Great question here, especially if you’re thinking long-term personalization from the start.

In most cases, the best approach will be a combination rather than relying on just one data type. From what we’ve found works best, product-level details should stay tied to catalog or event data, while customer-level traits that you want to reference often for segmentation or personalization can be stored as profile properties.

So for example, if cabinet capacity or manufacturer is something that describes the products a customer has purchased, that may begin as product or event data, but if you want to use it repeatedly for future targeting though, it might make sense to also roll that up into profile properties. Same goes for owned accessories versus not yet purchased accessories, where many brands we’ve seen will use a mix of event data, profile properties, and segments depending on how dynamic they want that logic to be.

Because the right structure really depends on how your WooCommerce data is coming into Klaviyo and how you plan to use it later, I’d recommend reaching out to Support so they can give more tailored guidance on the most scalable setup for your use case! 


 

Temi@Klaviyo