Webhooks provide a way to push data, in real time, from one application to another. In the case of ProfileSync, Identity Cloud webhooks push data regarding user profile changes to ProfileSync; ProfileSync then transforms and repackages that data as needed and pushes it to the target API. As noted previously, all of this activity happens almost-instantly: when a profile is updated, Akamai immediately notifies ProfileSync, which immediately copies that data to the target API. As a result, your CRM database or your marketing database will almost-always be perfectly up-to-date.
Incidentally, this provides a major advantage over traditional API-based applications, where the application periodically polls the source database for changes. In a case like that, your target database will only be as up-to-date as your polling interval: if you poll once-an-hour for updates, then the target database could be as much as an hour out of date.
Note. In addition to that, constant polling – even if there are no changes to be retrieved – adds to network congestion and to server resource use.
Although Akamai will set up your webhooks for you, you need to determine such things as:
- The type of changes (e.g., profile creations, modifications, and deletions) to be reported.
- The fields to be copied from the Akamai user profile to the target API.
- The users for which data will be copied (e.g., all users; only the users who live in the US; only the users who don't live in the US; etc.).