Member Synchronization Flow

As illustrated in the following image, the typical steps involved in synchronizing member enrollment data between Siebel Loyalty and CrowdTwist are as follows:

1. When a member is enrolled or updated in Siebel Loyalty, the appropriate Synchronization Workflow is invoked and the data is sent to Oracle Integration Cloud (OIC).

   • If Siebel cannot connect to OIC, then review the CT Sync Status and Error Attributes of the Member Object, which will show the appropriate error.

   • If a member contains the CT Sync Error/Status, then the administrator must take appropriate action to correct the error and update the member data.

2. OIC sends the member data (OIC Member Sync Flow) to CrowdTwist.

   • If OIC integration cannot connect to the CrowdTwist server, then the OIC instance returns an error. The OIC administrator must resubmit the flow once the CrowdTwist server is up and running again.

   • If CrowdTwist returns a valid data error, the same is updated on the Siebel member's CT Sync Error/Status Attributes.

3. In CrowdTwist, the member is created or updated through one of the following CrowdTwist REST APIs. The member's Third Party ID in CrowdTwist corresponds to the member's Member Number is Siebel Loyalty.

   • CrowdTwist User Create - for more information, see https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-develop/Developers/UserCreate.html.

     Note: CrowdTwist Batch User Create is also available for batch member synchronization - for more information, see https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-develop/Developers/BatchUserCreate.html. This API is used during initial data load to create or update member data.

   • CrowdTwist User Update - for more information, see https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-develop/Developers/UserUpdate.html.

     If an enrolled member's data changes in Siebel, then the corresponding member record in CrowdTwist is updated via OIC using a CrowdTwist User Update REST API call. This API call is also used to update member data during incremental data load.

Troubleshooting Member Synchronization to CrowdTwist

If a member created or updated in Siebel Loyalty is not synched to CrowdTwist, then do the following:

1. Check the Member Attributes CT Sync Status and CT Sync Error to identify the failed operation and error.

2. If there is a Data Error (for example: Email Address is already taken), then correct the error (for example: Update, correct, or provide an alternate email address).

3. If the CT Sync Status state is OIC Failure, then ensure that the OIC connection is working and that the integration is active. Update the member to re-trigger the synchronization flow.

4. If the CT Sync Status state is CT Failure, then check the OIC CT connection (Oracle CrowdTwistRest Connection) and ensure that it is working. Resubmit the OIC instance to re-trigger the synchronization flow.

5. In case of data discrepancy between Siebel Loyalty and CrowdTwist or if you receive any OIC Error Email notification, review the corresponding OIC instance to analyze the issue and take appropriate action.