When you integrate Junip with marketing platforms like Klaviyo or Postscript, we send events to those partners which allows you to send review messages through their platform. At the end of May 2022, we moved merchants to our new Flows experience to offer a better way to collect reviews and we also updated our event naming to better reflect these changes.
The bottom line:
You may have noticed different event names in different places between your dashboard and our help docs. That's because some users are using legacy event names while others are using our new event names. Whichever you're using, these are just differences in naming, the functionality will remain the same and you can continue to use Junip & our integrations seamlessly with either!
If you were using Junip before Flows...
We've moved you over to the new Flows experience but we kept your existing event names so that it wouldn't disrupt your integrations. You may not have noticed any discrepancies in naming, but if you did, it's probably because you're using our help docs and are seeing the new event names there. Functionality is the same so you can continue to use the help doc steps, just remember that your events have different names. You can refer to the table below to compare the legacy and new event names.
If you started with Junip after we released Flows...
You'll be using our new event names, which will match our help docs so you shouldn't have any issues!
Comparison of event names
Legacy event name
New event name
Junip - Order fulfilled
Junip - Review request
Junip - Review created
Junip - Review submitted
Junip - Order targeted by campaign
Junip - Review request by campaign
Junip - Incentive rewarded
This event info has been added to the "Junip - Review submitted" event
This event info used to be included in the "Junip - Review created" event
Junip - Review confirmation required
The biggest change here is whether or not you have a separate incentive event and confirmation event. New events have their incentive info included in the "Review submitted" event, while confirmation info has its own event. The info is the same, the only difference is naming and which event they're included in.
These updates are meant to make it even easier for brands to understand the events we are sending to integration platforms, but don't hesitate to reach out if you have any questions!
You might want to check out this guide to add integrations to your flows in Junip or the one that lists the different variables for each of these new events (if you're looking for variables for legacy events - that's here).