Actions31
- Conversation Actions
- Message Actions
- Visitor Actions
- Contact Actions
- Bot Actions
- Operator Actions
Visitor → Track Visitor
AI-generatedOverview
The "Track Visitor" operation in the Visitor resource allows you to track visitor activity on your website or application by sending event data to the Tidio API. This node is useful for monitoring user behavior, such as page views or custom events, enabling personalized engagement and analytics.
Typical use cases include:
- Tracking when a visitor views a specific page.
- Logging custom events like button clicks or form submissions.
- Enhancing customer profiles with behavioral data for targeted marketing or support.
For example, you can track a "page_view" event whenever a visitor loads a page, optionally including additional custom properties describing the context of the visit.
Properties
| Name | Meaning |
|---|---|
| Visitor ID | The unique identifier of the visitor to track. |
| Additional Fields | A collection of optional fields to customize the tracking event: |
| - event | The name of the event to track (default is "page_view"). |
| - customProperties | Custom properties as a JSON object to provide extra details about the event. |
Output
The node outputs a JSON object representing the response from the Tidio API after tracking the visitor event. This typically includes confirmation of the tracked event and any related metadata returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"json": {
"success": true,
"event": "page_view",
"visitorId": "visitor123",
"properties": {
"key1": "value1",
"key2": "value2"
}
}
}
Dependencies
- Requires an active Tidio API integration with valid credentials including an API key, client ID, and client secret.
- The node uses these credentials to authenticate requests to the Tidio API endpoint.
- Proper configuration of the Tidio API credentials in n8n is necessary before using this node.
Troubleshooting
- Invalid Visitor ID: If the visitor ID is missing or incorrect, the API will fail to track the event. Ensure the visitor ID corresponds to an existing visitor in Tidio.
- Malformed Custom Properties JSON: The
customPropertiesfield must be valid JSON. Invalid JSON syntax will cause errors. Validate JSON format before input. - API Authentication Errors: Incorrect or expired API credentials will result in authentication failures. Verify that the API key, client ID, and client secret are correctly configured.
- Network Issues: Connectivity problems may prevent the node from reaching the Tidio API. Check network access and proxy settings if applicable.
- Unexpected API Responses: If the API returns errors, review the error message included in the node output for guidance.
Links and References
- Tidio API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of nodes and credentials)