Overview
This node integrates with the Persio API to track user page views within an application or website. Specifically, the "Track" resource with the "Page" operation allows you to record when a user visits a particular page, along with rich contextual information about the user, device, campaign, and app environment.
Common scenarios for this node include:
- Monitoring user navigation through different pages of a web or mobile app.
- Analyzing user engagement by tagging specific pages like "Signup", "Checkout", or "Pricing".
- Enriching analytics data with detailed context such as device info, campaign source, and timezone.
- Feeding page view events into marketing automation or CRM systems via integrations.
For example, you could use this node to send a "page view" event every time a user lands on your signup page, including their locale, device type, and campaign details, enabling targeted follow-up campaigns.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose page view is being tracked. If not provided, an anonymous ID will be generated automatically. |
| Name | The name of the page being viewed (e.g., "Signup"). This helps identify which page the event corresponds to. |
| Context | Additional contextual information about the page view event, including: - Active (boolean): Whether the user is currently active. - IP: User's IP address. - Locale: User's locale string (e.g., en-US). - Page: Dictionary with page details like hash, path, referrer, search, title, URL. - Timezone: User's timezone in tzdata format (e.g., America/New_York). - App: Information about the app (name, version, build). - Campaign: Marketing campaign details (name, source, medium, term, content). - Device: Device details (id, manufacturer, model, name, type, version). |
| Integration | Controls which integrations receive the event data. Options include: - All (boolean): Send to all integrations. - Salesforce (boolean): Send specifically to Salesforce integration. |
| Properties | Custom key-value pairs to add additional properties to the page event. Multiple properties can be added, each with a key and value string. |
Output
The node outputs a JSON array where each element corresponds to the response from the Persio API for the page tracking event sent.
The structure of each output item includes the data returned by the Persio API after successfully recording the page event. This typically contains confirmation details of the tracked event.
No binary data is produced by this node.
Dependencies
- Requires an API authentication token credential for the Persio API.
- The node calls the Persio API endpoints using HTTP POST requests to
/page. - No other external dependencies are required beyond standard HTTP connectivity.
Troubleshooting
- Missing User ID: If no User ID is provided, the node generates an anonymous UUID. Ensure this behavior aligns with your tracking requirements.
- Invalid Context Fields: Providing malformed or incomplete context objects (e.g., invalid timezone strings) may cause API errors.
- API Authentication Errors: Ensure the API key credential is correctly configured and has permissions to send tracking data.
- Network Issues: Connectivity problems to the Persio API endpoint will cause request failures.
- Error Handling: If the node is set to continue on failure, errors will be included in the output array; otherwise, execution stops on the first error.
Links and References
- Persio API Documentation (for detailed API usage and schema)
- n8n Documentation (for general node usage and credential setup)