AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation, Get Retrieve User Enabled Stats under the Ad Audit resource, is designed to fetch statistics related to user-enabled features or activities in an advertising audit context. It allows users to retrieve detailed data about what features or settings a specific user has enabled, which can be useful for auditing, monitoring user behavior, or generating reports on user activity within an ad platform.

Practical scenarios include:

  • Auditing user permissions or feature usage in an advertising system.
  • Generating reports on user engagement with certain ad audit features.
  • Monitoring compliance or configuration states per user.

Properties

Name Meaning
X USER ID The unique identifier of the user whose enabled stats are being retrieved.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A filter condition to narrow down results.
- 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 of this node operation is JSON data containing the retrieved user-enabled statistics. The structure typically includes fields representing various enabled features or settings associated with the specified user, along with metadata such as timestamps or counts depending on the API response.

If binary data were involved (not indicated here), it would represent files or media related to the audit, but this operation focuses on JSON-formatted statistical data.

Dependencies

  • Requires an API key credential for authentication to the external service providing the Ad Audit data.
  • The base URL and authentication details must be configured in the node credentials.
  • The node uses HTTP headers to pass the user ID (X-USER-ID) and supports additional query parameters sent as URL queries.

Troubleshooting

  • Missing or invalid X USER ID: The request will fail if the user ID is not provided or incorrect. Ensure the user ID is valid and correctly set.
  • API authentication errors: Verify that the API key or authentication token is correctly configured in the node credentials.
  • Query parameter issues: Invalid values for skip, limit, or order_by may cause errors or unexpected results. Use appropriate types and valid field names.
  • Empty or no data returned: This might indicate no enabled stats exist for the given user or the condition filters out all data. Adjust query parameters accordingly.

Links and References

  • Refer to the external API documentation of the Ad Audit service for detailed information on available query parameters and response schema.
  • n8n documentation on how to configure API credentials and use HTTP header and query parameters in nodes.

Discussion