Bento icon

Bento

Native integration for Bento API actions

Actions16

Track Event

AI-generated

Overview

This node operation 'Track Event' allows users to record custom events and behaviors associated with a subscriber or user, identified by a unique user ID (typically an email address). It supports attaching additional properties to the event for enhanced segmentation and personalization. This is useful in scenarios such as tracking user actions like purchases, page views, or other custom-defined events to enable targeted marketing, analytics, or automation workflows.

Use Case Examples

  1. Track a 'purchase_completed' event for a user with email 'user123@example.com' and include properties like 'product_id' and 'price'.
  2. Record a 'page_viewed' event when a user visits a specific page, attaching properties such as 'page_url' and 'referrer'.
  3. Log custom events for user behavior analysis and trigger automated marketing campaigns based on event data.

Properties

Name Meaning
User ID The unique identifier for the user (typically email address) whose event is being tracked.
Event Name The name of the custom event to track, e.g., 'purchase_completed' or 'page_viewed'.
Event Properties Additional key-value pairs of properties and data to attach to the event for segmentation and personalization.

Output

JSON

  • operation - The operation performed, here it will be 'trackEvent'.
  • success - Boolean indicating if the event tracking was successful.
  • event
    • userId - The user ID associated with the tracked event.
    • eventName - The name of the tracked event.
    • properties - The additional properties attached to the event.
  • apiResponse - The raw response from the Bento API after tracking the event.
  • message - A message indicating success or failure details.
  • error - Error message if the event tracking failed.

Dependencies

  • Requires an API key credential for Bento API authentication including publishableKey, secretKey, and siteUuid.

Troubleshooting

  • Ensure the User ID and Event Name are provided and valid; missing these will cause errors.
  • Validate that the User ID is in a proper email format as expected by the API.
  • Check that event property keys and values do not exceed length limits (50 characters for keys, 500 for values).
  • If the API request fails, verify the API credentials and network connectivity.
  • Rate limiting errors may occur; the node retries with exponential backoff but excessive requests should be avoided.

Links

Discussion