Using Reclaim for Product Views:
We must enable this feature for you. If you’ve not already spoken with someone on our team, please ensure you request that we enable this for you.
This feature can identify product and/or category views/abandonment for both unknown, non-logged in users (Resolve contacts) and known, non-logged in customers (emails in your suppression list).
To use this feature, you must first ensure that you’re using the most recent version of our script on your website. The base script must fire before the Product Views script. You can find your script in your Retention.com account under Code Script > View Script.
This feature works for any e-commerce website, we will show examples for Shopify in this tutorial.
Click here for a link to all our tutorials on how to add the script to your site, in case you need a refresher.
ON YOUR WEBSITE:
There are two options for updating your Viewed Product events for Reclaim:
- RECOMMENDED, our instructions will use this method. You can create a new Viewed Product event name that will be unique to Reclaim. For example, “Viewed Product – Reclaim.” You will create a cloned/unique flow for these events.
- You can update your existing Viewed Product events to include those coming from Reclaim and add them to all other Viewed Product events. If you do this you’ll need to ensure you add a filter to your existing Viewed Product flow to prevent duplicates. Jump to “Flow Filter for Viewed Product Flow” for instructions.
1. Locate your Viewed Product tracking snippet from Klaviyo. If you are using Shopify, this should be located in the liquid template for the product page(s).
The Viewed Product tracking snippet that you need to locate looks like this:
_learnq.push(['track', 'Viewed Product', item]);
Here’s an example of the full snippet with an item’s image URL, price, etc:
Note: If you do not have a Viewed Product tracking snippet installed, skip to Step 3 below.
2. Add the following script to the your existing Viewed Product tracking snippet in Klaviyo:
<script>geq.event('Viewed Product Reclaim', item);</script>
So the whole thing should look like this (we’ve not included the additional details for price, image URL, etc here):
_learnq.push(['track', 'Viewed Product', item]); geq.event('Viewed Product Reclaim', item);
3. If you do not have an existing Viewed Product tracking script, add this to your theme:
Once this script update has been implemented properly, and the event is triggered, you will see this new metric populate in Klaviyo.
- Clone your existing Viewed Product Flow. Put the word “Reclaim” at the beginning of the new name, eg: “Reclaim Viewed Product Flow.” If you don’t already have one set up, check out Klaviyo’s recommendations for setting this up.
- Change the Trigger metric from Viewed Product to “Viewed Product Reclaim.”
If you’re starting from scratch, Create a New Flow and choose “Metric” as your flow trigger, then Viewed Product Reclaim:
- Next, add the following recommended Flow Filters:
Are not in the original Viewed Product Flow
Placed Order zero times since starting this flow
Started Checkout zero times since starting this flow
hasn’t been in this flow in the last 7 days
Added to Cart zero times since starting this flow (assuming you are using the Added to Cart metric)
- Recommended. Add a Conditional Split for those who are Retention.com/Resolve contacts (ie, unknown, not logged in) and those that are known but not logged in. This will let you compare ROI from Resolve contacts vs Klaviyo’s unknown/unauthenticated customers.
Note that this requires our Klaviyo integration identifier to be turned on. Contact us if you need this enabled.
5. Now, add your Viewed Product abandonment emails down each path of the conditional split. Send the same content to each path.
Flow Filter for Viewed Product Flow
If you are not using our recommended Viewed Product name (Viewed Product Reclaim) and instead folding all our events into your existing Viewed Product flows, you will need to add this flow filter to measure the results properly.
We attach an event identifier with every event we send called:
After you have implemented the script on your site and events are flowing, you will need to adjust your existing flow to add a Trigger Filter.
- Open your existing Viewed Product flow.
- Add a Conditional Split after the Viewed Product trigger.
- For the Yes path, set it to:
What someone has/has not done
Person has Viewed Product
at least once
in the last