First things first is authorizing Junip to send events to Omnisend. Make sure to enable all permissions with this API key.
The integration lives in our admin at "https://admin.juniphq.com/integrations".
Once you've added your Omnisend API key with all permissions enabled, we'll begin sending two events into Omnisend:
1. Junip - Order fulfilled
2. Junip - Order targeted by campaign
3. Junip - Review created
A list of template variables for these events can be found here.
Junip - Order fulfilled
This is used to fully manage the review request flow within Omnisend, 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 Omnisend as an event instead of sending the review request email from Junip.
Junip - Review created
Review created sends an event to Omnisend 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".
Creating a template
You'll utilize dynamic variable from the respective events we send when making a template for your review request emails or texts. This doc walks through how to leverage those variables to create a simple template (using email as the reference point), but can be used in SMS as well!
Making the switch
If you're already sending requests through Junip & switching to send through Omnisend, 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 Omnisend flow, then make up the missed customers with a campaign. If you have any questions on this just shoot us a message.