Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Web Container Actions
- Get Web Tag
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Mix Collect Redirect Rule → Update Redirect Rule
AI-generatedOverview
This node operation updates an existing Mix Collect Redirect Rule in the Commanders Act platform. It is useful for modifying redirect rules that control how users are redirected based on specific criteria in the Mix Collect system. For example, a user can update the URL or conditions of a redirect rule to change the behavior of web traffic redirection.
Use Case Examples
- Updating a redirect rule to change the target URL for a specific campaign.
- Modifying the conditions under which a redirect rule applies to better segment user traffic.
Properties
| Name | Meaning |
|---|---|
| Redirect Rule ID | The unique identifier of the redirect rule to update. Required to specify which redirect rule to modify. |
| Query Parameters | Optional query parameters to filter or modify the request. Includes various filters like date ranges, status, and other attributes relevant to the redirect rules. |
| Request Body | The JSON object containing the updated data for the redirect rule. This is the main payload that defines the changes to be applied to the redirect rule. |
Output
JSON
json- The JSON response from the Commanders Act API representing the updated redirect rule or the result of the update operation.
Dependencies
- Commanders Act API credentials (siteId and tokenAPI)
Troubleshooting
- Ensure the Redirect Rule ID is provided; otherwise, the node will throw an error indicating the ID is required.
- Verify that the API credentials are correctly set up and valid to avoid authentication errors.
- Check the structure and content of the Request Body JSON to ensure it matches the API's expected format to prevent request failures.
- If the API returns an error, the node will throw a NodeApiError with details; review the error message and stack trace for troubleshooting.