Why use Klaviyo Enrichment?
Reach customers that browser-based tracking misses
Klaviyo's native tracking relies on cookies and browser-side scripts, which means ad blockers, privacy settings, and iOS restrictions can prevent events from firing. ProfitPeak sends the same events server-side, so you capture more of the customer journey and trigger more flows.
Run enriched flows alongside your existing ones
You don't need to replace your current Klaviyo setup. Clone your existing flows, swap in ProfitPeak triggers, and run them in parallel. The original flow handles customers Klaviyo tracks natively, while the ProfitPeak flow catches everyone else.
Avoid double-sending with simple safeguards
Add conditions to your ProfitPeak flows that check whether the customer already received the original email. Then add a short delay (10 to 15 minutes) so the original flow has priority. This keeps your sending clean without manual monitoring.
How the data is structured
Once ProfitPeak is connected to Klaviyo, events are sent as ProfitPeak-specific triggers that mirror Klaviyo's native events. These appear in Klaviyo's flow builder as separate trigger options, so you can build flows that respond to ProfitPeak events specifically.
Available ProfitPeak events in Klaviyo:
Profit Peak Added Product to Cart
Profit Peak Completed Checkout
Profit Peak Order Completed
Profit Peak Removed Product from Cart
Profit Peak Started Checkout
Profit Peak Viewed Cart
Profit Peak Viewed Collection
Profit Peak Viewed Page
Profit Peak Viewed Product
Each event matches its native Klaviyo equivalent, giving you flexibility to enrich any flow type from browse abandonment through to post-purchase.
Setting up an enriched flow
Clone your existing flow and rename it with a pipe and "ProfitPeak" at the end (e.g., Browse Abandonment | ProfitPeak)
Swap the trigger to the equivalent ProfitPeak event
Add a condition to exclude anyone who received the original flow email (zero times since starting this flow)
Add exclusion triggers where relevant (e.g., exclude Added Product to Cart from a browse abandonment flow)
Add a 10 to 15 minute delay at the start so the original flow sends first
Preview, test, and turn on when ready
Where to go next
Once your enriched flows are running, you can measure their impact:
Check the Attribution Vertex to see how Klaviyo performs as a channel
Use Sherpa to ask how your flows are contributing to revenue
Review Customer Intelligence to understand how email touchpoints fit into the broader customer journey