On this page, we will briefly explain the basic logic behind a Trigger in FT CRM.
⏲ Real-Time based Events
The triggers existing in the system are mainly based on real-time events that are sent to our API.
These triggers are reliant on the data being sent, from your system to us, in order to work.
Here is an example:
Below we have set up a trigger for any failed deposits of €100 or greater.
When an event that matches the above criteria is sent to our APIs, from your system, any active activity that has this specific trigger would then be triggered if the player exists in the segment.
🕒 Time Events
Time Events are the exception when it comes to Real-Time data events. This type of trigger is not based on any events/messages being sent from your system to our APIs.
It's simply triggered based on time.
When using a time trigger, pay close attention to the firing conditions of your activity. Always enable an activity at least 10 mins before the main time trigger is set to fire.
Example: The main trigger of your activity is set to fire at 13:00. Set the firing conditions to start at 12:50 and ensure that the activity has been QA'd and enabled in advance.
This allows for the system to have sufficient time to process the activity before it is scheduled to trigger.