Klaviyo guide

The Junip integration with Klaviyo allows you to manage the entire review solicitation process from Klaviyo. 

Sending review requests from Klaviyo directly helps in maintaining consistent branding, domain/sending authority, following suppression guidelines & more flexibility using their flow builder. We also create an event in Klaviyo when a new review is submitted, letting you track your success and follow up with customers.

First things first is authorizing Junip to send events to Klaviyo. You can do that in our admin at "https://admin.juniphq.com/integrations".

Once you've added your Klaviyo API key, we'll begin sending three events into Klaviyo:

1. Junip - Order fulfilled
2. Junip - Order Targeted By Campaign
3. Junip - Review created

A full list of the variables for these events can be found here.

Junip - Order fulfilled

This is used to fully manage the post purchase review request flow within Klaviyo, no longer sending any review requests from Junip. This doc covers how to make a basic product review request flow, we'll continue to create more examples of flows & would love to see what you've created.

Junip - Order Targeted By Campaign

This event is triggered by our Campaign builder. When you create a campaign audience within Junip, you can send it to Klaviyo as an event instead of sending the review request email from Junip.

Junip - Review created

Review created sends an event to Klaviyo when someone leaves a review (along with the data from that review). You can use it to kick off flows like refer-a-friend, or segments like "happy customers" & "detractors".

Making the switch

If you're already sending requests through Junip & switching to send through Klaviyo, you want to be careful to not double send. The best way to make sure you avoid this is to turn off your emails in Junip when you turn on the Klaviyo flow, then make up the missed customers with a campaign. If you have any questions on this just shoot us a message.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.