Event collection process

Here's a rewritten version of the explanation:

  1. Event Initiation:

    • The process begins when a user interacts with your digital platform, such as a website or app.
    • The client-side system (like your website's JavaScript) detects this interaction and generates an event, a data packet that captures what the user did.

  2. Event Transmission:

    • This event data is then sent to Tracardi, typically in real-time.
    • Transmission is usually handled by a JavaScript snippet embedded in your website or via an API call from your application.
    • The event includes key identifiers like profile ID and session ID, which allow Tracardi to recognize and track the user across different interactions.

  3. Reception and Validation:

    • Tracardi's API receives the incoming event data.
    • The system checks whether the event follows the required format and includes all necessary information.
    • It also verifies the event's source by checking the event source ID to ensure it comes from a valid origin.

  4. Profile Identification:

    • Tracardi attempts to match the event with an existing user profile using the provided identifiers.
    • If no match is found, a new profile may be created, or the system might try to link the event to an existing profile using other available data.

  5. Data Enrichment:

    • Tracardi may enhance the event data by adding additional information.
    • This could include the user's geographic location (derived from the IP address) or marketing-related data such as UTM parameters.

  6. Event Processing:

    • The event can trigger specific workflows within Tracardi, such as starting an automated marketing sequence.
    • It might also activate integrations with external systems.
    • The event is processed according to the rules and actions you've configured within Tracardi.

  7. Profile Update:

    • The event data is used to update the user's profile in Tracardi's database.
    • If applicable, Tracardi may merge this profile with others if it determines they belong to the same user.

  8. Data Storage:

    • The complete event data is stored in Tracardi's database for future analysis and reporting.
    • The user's profile is also updated and saved, reflecting any new information from this event.

  9. Profile ID Response:

    • Tracardi sends the profile ID back to the client (your website or app).
    • This ID should be stored on the client-side and included with all future events for this user, ensuring consistent tracking.

This process is executed in parallel in commercial Tracardi, some steps may be pushed as background processes, while open source version process all steps one after another.