Omneo Invites

Omneo Invites is a refer-a-friend service. A profile in your incentive program (the referrer) enters a friend’s first name and email address. Omneo emails the friend (the invitee) a branded invitation. When the invitee joins, Omneo records who referred them on the new profile, and your Reactions issue incentives to the referrer, the invitee, or both. Referrers can also share a personal invite code instead of sending an email. A new customer who enters the code when they sign up is recorded as a referral in the same way.

​

What Invites does

1. Create. The referrer submits a friend’s name and email, from Profile Portal or from your own website. Omneo checks the referrer’s remaining quota and creates an invite in the PENDING state.
2. Email. Omneo sends the invitation through your SendGrid account using your dynamic template. The email carries the referrer’s first name, an optional personal message, the expiry date, and links to join, decline, or opt out.
3. Join. The invitee follows the link to your join page. The page pre-fills their email address from the link.
4. Accept. When the invitee registers, Omneo checks that the email matches the invitation, finds or creates the invitee’s profile, writes the referral to the profile as the custom attribute invites.invited_by (the referrer’s profile ID), applies any default statuses, and marks the invite ACCEPTED.
5. Reward. Your Reactions run on the new profile. Typical rules issue a Reward to the referrer when the invitee joins or completes a first Transaction.

Invites owns steps 1 to 4. Step 5 is standard Omneo automation, configured the same way as any other Reaction.

​

Where referrers send invites

Both surfaces can run side by side. A referrer’s quota is shared across them.

​

What the invitee experiences

• The invitation comes from your brand’s sender address, in your template, and includes the referrer’s first name and any personal message they wrote.
• The join link opens your join page with the invitee’s email pre-filled. The invitee completes registration as normal.
• If the invitee has pending invites from more than one referrer, the first invite accepted wins. Omneo marks the others DECLINED so only one referrer is credited.
• If the invitee registers with a different email address, the referral is not credited. The profile is still created.
• The email also carries a decline link and an opt-out link. Declining marks that one invite DECLINED. Opting out blocks all future invitations to that address and declines any pending ones.

​

Invite codes

An invite code is a profile’s personal referral code. The referrer shares it however they like, and a new customer enters it when they sign up. Omneo then records the referral on the new profile with the same invites.invited_by custom attribute an accepted email invite writes, so your referral Reactions apply to both. How codes work:

• One code per profile. A profile’s code is created the first time it is shown, and stays the same after that. Codes are eight characters and leave out characters that are easily confused, such as 0 and O. Case, spaces, and hyphens are ignored when a code is entered.
• The owner stays private. Checking a code says only whether it is valid, never whose it is.
• One referrer per profile. A profile that already has a referrer, from a code or an email invite, cannot be attributed to a second one. A profile cannot use its own code.
• Attribution follows sign-up. The referral is written after the new profile exists in Omneo, as an update to that profile.

​

Where codes are shown and entered

Invite codes are off by default. See Configuring Invites for what Omneo sets up.

​

Invite statuses

Expiry is enforced when an invitee tries to accept. An invite past its expires_at date is refused even while its status still reads PENDING. See Status lifecycle for how to handle this in your own UI.

​

Quotas and campaigns

Every invite belongs to an Invite Definition, which Omneo configures for your tenant. A definition sets: You can run a single definition for every profile, or map profile statuses to different definitions so that, for example, higher tiers receive more invites. Omneo can also set a per-profile override to raise or remove one referrer’s limit. Quota counts PENDING, ACCEPTED, DECLINED, and EXPIRED invites. Revoked invites do not count, so a referrer who cancels a stale invite gets that slot back.

​

Privacy and opt-out

Invites is designed so that a referrer cannot use it to discover whether an email address already belongs to your program. If the address has already accepted an invitation, the referrer still sees a normal pending invite in their list and no email is sent. Opt-out is permanent for that address. Later invites to it are refused, and Omneo can lift the block on request. Omneo can also block whole email domains for your tenant.

​

Referral incentives

Invites writes one fact to the invitee’s profile: the custom attribute invites.invited_by, whose value is the referrer’s profile ID. Everything else is standard Omneo automation:

• A Trigger on profile creation or first Transaction, conditioned on invites.invited_by being set, issues a Reward to the referrer. The action also writes invites.invited_by_name to the invitee’s profile for use in communications.
• The referrer’s profile carries a total_referred aggregation, the number of distinct profiles that name them in invites.invited_by. Use it for milestone incentives such as “refer five friends”.
• Welcome incentives for the invitee use the same Triggers as any other join.
• An invite code referral is written to a profile that already exists, so Omneo raises a profile update event rather than a profile creation event. A Trigger that only checks invites.invited_by on profile creation misses code referrals. Condition it on invites.invited_by changing from empty, or on the first Transaction.

See Program objectives for where referral programs fit in an acquisition strategy, and Custom attributes for how the referral is stored.

​

Administration

Omneo manages Invite Definitions, quota overrides, the opt-out list, and invite metrics on your behalf. Omneo support can look up any invite by its ID, which is why the integration guide recommends logging invite IDs against your own customer records. See Configuring Invites for who sets up each part, Integrating Omneo Invites for the developer guide, and the Invites API reference for every endpoint.