AvantGuard - PXL icon

AvantGuard - PXL

AvantGuard - PXL

Actions5

Overview

The node integrates with the AvantGuard PXL API to retrieve analytics insights about links and domains. Specifically, the "List Insight" operation fetches detailed analytics data filtered by various optional parameters such as date range, device type, browser, location, and traffic source.

This node is useful for marketers, analysts, or developers who want to programmatically access link performance metrics and user engagement data. For example, it can be used to generate reports on how many clicks a specific shortened link received over the past week, broken down by country or device type.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the insight data returned. Includes:
- Date From Start date (YYYY-MM-DD) for the data range; defaults to 7 days before current date.
- Date To End date (YYYY-MM-DD) for the data range; defaults to current date.
- Timezone Timezone offset for returned data; defaults to UTC.
- Link Specific shortened link to get analytics for (e.g., pxl.to/mylink).
- Domain Specific domain to filter analytics (e.g., pxl.to).
- Device Device type filter (e.g., Desktop).
- Browser Browser filter (e.g., Chrome).
- OS Operating system filter (e.g., Windows).
- Country Country filter using ISO 3166 2-digit code (e.g., US).
- City City filter (e.g., Washington).
- Medium Traffic medium filter (e.g., Click).
- Source Traffic source filter (e.g., footer).

These parameters allow fine-grained control over which analytics data is retrieved.

Output

The node outputs JSON data containing the analytics insights matching the specified query parameters. The structure typically includes metrics such as click counts, timestamps, device/browser breakdowns, geographic distribution, and other relevant statistics provided by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard PXL API.
  • The base URL for API requests is https://api.pxl.to/api.
  • The node uses standard HTTP headers accepting and sending JSON content.

Troubleshooting

  • Invalid or missing API credentials: Ensure that a valid API key credential is configured in n8n for this node.
  • Incorrect date formats: Dates must be in YYYY-MM-DD format; otherwise, the API may reject the request.
  • Empty or no data returned: Check that the query parameters are correct and that there is data available for the specified filters and date range.
  • Network or API errors: Verify network connectivity and that the API endpoint is reachable.
  • Unsupported filter values: Using invalid device, browser, or location names might result in empty responses or errors.

Links and References

Discussion