1st Party Data is data that you already own. Visitor Edge helps you in connecting the dots and allowing you re-identify your visitors. As long as Visitor Edge stays installed, any visitor that comes to your website in the future, will be identified.
Note: We’ll have more integrations to ESPs and activation platforms coming soon in Q2
How we’ll be sending you data to Klaviyo:
- We will be sending “Metrics” to your Klaviyo account
- We will be sending profiles of Visitors to your Klaviyo account
1st Party Data helps you learn:
- Detailed insights on what your customers are buying
- When an old customer re-visits your website
- Who you should add to your audiences
- How to best personalize the User experience
Creating Klaviyo Flows: #
In order to start monetizing your 1P data, we recommend cloning your already existing flows listed below but instead changing the Trigger event to be one of the Visitor Edge’s metrics.
- View Content (Browse Abandonment Flow)
- Add to Cart (Cart Abandonment Flow)
- Initiate Checkout (Abandoned Checkout Flow)
1. View Content (Browse Abandonment Flow) #
For your existing Browse Abandonment flows, your native Klaviyo flow would look something like this with the trigger event as “Viewed Product” under the title.
#
2. AddToCart (Cart Abandonment Flow) #
For your existing Add to Cart flows, your native Klaviyo flow would look something like this with the trigger event as “Add to Cart” under the title.
What we recommend is cloning this existing flow mentioned above but instead we change the Trigger event to be a Visitor Edge based event, normally called “VE_3P_eventname”.
- In this case it is called “VE_1P_AddToCart”.
After cloning your flows for this event you should end up with identical copies of your existing flow, except with the “Trigger” event being different.
#
3. Initiate Checkout (Abandoned Checkout Flow) #
For your existing Abandoned Checkout flows, your native Klaviyo flow would look something like this with the trigger event as “Checkout Started” under the title.
What we recommend is cloning this existing flow mentioned above but instead we change the Trigger event to be a Visitor Edge based event, normally called “VE_3P_eventname”.
- In this case it is called “VE_1P_Initiate Checkout”.
After cloning your flows for this event you should end up with your flows looking like this for each event/scenario mentioned above:
- We have 1 Flow based around 1P and another flow based on 3P data. (we’ll add this in the next step where we talk about 3P data)
