Content of this article
- Preliminary Remarks
- Overview of Possible Events (Callback Types)
- Notes On Data Protection
1. Preliminary Remarks
Callbacks enable to transmit information on defined events in the plenigo system to other systems basically in real time.
When integrating plenigo, it may be desirable for third-party systems to receive information about events that occur in the plenigo system so that these systems can perform actions accordingly.
For this purpose, certain events, so-called callbacks, can be defined in the Merchant Backend.
Examples for events:
- The creation of a customer in plenig should automatically be transmitted to a customer data hub.
- Changes on opt-in settings in plenigo should automatically be transmitted to a marketing tool.
- The information on the cancellation of a subscription should automatically be transmitted to a newsletter dispatch tool.
2. Overview of Possible Events (Callback Types)
In the Merchant Backend plenigo provides various callback types for events. The selection is constantly extended.
If an event occurs, plenigo generates a new event object. An individual order via the plenigo Checkout, for example, can lead to several events:
- Creation of a customer account
- Creation of an order
- Creation of a subscription
- Creation of an invoice
For each event, a callback can be created. Several events can also be combined in one callback.
3. Notes On Data Protection
When most callback types are used, personal data is transmitted. The receiving system can therefore be defined as an additional data processor under current legislation. This should always be taken into account when using callbacks.