Activation Actions Parameters is a Beta release. For more information, contact your Customer Success Representative.
User-defined custom Workflows called by Activation Actions can refer to the information of the activation by using built-in parameters. The following table provides the activation's parameter details to help you integrate these effectively into your custom workflows and create robust post-processing actions.
| Parameter Name | Description | Example |
|---|---|---|
| segment_id | Unique identifier for the segment. | An integer value |
| segment_name | Name of the segment. | A string value |
| activation_id | Unique identifier for the activation. | An integer value |
| audience_id | Identifier for the audience involved in the activation. | An integer value |
| segment_folder_id | Identifier for the folder where the segment is stored. | An integer value |
| activation_actions_db | Name of the database that contains the table specified in parameter activation_actions_table. | "cdp_audience_x" where x is an integer value. |
| activation_actions_table | Name of the table that contains profiles to be activated in the nested user-defined workflow. | "cdp_syndication_x" where x is an integer value. |
| result_connection_name | Name used for the connector or authentication in the nested user-defined workflow. | A string value. For example, "my_s3_connection". |
| result_connection_settings | Configuration settings for the result connector, formatted in JSON. | {"bucket": "my_s3_bucket", "path": "/logs/"} |
| activation_session_id | Session identifier of the Activation workflow. Used internally for tracking and potentially metering. | A bigint number |
| activation_attempt_id | Attempt identifier of the Activation workflow. Used for internal tracking and potentially metering. | A bigint number |
| journey_id | Unique identifier for the journey. | An integer value |
| journey_activation_step_id | Unique identifier for the journey activation step. | An integer value |
The parameters of Activation Actions are used as variables of Workflow. Therefore, the following example of user-defined custom Workflow will display the parameters in the log.
+echo_activation_actions_parameters:
echo>: segment_id ==> ${segment_id}, segment_name ==> ${segment_name}, activation_id ==> ${activation_id}, audience_id ==> ${audience_id}You need to explicitly specify result setting to export the data.
+activation_actions_export:
td>:
query: "SELECT * from ${activation_actions_db}.${activation_actions_table}"
result_connection: ${result_connection_name}
result_settings:
${result_connection_settings}