ID Synchronisation

Besides making identifiers available via fcData local storage, we also support server-side ID synchronisation with external systems using APIs.

Event-based Processing

For every incoming Trigger Event the Backend application does the following steps:

1. A new Trigger Event arrives and gets consumed.

2. UMID is extracted from the Trigger Event.

3. Database lookup is made so the Profile, Identifiers and any existing Synchronization entries are fetched.

4. All the Sync conditions have to be checked, in order to select the Identifiers ready for upload.

5. HTTP Requests to the Target Platforms are built on top of the selected Identifiers and Target Platforms configuration.

6. HTTP Requests are executed in parallel using the HTTP Client pool.

7. Once HTTP Requests are successful …

   1. the Trigger Event is marked as acknowledged.

   2. insert/update the synchronization_identifier and synchronization_profile table entries.

Multiple incoming Trigger Events can be processed at the same time.

Target Platforms

We support multiple external systems / Target Platforms.

Identifiers and their mapping can be configured as per client needs.