Overview
This node integrates with the Persio API to identify users by associating traits and context information with a user ID or an anonymous ID. The "Identify: Create" operation allows you to send detailed user profile data, including traits (custom key-value pairs) and contextual metadata such as device info, app details, campaign data, and more. This is useful for personalizing user experiences, tracking user attributes over time, or syncing user profiles across systems.
Practical examples:
- Enriching a user profile with demographic or behavioral traits.
- Sending device and app context to better understand user environment.
- Associating marketing campaign data with a user for attribution analysis.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to identify. If not provided, an anonymous ID will be generated automatically. |
| Traits | A collection of custom key-value pairs representing user attributes or properties. For example, "age": "30", "subscriptionLevel": "premium". |
| Context | Metadata about the user's current environment, including: - Active (boolean): Whether the user is active. - IP (string): User's IP address. - Locale (string): Locale string like "en-US". - Page (string): Info about the current page. - Timezone (string): Timezone in tzdata format, e.g., "America/New_York". - App: Details about the app (name, version, build). - Campaign: Marketing campaign info (name, source, medium, term, content). - Device: Device details (id, manufacturer, model, name, type, version). |
| Integration | Specifies which integrations should receive this identify call. Options include sending to all integrations or selectively to specific ones like Salesforce. |
Output
The node outputs an array of JSON objects representing the response from the Persio API after creating the identify record. The exact structure depends on the API response but generally includes confirmation of the identified user and any metadata returned by Persio.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Persio API.
- The node uses the
persioApiRequesthelper function to make HTTP POST requests to the/identifyendpoint. - No additional external dependencies beyond the Persio API and n8n credentials are required.
Troubleshooting
- Missing User ID: If no User ID is provided, the node generates an anonymous ID. Ensure this behavior aligns with your use case.
- Invalid Traits Format: Traits must be provided as key-value pairs; incorrect formatting may cause API errors.
- Context Fields: Providing invalid or malformed context fields (e.g., wrong timezone format) might result in request rejection.
- API Authentication Errors: Ensure the API key credential is correctly configured and has necessary permissions.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Persio API endpoint.
- Error Messages: The node throws error messages received from the Persio API. Review these messages for hints on missing or invalid parameters.
Links and References
- Persio API Documentation (general reference for API endpoints and payloads)
- n8n Documentation for configuring credentials and using HTTP Request nodes if needed