ProfileSync "extends Akamai's Identity Cloud with reverse API calls to back-end systems." That's a complicated-sounding definition for a what turns out to be a fairly simple concept: when notified that an Akamai user profile has been created, modified, or deleted, ProfileSync can use API calls to replicate those changes to a CRM, a DMP, or just about any other system that has a public-facing API, message queue, or file server. To name just a few of these "target APIs," ProfileSync has been successfully used with:
- Microsoft Dynamics
- Oracle Responsys
And that's not all. By using webhooks (a standard technology for pushing data from one application to another), data transfers can happen in real-time. As soon as a user updates his or her user profile, an Akamai webhook can notify ProfileSync that a change has taken place. In turn, ProfileSync can identify the nature of the change, then replicate that change to the target API. For example, if Bob Jones registers on your web site, an activity that results in a new user profile, ProfileSync can immediately create a corresponding Salesforce user profile for Bob Jones. And before you ask, yes, this is very secure: all ProfileSync activity takes place over a secure connection, using either an API secret or an OAuth access token.
In other words, ProfileSync: can
- Call the API of customer’s back-end system; for example, ProfileSync can call Salesforce APIs or Microsoft Dynamics APIs, and use those APIs to update user data.
- Be triggered by a webhook notification. However, notifications can also come from a CORS-enabled API. CORS (cross-origin resource sharing) is a technology that allows resources from one domain to be used in another domain.
If you don't want or don't need real-time notifications, ProfileSync can also be configured to periodically poll Akamai for user profile changes.
- Push registrations, profile updates, and forget-me's (account deletions) to the target API.
- Provider organizations with custom filtering, field mapping, and conversion and translation rules.
- Implement data throttling to ensure reliable data delivery. This involves intentionally slowing down a transmission in order to minimize network congestion.
- Potentially, update a user profile by interpreting the returned API result. Typically, ProfileSync is a one-way transmission mechanism: changes made to a user profile are transmitted to the target API, but changes made in the target API are not replicated to the Akamai user profile. However, ProfileSync can be configured to make at least someuser profile updates based on the response returned when ProfileSync calls a backend API.
For more information, see Appendix A: ProfileSync Capabilities.