Creating an action: Oracle Unity destination

Actions are configured in three steps:

  1. Basic Details: You’ll provide a name and description for your action so that it is easily recognized. Learn more about the Basic Details step.
  2. Rules: You’ll define the behaviors and filters that make up the rules you want to listen for in real-time. Learn more about the Rules step.
  3. Destinations: You’ll select the specific data you want to send and to which action system you want to send it.


  • You must have configured the first two screens on the Create Actions page.
  • Before you can create an action, you must be assigned a role that includes the Manage Actions user right.
  • A connection must be configured and enabled. When creating an action, you will be required to select an enabled connection and destination before you can save.

To configure an Unity destination for an action:

  1. Follow the the Basic Details and Rules screens.
  2. On the Destination screen, select a connection to Oracle Unity.

    Note: If you haven’t yet created a connection, or if your connection is not enabled, you will not be able to continue.

  3. Select the Destination Type for the connection you selected in the previous step. For Oracle Unity connections, the Destination Type corresponds to the Unity data object you want to set up the Action for.
  4. Select a Destination.
  5. Under Field Mapping, select and map the Infinity data you want to send to the fields in your selected destination. Attributes that are marked as Required in the Destination settings will be automatically added for field mapping.

    Tip: If you don't see a parameter, navigate to Settings and check the Analytics and Actions option to include the parameter in Actions.

    An image of the field mapping section

    1. Under the Infinity Data column, select the Behavior Attributes or Parameters you want to map to your destination fields.

      Tip: You can choose behavior attributes for the behaviors you included in the Rules screen. For example, if you choose to include the View Form and Submit Form behaviors, you will see them here, and you can choose from a set of behavior attributes, such as Form Name.
      You can also choose from your set of parameters.

    2. (Optional) If you're selecting a Parameter, you can select the occurrence of the parameter in the session:
      • Any occurrence in session: Sends all the data in an array format to the destination field.
      • Note: If the destination field doesn’t expect an array, select First occurrence in session or Last occurrence in session.

      • First occurrence in session: Sends only the first value in that session.
      • Last occurrence in session: Sends only the last value in that session.

  6. Click Save.

    When an action is saved, by default it is disabled. The action will not begin to run until it is enabled. Learn how to enable an action.

When an action is saved, by default it is disabled. The action will not begin to run until it is enabled. Learn how to enable an action.

Error retries

If any error is returned from the destination when sending data, the action will try to resend the data after one minute and then retry in intervals that double the time for subsequent retries. Retries will continue until five attempts is reached. After five attempts, the event will stop retrying and the action will continue to send all events that occurred following that event.

If errors persist for an action, you can access the History tab to review errors that may require your attention. For example, a password change may require an update to the authentication fields for the action. Once an event has been sent successfully after a retry, the error status will clear from the action.

Learn more

Standard behaviors

An overview of Actions

Accessing actions

Enabling an action

Disabling an action

Editing an action

Deleting an action