Actito aims at offering you a wide range of connectivity options in your marketing approach. Consequently, we particularly want to enable the exchange of data between Actito and other systems related to your activity.

Several solutions allow you to directly interact with Actito without having to go through the interface. Webservices already allow you to call data recorded in Actito and submit data to Actito.

The introduction of Webhooks gives you the reverse service in comparison to Webservices. It is no longer necessary to make a call every time you need a piece of information. Webhooks are in fact listening to the information. By subscribing to Webhooks, the latter allow you to be directly notified when specific events occur on a profile or a custom table entry. These events will be communicated to an URL that you will have to specify.

While this page gives useful additional business context regarding webhooks, the information to set-up webhooks may be outdated.

We invite you to consult the developer documentation for all technical matters: https://developers.actito.com/docs/integration-framework/webhooks/intro/


Affected events

Webhooks allow you to get notified about events revolving around profile tables and custom tables of the data model.

These events can be of the following nature:

  • CREATE: Allows you to get notified for each profile creation or each new data record

  • UPDATE: Allows you to get notified for each modification on a profile or data record. It is possible to specify exactly which field of the table must be taken into account

  • DELETE: Allows you to get notified every time a profile or a record is deleted

  • UPDATED_SEGMENT and UPDATED_SUBSCRIPTION: These events are specific to profile tables. They allow you to get notified for every subscription and segmentation modification

Good to know

For custom tables, events must be defined in the JSON definition file of the custom table (in the "tableEventDefinition" parameter).


When Actito records an event that matches the definition of the Webhook subscription, the Webhook will submit the information to the URL that you specified.

One call will be created for each event.


To receive notifications every time an event occurs in the table to which you are listening, it is necessary to create a subscription to a Webhook. A Webhook subscription must be created for each event and each table to which you are listening.

Creating and managing these subscriptions can be done through the Actito APIs. Their definition is available on the technical documentation, at the same place as every other API method:

The creation of a Webhook subscription and managing existing subscriptions is done in the 'Webhook Controller' category, no matter the type of table to which the Webhook is listening.