Junip's unique integration with Omnisend allows you to manage the entire review solicitation process from Omnisend, which has become a game-changer for brands.

Topics we'll cover in this guide:

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

More info on the integration in our blog post here.

We send review data in the form of events to Omnisend, which allows you to trigger actions that are based on those events. Each event has dynamic review information that you can use in your Omnisend flows and emails to ensure a seamless experience for your customers.

You can find a list of the events we send and brief description below.

A full list of the variables for each event can be found here.

Triggered when a review is to be requested. This is used to fully manage the post purchase review request flow within Omnisend, no longer sending any review requests from Junip.

Triggered when a Junip campaign selects an order to be reviewed. When you create a campaign audience within Junip, you can send it to Omnisend as an event instead of sending the review request email to that audience from Junip.

Triggered when a customer submits a review. This includes data from that review, so you can use it to kick off flows like refer-a-friend, segments like "happy customers" & "detractors", or send the incentive code that was awarded to that customer for leaving a review (instead of the automatic email from Junip).

Triggered when a review requires confirmation. This allows you to send the "confirm identity" email through Omnisend (instead of Junip) when a review is submitted from a source that requires confirmation.

Please note: we've recently updated the names of our events so if these event names do not match what you're seeing, then you can still use your old events without issue. This help doc explains the event name changes in more detail.

Since you're working in Omnisend's platform to perform these actions now, you can leverage all of the features they offer; like A/B testing, suppression lists, conditional splits, customer segments, etc.

You also have a lot more customization in how you perform these actions, your email can be totally custom & on-brand, and a lot of brands appreciate being able to send an email or SMS as the message, add segmentation to the flow, or perhaps a reminder message some days later.

We'll be highlighting some awesome use-cases and examples of things we've seen brands build with this integration, get in touch with us if you want to share yours and be featured!

There are three main steps to setting up the Omnisend integration, which are as follows:

You need to tell Junip where and how you want to send messages for things like review requests, incentives, etc. By default, we'll send these using Junip's emails. If you're integrating with Omnisend, then you'll want to change this so that instead of sending an email from Junip, we'll send an event to Omnisend (where you can send the message).

This guide explains step-by-step how to add Omnisend to your Junip flows to do that.

Reminder to make sure that your flow in Junip is enabled, this means it will start sending events to Omnisend, but Omnisend won't actually send any messages until you've enabled the flows on their platform. That's why we suggest enabling this asap and then using the Omnisend flow status as the final check to enable when you're ready.

The guide above mentions this but this is important enough that we thought we'd reiterate. Now that Junip is sending those events to Omnisend, we need to set things up on Omnisend's end to take the event and turn it into something useful, like a message (or sequence of messages).

You'll want to setup a flow and an email -- we'll offer instructions to create a basic version of both below:

This guide walks you through the process for creating a basic review request flow in Omnisend, this is the flow we'll use to automatically request reviews after a customer's order is fulfilled / delivered and is the priority to start.

This is meant as a starting point, so feel free to create other flows for different purposes, or make any customizations you'd like.

Our new flow now needs an email to send to customers!

This guide will explain how to add an email to this review request flow. You can design your email however you want, but it's important that you use the dynamic review link [[custom_event.order_review_url]] so that customers can seamlessly leave a verified review for the products they purchased.

If you're looking for review request email inspiration, we cover best practices here.

If you're interested in understanding how you can pull in other dynamic variables into an email from Omnisend, let us know!

We've just added Omnisend to your review flow in Junip and created a flow + email in Omnisend to send these messages. When you're ready to start sending review requests via Omnisend, you'll want to enable the workflow(s) in Omnisend.

You can check your Events Outbox in Junip to see which events are in queue and which have been sent. New orders will be added to the queue, then wait the time delay you set and send to Omnisend when they're ready. As events are sent to Omnisend, you should see them being added to the relevant flows.

If you've just moved to Junip, or spent some time setting up your Omnisend integration and missed requesting reviews from some customers, you can use a one-time campaign to request reviews from those customers.

This guide will explain how to send this campaign via Omnisend.