UChat Official

Introduction

In today's digital landscape, tracking user interactions and events is crucial for understanding customer behavior, optimizing marketing strategies, and enhancing chatbot functionalities.

This summary explores the process of creating, logging, and analyzing custom events within a chatbot environment, emphasizing the integration of API calls, flow builder tools, and analytics dashboards.

By leveraging these features, businesses can unlock a multitude of use cases, from offline event tracking to detailed sales analytics, all within a seamless platform.

Deep Dive into Custom Event Management

1. Creating and Logging Custom Events

  • In-Flow Creation:
    Users can finalize the creation of custom events directly within the flow builder. This intuitive interface allows for easy setup without requiring extensive technical knowledge.

  • Logging via Flow Builder:
    Once created, custom events can be logged automatically during user interactions, enabling real-time data collection.

  • API-Based Logging:
    For more advanced use cases, such as offline events or external triggers, the platform supports API calls to log custom events programmatically.

2. API Endpoint for Custom Event Logging

Feature

Details

Endpoint

subscriber/log-custom-event

Supported Methods

POST (via API call)

Use Cases

Offline event tracking, external system integration, automation outside chatbot flows

  • API Authentication:
    Users must authorize using an API key, which can be generated or retrieved from the platform's API key management section.

  • Request Structure:
    The API call requires specific parameters:

    • user_ns (User Identifier)

    • event_name (Must match existing custom event)

    • text_value (Descriptive info about the event)

    • pricing_value (Monetary value associated with the event)

    • quantity (Number of items or units)

  • Example Workflow:

    • Fetch user ID (e.g., user_ns3)

    • Select or define an event name (e.g., template_sale)

    • Provide relevant details (e.g., restaurant_template, $297)

    • Execute the API call and receive a status response (e.g., 200 OK)

3. Practical Implementation

  • Triggering a Custom Event:
    For example, when a customer purchases a restaurant template outside the chatbot, an API call can log this event with details like:

    • Event Name: template_sale

    • Text Value: restaurant_template

    • Pricing: $297

    • Quantity: 1

  • Verification:
    After logging, the platform's analytics dashboard updates automatically, reflecting the new event.

Analytics and Visualization

1. Monitoring Custom Events

  • Real-Time Updates:
    The analytics dashboard displays logged custom events immediately after they are triggered, providing insights into:

    • Event counts

    • Revenue generated

    • User activity

  • Event Details:
    Hover over individual entries to see timestamp and additional info.

2. Graphical Representation

  • Customizable Charts:
    Users can modify graphs to suit their analysis needs:

    • Change chart types (bar, line, pie)

    • Filter by date ranges

    • Segment by user or event type

  • Example:
    Visualize sales over time for different templates, compare offline vs. online events, or analyze user engagement metrics.

Use Cases and Practical Applications

Use Case

Description

Benefits

Offline Sales Tracking

Log sales made outside the chatbot (e.g., in-store, workshops)

Unified view of all transactions

Marketing Campaigns

Track responses to external marketing efforts

Measure ROI and engagement

Product Launches

Log custom events for new product interest

Data-driven decision making

Customer Support

Record support interactions or issue reports

Improve service quality

Integration with Third-Party Platforms

  • Automation Tools:
    The API endpoint can be integrated with platforms like Make, Integromat, Zapier, or Shape to automate event logging based on external triggers.

  • Seamless Data Flow:
    This integration allows for automatic synchronization of offline events, CRM updates, or marketing actions, ensuring comprehensive analytics.

Best Practices for Effective Custom Event Tracking

  • Consistent Naming Conventions:
    Use clear, descriptive event names to facilitate analysis (e.g., purchase_template, signup_complete).

  • Detailed Text Values:
    Include relevant context in text_value for richer insights.

  • Accurate Pricing Data:
    Ensure pricing_value reflects actual transaction amounts for revenue tracking.

  • Regular Monitoring:
    Frequently review analytics dashboards to identify trends and anomalies.

  • Leverage Graphs and Filters:
    Customize visualizations to focus on key metrics and timeframes.

Final Thoughts

Custom event logging is a powerful feature that enhances a chatbot platform's ability to capture detailed user interactions and generate actionable insights.

By combining flow-based creation, API integrations, and dynamic analytics dashboards, businesses can monitor offline and online events seamlessly, optimize their marketing strategies, and improve overall customer engagement.

This comprehensive approach ensures that every interaction, purchase, or engagement is tracked accurately, providing a holistic view of customer behavior. Whether you're tracking sales outside the chatbot, measuring campaign effectiveness, or analyzing user preferences, the tools and methods outlined here empower you to make data-driven decisions with confidence.