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
Event Delivery → Get Destination Event Delivery Trend
AI-generatedOverview
This node interacts with the Commanders Act API to retrieve the delivery status history of a specific event delivery destination over a given period. It is useful for monitoring and analyzing trends in event delivery performance, helping users identify patterns or issues in event processing.
Use Case Examples
- A marketing analyst wants to track the trend of event deliveries to a particular destination to ensure data is being sent correctly over time.
- A system administrator monitors the delivery trends to detect any degradation or improvement in event delivery success rates.
Properties
| Name | Meaning |
|---|---|
| Event Delivery ID | The unique identifier of the event delivery destination for which the delivery trend is requested. |
| Query Parameters | Optional parameters to filter or customize the API request, such as date ranges, filters, granularity, pagination, sorting, and other specific query options. |
Output
JSON
deliveryTrendData- The delivery status history data for the specified event delivery destination over the requested period.
Dependencies
- Commanders Act API with API token credentials
Troubleshooting
- Ensure the Event Delivery ID is provided; otherwise, the node will throw an error indicating the missing ID.
- Verify that the API credentials (site ID and token) are correctly configured and valid to avoid authentication errors.
- Check the format and validity of query parameters to prevent API request failures.
- Common error messages include missing required parameters or authentication failures; resolving these involves providing the necessary IDs and valid credentials.
Links
- Commanders Act API Documentation - Official API documentation for Commanders Act, useful for understanding available endpoints and parameters.