Skip to main content
Solved

Capturing Data for Custom Properties from User Navigation

  • November 28, 2022
  • 2 replies
  • 132 views
S
Contributor II
Forum|alt.badge.img+2

Hello, 

I am new to Klaviyo, and as a developer, I am looking to be pointed in the right direction.

I would like to capture certain navigation values on my site (if they click a certain size, I want to capture that).  I would then add that to the user’s profile data if I knew who they were, or retain it should they purchase or otherwise complete a form.   

I can capture and retain information using the GTM Data Layer, but wonder if there is a better way using Klaviyo.  I also wonder the best way to add/update the user’s profile with the information so I can later help the user know about sales or in their size or preferred colour etc.

Sorry for this basic question.  I just can’t find information other than submitting information via a form submit.

 

Best answer by Brian Turcotte

Hi @scotiaceilidh and welcome to the Community!

 

This is a fantastic question! Klaviyo can certainly be leveraged to understand user activity such as size preference, page views, etc., it just depends on your specific use case and how your e-commerce store is setup. It’s true that the simplest way to accomplish this would be to include size preferences on your sign up form, but there are some other potential workarounds. 

 

There is a native Viewed Product metric, but it doesn’t pass size/variants like the Ordered Product metric. If you want to use that metric to track size data, you would have to edit the actual snippet on your site to include size tracking, a task that would vary depending on the type of store and your development capacity. If you would like more in-depth help on development, you could always reach out to our wonderful network of official Klaviyo Partners.

 

As far as gathering size preference from a page view (instead of product), it again depends on how your store is set up. If each size is relegated to its own page, then you could use a Custom Viewed Page Metric as I outlined in this post, labeling each page with the size:

 

If you choose this option, you could then create a flow that’s triggered by the Viewed Page’ metric that updates users’ profile with a custom size property:

Update Profile Property with Flow

 

I hope this helps to clarify, and thanks for using the Community!

 

- Brian

 

 

View original
    Did this topic or the replies in the thread help you find an answer to your question?

    2 replies

    Brian Turcotte
    Forum|alt.badge.img+37
    • Brian Turcotte
    • Klaviyo Alum
    • 1393 replies
    • Answer
    • November 29, 2022

    Hi @scotiaceilidh and welcome to the Community!

     

    This is a fantastic question! Klaviyo can certainly be leveraged to understand user activity such as size preference, page views, etc., it just depends on your specific use case and how your e-commerce store is setup. It’s true that the simplest way to accomplish this would be to include size preferences on your sign up form, but there are some other potential workarounds. 

     

    There is a native Viewed Product metric, but it doesn’t pass size/variants like the Ordered Product metric. If you want to use that metric to track size data, you would have to edit the actual snippet on your site to include size tracking, a task that would vary depending on the type of store and your development capacity. If you would like more in-depth help on development, you could always reach out to our wonderful network of official Klaviyo Partners.

     

    As far as gathering size preference from a page view (instead of product), it again depends on how your store is set up. If each size is relegated to its own page, then you could use a Custom Viewed Page Metric as I outlined in this post, labeling each page with the size:

     

    If you choose this option, you could then create a flow that’s triggered by the Viewed Page’ metric that updates users’ profile with a custom size property:

    Update Profile Property with Flow

     

    I hope this helps to clarify, and thanks for using the Community!

     

    - Brian

     

     

    S
    Contributor II
    Forum|alt.badge.img+2
    • scotiaceilidh
    • Author
    • Contributor II
    • 4 replies
    • November 30, 2022

    Hello Brian, 

    Thank you for your response.

    We have to be really careful what data we collect, as the wrong data collection method can be mis-leading.  For example, if we collect size information from products we currently offer, the data we get will just reflect what we offer at best, or just what is in inventory at worse.   What we want to know, is what size (There are 65 sizes for each product we offer, but there are another 40 we could offer).  So, what we are developing a a size calculator that spits out the correct Bra Size and leading traffic into it as a 1st step in their buying process.  The calculator results will therefore tell us what people are looking for from the full spectrum of options (not just from the range we offer, or what is currently available in stock).  This will inform what we stock, and allow us to correlate size with certain styles.

     

    There is also a lot of personalization we can do now that we have the customer’s size.  But the first step is capturing it in Klaviyo, and it would best be done triggered off the user getting the result, not just holding onto it in a variable with the hopes they will submit a form or order at a later point.  If we know the customer via Klaviyo, I would like to update their Profile with their size info.

     

    Hope that helps understand what I am looking for.  I really appreciate your help here.

    Brian Turcotte
    1 person likes this
    • Brian Turcotte
      Brian Turcotte

    Reply


    Terms & Conditions

    Links & Resources

    Platforms

    Partners

    Useful Things

    About

    • Terms and Privacy |
      © 2024 Klaviyo All rights reserved. Klaviyo and the Klaviyo logo are trademarks or registered trademarks of Klaviyo, Inc. or its affiliates.