issue-ecert.
Flow
- Omneo issues a Benefit to a Profile, for example through a Reaction, a tier attainment or a manual issue in CX Manager.
- Omneo sends the
benefit.createdevent to the extension. - If the Benefit Definition carries the tag
issue-ecert, the extension orders an eCert from Givex for the Profile. Benefits from any other definition are ignored. - Givex emails the eCert to the Profile’s email address.
- Omneo stores the Givex card number on the Benefit.
Benefit Definition requirements
A Benefit whose definition lacks
value or period is not sent to Givex.
What Omneo records on the Benefit
Your POS and eCommerce platforms read these redeem codes to apply the eCert at checkout, in the same way as any other Benefit with redeem codes.
After the eCert is issued
An eCert is ordered once, when the Benefit is created. Omneo sendsbenefit.updated events to the extension as well, but it accepts them without acting, so editing a Benefit in Omneo after issuance does not reissue or change the Givex eCert. To put a new eCert in a Profile’s hands, issue a new Benefit.
Sender details
The eCert names your brand as the sender using theissuer_name and issuer_email settings. See Setup.
When an eCert cannot be ordered
If Givex does not accept the order, the Benefit stays on the Profile without redeem codes and Omneo does not retry. A Benefit from anissue-ecert definition that still has no external_id a few minutes after issue is the sign to look for. Contact Omneo support with the Benefit ID.