1. Loyalty Administration Guide
  2. Engagement Activity Push

Engagement Activity Push

CrowdTwist engagement activities are created in the CrowdTwist Control Center application. The CrowdTwist Widget supports Activity List, Survey, Poll, Quiz, Code Redemption and Social Contact. Customers can implement the following CrowdTwist engagement activities through either the Crowd Twist API or CrowdTwist Activity List Widget:

  • Surveys, Polls, and Quizzes

  • Social Connections (Facebook, Twitter, Pinterest)

  • Code Redemption

  • Custom Activities

When a member participates in a quiz, poll, or survey, or performs a social activity (such as a share, review, like or dislike of a post), CrowdTwist creates an engagement activity for this, and then pushes the data to Siebel Loyalty so that the member will be rewarded based on their participation in the quiz, poll, survey, or social activity. Depending on the type of engagement activity and the associated reward, a corresponding transaction is created and processed in Siebel Loyalty.

Engagement Activity Push Flow

As illustrated in the following image, the typical steps involved in the Engagement Activity Push (asynchronous flow) from CrowdTwist to Siebel Loyalty are as follows:

  1. When a member participates in a quiz, poll, or survey through either the Crowd Twist API or CrowdTwist Activity List Widget, CrowdTwist creates a Live Push User Activity to OIC.

  2. When OIC receives the Engagement Activity Push from CrowdTwist, it maps the CrowdTwist fields to Siebel fields.

    The Program Name, Product Name, and Point Name must be specified in the integration properties as follows:

    1. Log in to OIC (https://oicpmapdev-oicpm.integration.ocp.oraclecloud.com/ic/home) and deactivate the Oracle CT Siebel Loy ActivityPush integration.

    2. Edit the integration properties for Oracle CT Siebel Loy ActivityPush by entering the modified properties for (ProductName, ProgramName, PointName) and save.

    3. Reactivate the Oracle CT Siebel Loy ActivityPush integration.

    If OIC cannot connect to the Siebel Server, then an error is thrown and an email notification is sent. The OIC administrator must resubmit the flow once the Siebel Server is up and running again. When a transaction is successfully created for the Engagement Activity Push, no further operation is required.

  3. When Siebel receives the request from OIC, the Siebel endpoint ProcessExternalOrderTxn API is called and either an Accrual (where points are assigned to the member) or an Adjustment (where the points are redeemed from the member based on points sent) transaction is created.

    If successful, transaction processing returns a status of processed, otherwise a status of rejected.


Engagement Activity Push Flow: This image is described in the surrounding text.

Troubleshooting Engagement Activity Failure

If the OIC flow throws a 500 error, then do the following:

  1. Check that the email notification has been sent to the OIC administrator.

  2. Ensure that the Siebel Server is up and running.

  3. Resubmit the OIC instance to call the Siebel endpoint again.

If a transaction is created but has a Rejected status, then do the following:

  1. Check the processing information and review the details of the processing error.

  2. Correct the error shown in the processing information, and resubmit the transaction for processing.

Handling Engagement Activity Push with Negative Points

In a scenario where CrowdTwist rolls back an engagement activity, it will send the Engagement Activity Push to Siebel Loyalty with negative points. When negative points are pushed from CrowdTwist for adjustment, a Redemption - Manual Debit transaction created in Siebel Loyalty will deduct the points from the member's point balance. This is possible if a Loan is set up for the member to allow a points overdraft in case the member does not have sufficient points to adjust against such a negative point adjustment. If not, then the transaction will be rejected and an "insufficient point balance error" will be returned.