Omnisend Loyalty and Reviews Integration

Connect Omnisend with an API key and Reorbit’s loyalty and review events become triggers for your Omnisend automations — email, SMS or push.

⛔ The first event Reorbit sends does not trigger anything. Omnisend only lets you build an automation for an event it has already seen, so send one first, then build.

---

What is the Omnisend integration?

Reorbit decides who to message and when — someone joined your programme, a review request is due, points are waiting. Omnisend sends the message. Reorbit passes each moment to Omnisend as a custom event with everything the message needs (points balance, products, review links), and you build the automation in Omnisend that turns it into an email or text.

It is an alternative to Klaviyo, not an addition to it. You can connect both, and choose per message which one sends.

---

Before you start

• An Omnisend account.
• An Omnisend API key with the brands.read and events.write permissions. Reorbit checks the key when you connect, but it can only confirm brands.read: a key without events.write connects, and then Omnisend refuses every event. Tick both.

---

Step-by-step: connect Omnisend

1. Create the key in Omnisend

In Omnisend, go to Store settings → API keys → Create API key. Give it a name you will recognise later (for example, Reorbit), tick brands.read and events.write, and copy the key.

Installed Reorbit from the Omnisend App Market? Use the key it gives you and go straight to step 2.

2. Paste it into Reorbit

In Reorbit, go to Settings → Integrations. In the Omnisend section, paste the key and click Connect.

Reorbit checks the key with Omnisend before saving it, so if it succeeds you will see Connected to your brand name and the last four characters of the key. If Omnisend rejects the key, nothing is saved and Reorbit says so.

3. Choose which messages send through Omnisend

Connecting does not move any message on its own. Go to Settings → Automated messages, open a message, and under Delivery choose Omnisend, then save.

⏰ This takes effect on the next nightly run — if you save late in the day, the following night. Messages already prepared go out on the channel they were prepared with. Changing the channel does not switch a message on: a message that is off stays off.

4. Let one message send, then build the automation

Omnisend will not offer an event in its automation builder until it has seen that event at least once. The first message Reorbit sends therefore reaches Omnisend and triggers nothing — which is expected, not a fault.

After that first send, go to Omnisend → Automations → Create automation → Custom event, pick the Reorbit event, and build the email or SMS. From then on, every send triggers it.

---

The events Reorbit sends

Event in Omnisend	Sent when	Timing
Reorbit Sparks - Loyalty Welcome	Someone joins your loyalty programme	Nightly
Reorbit Sparks - Loyalty Points Reminder	A member has points sitting unused	Nightly
Reorbit Sparks - Review Request	It is time to ask for a review	Nightly
Reorbit Sparks - Review Reminder	A review request went unanswered	Nightly
Reorbit Sparks - Repeat Replenishment	A customer is due to reorder	Nightly · off by default
Reorbit Sparks - Repeat Cross Sell	A customer is a good fit for a related product	Nightly · off by default
Reorbit Sparks - Repeat About to Lapse	A regular customer has gone quiet	Nightly · off by default
Reorbit Sparks - Repeat Subscription Upsell	A repeat buyer is a good fit for a subscription	Nightly · off by default
Reorbit Referrals - Referral Claimed	A friend claims a referral link	Immediately
Reorbit Referrals - Referral Completed	A referred friend’s order pays out the reward	Immediately
Reorbit Referrals - Referral Shared	A shopper invites a friend by email from your storefront	Immediately

Nightly events are chosen once a night, so a message you switch on today sends from the next run. The four marked off by default are under Settings → Automated messages → Marketing messages and send nothing until you turn them on. Referral events go out the moment they happen.

Marketing consent

Only the four marketing events — Repeat Replenishment, Repeat Cross Sell, Repeat About to Lapse and Repeat Subscription Upsell — are limited to customers whose email marketing status in Shopify is Subscribed. Review, loyalty and referral events are about an order, a programme the customer joined or a referral, not marketing, so they are sent whatever the customer’s marketing consent.

Reorbit never sends a subscription or consent status to Omnisend. Each event creates or updates the contact with the email address and the loyalty properties below, and nothing else, so the contact’s email and SMS subscription status stays whatever Omnisend already holds. Whether a message reaches a contact who is not subscribed is decided in Omnisend, by your automation and the contact’s status.

⚠️ Referral Shared goes to someone who has not opted in to anything. A shopper typed the friend’s address into your storefront. Build its automation as a single email that answers the invitation, and don’t add those contacts to a list or a marketing flow.

What each event carries

Every property below appears in Omnisend’s automation builder once the event has been received. Reorbit declares each property’s type to Omnisend from the first value it sends: whole numbers as numbers, and dates sent as ISO text (such as occurredAt) as dates.

Property	On	What’s in it
sparkType	Every Sparks event	Which message this is, e.g. reviews_reviewRequest
occurredAt	Every Sparks event	When Reorbit chose this moment
products, productCount	Every Sparks event (empty for loyalty ones)	The products the message is about. Each has title, imageUrl, productUrl, price, variantTitle, sku
reviewUrl, ratingUrls	Each product, on Review Request and Review Reminder	A signed link to the review form, and the same link pre-rated per star (ratingUrls keys 1–5). Valid for 180 days
orderId, orderNumber, orderCount, customerId	Review Request and Review Reminder	The order being asked about. If orderCount is more than 1, the ask covers several orders — don’t write “your order #1042”
customerId, pointsBalance, joinedAt, daysSinceJoining	Loyalty Welcome	The balance they start with and when they joined
customerId, pointsBalance, lastActivityAt, daysInactive	Loyalty Points Reminder	The balance waiting and how long they’ve been quiet
referralId, discountCode, receiverEmail, advocateCode, expiresAt	Referral Claimed	The friend’s discount code, their email, the advocate’s referral code and when the code expires
referralId, discountCode, rewardTitle, rewardValue, rewardType, expiresAt, refereeEmail, advocateCode	Referral Completed	The reward the advocate earned and its code. Sent to the advocate; refereeEmail is the friend
shareId, receiverEmail, advocateName, advocateCode, referralLink, note, refereeRewardDescription	Referral Shared	Who invited them, their link, the reward on offer, and the advocate’s note if they wrote one

What Reorbit writes on the contact

Every Sparks event, and Referral Completed (on the advocate), also updates the Omnisend contact with the customer’s loyalty standing. Referral Claimed and Referral Shared do not — the friend may not be a customer yet. Use these for segments and conditions — “points balance over 500”, “in the Gold tier”:

Contact property	What’s in it
loyaltyPointsBalance	Points available now
loyaltyLifetimePointsEarned, loyaltyLifetimePointsSpent	Totals since they joined
loyaltyRewardsAvailableCount	How many rewards they can redeem right now
loyaltyDiscountsUnredeemed	The rewards they hold and haven’t used yet — each with rewardId, title, code, type, value and expiresAt (a timestamp in milliseconds)
loyaltyTierEntryActive, loyaltyTierEntryActiveSlug, loyaltyTierEntryDate	Their current VIP tier and when they reached it

Referral messages are the exception to step 3: they have no channel setting. They go to every provider you have connected, automatically. Referral Claimed and Referral Completed each have an on/off switch under Settings → Automated messages; Referral Shared is sent whenever your referral programme is active.

---

Managing the connection

• Test connection re-checks your key with Omnisend and updates what the card says.
• Replace key stores a new key. Use it when you rotate keys in Omnisend or reinstall Reorbit from the Omnisend App Market. Your message settings — which messages are on, and where each one sends — stay as they were.
• Disconnect deletes your stored key. Events stop reaching Omnisend, and any message set to send through it stops going out until you connect again. The key itself stays valid in Omnisend — delete it there too if you do not want it used. Your message settings are kept for when you reconnect.

Test connection tells you when something is wrong. Reorbit does not re-check your key on its own, so if events stop arriving in Omnisend, start there:

• “Omnisend is rejecting this key” — the key was deleted or is missing a permission. Create a new one and paste it in with Replace key. Events Omnisend refused while the key was rejected are not sent again.
• “We couldn’t reach Omnisend on the last check” — this says nothing about your key. Omnisend may simply have been busy; events keep being sent and a failed one is retried.

---

Tips & best practices

• Connect before you switch a message over. The Omnisend option stays disabled until a key is stored.
• Do the first send on a quiet message so the registration send lands somewhere harmless.
• The fastest way to see an event arrive is a referral. Open a referral link as a friend and claim it: Reorbit Referrals - Referral Claimed reaches Omnisend immediately, where every other event waits for the nightly run.
• Keep one key for Reorbit. The last four characters shown in Reorbit tell you which key it is, which matters when you rotate.
• You can run Klaviyo and Omnisend side by side while you migrate, one message at a time.

---

FAQ

Does connecting Omnisend move my messages off Klaviyo? No. Connecting only stores the key, and each message keeps sending where it sent before until you change its Delivery setting.

Why did my first message not trigger my automation? Omnisend does not offer an event in the automation builder until it has received it once, so the first send registers the event — build the automation after it, and the next send triggers it.

Can Reorbit send SMS through Omnisend? Reorbit sends the event and your automation decides what to do with it, which can be email, SMS or push, as long as the contact has the relevant consent in Omnisend.

Can I see my key again later? No — Reorbit stores it encrypted and never shows it again, only the last four characters, so to change it you paste a new key.

I changed a message to Omnisend and nothing happened that evening. The change reaches the sending pipeline on the next nightly run and anything already prepared goes out on its old channel, so check again after the following run, and check the message itself is switched on.

Does Reorbit subscribe my customers in Omnisend? No. Reorbit never sends a subscription or consent status, so it never subscribes anyone. Each event creates or updates the contact with the email address and Reorbit’s loyalty properties only. The four marketing events are sent only for customers subscribed to email marketing in Shopify; review, loyalty and referral events are sent regardless of marketing consent.

I replaced my key. Do I need to set up my messages again? No. Replace key changes only the stored key; which messages are on and where each one sends stay as they were, and new events use the new key within about a minute.

---

Next steps

• Next: How Review Requests Work — the message most stores start with.
• Related: Connecting Integrations · Setting up retention triggers · Referral messages