AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation, "Get Retrieve Event Stats" under the "Ad Audit" resource, is designed to fetch event statistics related to advertising audits. It allows users to retrieve detailed analytics or logs about ad events by specifying user identification and optional query parameters to filter, sort, or limit the data returned.

Common scenarios where this node would be beneficial include:

  • Monitoring ad campaign performance by retrieving event stats filtered by specific conditions.
  • Auditing user interactions or system events related to advertisements.
  • Extracting subsets of event data for reporting or further processing in workflows.

For example, a marketing analyst could use this node to pull event stats for a particular user ID, applying filters to only get recent events or ordering them by date.

Properties

Name Meaning
X USER ID The User ID required to identify which user's event stats to retrieve.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A query condition/filter string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The output JSON contains the retrieved event statistics matching the specified user ID and any additional query parameters. The structure typically includes an array of event objects with their respective details such as timestamps, event types, counts, or other relevant metrics depending on the API's response schema.

If the node supports binary data output, it would represent raw or processed event data files; however, based on the provided code and properties, the primary output is JSON-formatted event statistics.

Dependencies

  • Requires an API key credential for authentication to the external service providing the ad audit event stats.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the external API endpoint that supports querying event stats with headers and query parameters as specified.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors or empty responses. Validate query syntax and parameter values.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify network access and credential settings.
  • Rate limiting or permission errors: If the API enforces rate limits or requires specific permissions, exceeding limits or lacking rights may cause errors. Check API usage policies and credentials.

Links and References

  • Refer to the external API documentation for the Ad Audit service to understand supported query parameters and response formats.
  • n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.

Discussion