This guide shows you how to integrate Neocom with Klaviyo.
The private API Key from your Klaviyo account with write access to lists
, profiles
, subscriptions
and events
The ID
of a Klaviyo list that Neocom should add and subscribe user profiles to. We recommend creating a new list for Neocom.
The Klaviyo list and Neocom Advisor's Save For Later feature use the same opt-in settings
<aside> <img src="/icons/warning_red.svg" alt="/icons/warning_red.svg" width="40px" />
We strongly caution against using single opt-in unless your specific use-case requires it.
</aside>
When a user submits their email via Save For Later and confirms their subscription*,* Neocom creates a new user profile in Klaviyo.
<aside> <img src="/icons/info-alternate_yellow.svg" alt="/icons/info-alternate_yellow.svg" width="40px" />
If a profile with this email already exists in Klaviyo, creation of the user profile is skipped.
</aside>
If double-opt-in is enabled, the profile is created about 8-10 minutes after subscription confirmation
Neocom then adds a Save For Later Event to the profile and subscribes the ****profile to the Klaviyo list.
<aside> <img src="/icons/info-alternate_yellow.svg" alt="/icons/info-alternate_yellow.svg" width="40px" />
If single opt-in is used, the profile is only added to the list without being subscribed.
</aside>
User profile is added to the list & subscribed to email marketing
Conversation data is added to the profile
The Save For Later Event contains all conversation data to build customised emails and to enrich user profiles with custom attributes.
Any automation in Klaviyo is done via flows. The most reliable way to automate with Neocom's data is to use Saved For Later Event metric as flow trigger.
Create a new custom flow in Klaviyo
Add a descriptive name for the flow
As Trigger, select API Metric
Select the Neocom Saved For Later Event
<aside> <img src="/icons/info-alternate_yellow.svg" alt="/icons/info-alternate_yellow.svg" width="40px" />
Users that were added to a list via Neocom do not trigger ****the “Added to list” ****event. Instead, we are using this event as starting point for our flow.
</aside>
<aside> <img src="/icons/info-alternate_yellow.svg" alt="/icons/info-alternate_yellow.svg" width="40px" />
Optional trigger filters can be set up to start the flow only for certain advisors.
Add optional trigger filters
Filter by advisor_name
to only trigger this flow for the “Snowboards” advisor
</aside>