Overview
This node integrates with the Persio API to track user events, allowing you to record specific actions users perform within your application or website. It is particularly useful for analytics, marketing automation, and customer behavior tracking scenarios. For example, you can track when a user completes a purchase, clicks a button, or views a page, along with contextual information such as device details, campaign data, and user locale.
In the "Track" resource with the "Event" operation, the node sends an event name along with optional user ID, context, integrations, and custom properties to Persio's tracking endpoint.
Properties
| Name | Meaning |
|---|---|
| User ID | The identifier of the user performing the event. If not provided, an anonymous ID will be generated. |
| Event | The name of the action that the user has performed (required). |
| Context | Additional contextual information about the event, including: |
| - Active: Whether the user is active (boolean). | |
| - IP: Current user's IP address (string). | |
| - Locale: Locale string for the user, e.g., "en-US". | |
| - Page: Information about the current page (hash, path, referrer, search, title, URL). | |
| - Timezone: User timezone in tzdata format, e.g., "America/New_York". | |
| - App: Details 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 | Specifies which integrations to send the event to, options include: |
| - All (boolean) | |
| - Salesforce (boolean) | |
| Properties | Custom key-value pairs describing additional properties of the event. Multiple properties allowed. |
Output
The node outputs a JSON array containing the response(s) from the Persio API after sending the event data. Each item corresponds to one processed input item. The structure reflects the API's response to the tracking request.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Persio API.
- The node uses the
persioApiRequesthelper function to make HTTP POST requests to Persio endpoints. - No other external services or environment variables are explicitly required beyond the API key.
Troubleshooting
- Missing Required Fields: The "Event" property is mandatory. Omitting it will likely cause an error from the API.
- Invalid User ID or Context Data: Providing malformed or invalid context fields (e.g., incorrect timezone format) may result in API errors.
- API Authentication Errors: Ensure the API key credential is correctly configured and valid.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Persio API.
- Continue on Fail: If enabled, the node will continue processing remaining items even if some fail, returning error messages per failed item.
Links and References
- Persio API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Creating Custom Nodes