Skip to main content
All CollectionsData Activation (Email)
How to Activate 3rd Party Data
How to Activate 3rd Party Data

Guide on integrating and utilizing third-party data in Klaviyo to enhance your email marketing campaigns.

Updated over 2 weeks ago

3rd Party Data aka "Amplify"

3P Data (Amplify) is data that you get access to, giving you enriched profiles of unknown visitors. These are usually visitors that came to your site, browsed around for a bit, added something to their cart, but never filled out any form. You will now know who they are, allowing you to recover those unknown abandoned carts. Note: All of our 3P emails that we deliver to your ESP are always Validated and Verified.

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 identified Visitors to your Klaviyo account

  • We will also sync profiles when they go from being 3P to 1P.

3rd Party Data helps you learn:

  • Information about your current visitors

  • What your window shoppers are interested in

  • Who you should add to your audiences

  • How to best personalize the User experience


Creating Klaviyo Flows

In order to start monetizing your 3P data, we recommend CLONING your pre-existing successful flows listed below but instead changing the Trigger event to be one of Visitor Edge’s metrics.

  • View Content (Browse Abandonment Flow)

  • Add to Cart (Cart Abandonment Flow)

  • Initiate Checkout (Abandoned Checkout Flow)

Example: Initiate Checkout Visitor Edge Flow

For your 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_3P_Initiate Checkout”.

After cloning your flows for this event you should end up with several flows looking like this for each event/scenario mentioned above:

Did this answer your question?