Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Business Feature / Process | Description | Example / use case | Empasis in training material | Additional notes |
---|
Customer events | Support for Purchase, achievement, referral events Customer identification based on contact id, contact code, CIM, gift card number, OTP
| | | |
Purchase Events | Captures the purchase basket in full, total amounts and SKUs. If SKUs do not exist in CRM.COM then they are created Captures organisation that submitted the event by matching to organisation id or transaction acquire points Support for multi-currency, if purchase in other currency then purchase event converted to business currency Purchase event classification. If submitted and does not exist then classification is created Net, total and tax amount handling. Support to input or be calculated Two spend models. Payout driven and POS driven Optional spend request. Ability to specify that the spend is successful only if enough funds to cover the purchase
| | Y | |
Transaction processor purchase events | Transaction processor submitting events and routed to all businesses with the same transaction access points (terminals) Transaction matching mode where purchase is matched to one submitted by the POS Transaction claim mode where customer claims the already submitted purchase via a self service API
| | | |
Purchase estimates | | | | |
Achievement event | | | | |
Referral event | | | | |
Event utilities | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
Notes:
Exercise for Contacts
Describe the various methods for identifying a contact when submitting a purchase event