Skip to main content

Feature Overview｜SDK Web Behavior Tracking Tool

  • Updated

    The Crescendo SDK resolves key challenges in real-time data tracking and customer engagement. Due to privacy policy restrictions, many companies are unable to share complete Google Analytics data. Our SDK overcomes the data latency limitations of GA4, providing fast and accurate tracking of website visitor behavior. It also supports the latest "User Identification and Identity Resolution" feature, helping brands achieve more efficient remarketing and personalized interactions.

     

    🙋 Key Features and Advantages

    Real-time Data Tracking

    Resolves the issue of being unable to interact in real-time due to GA4's data latency of up to 72 hours. Supports the rapid collection of visitor behavioral data, such as: page views, product views, add to cart, begin checkout, and purchase.

     

    User Identification and Automatic Identity Resolution 【 🎉 New Feature! 】

    With the new Web SDK Identify feature, the system empowers brands to precisely capture and store member identification data at optimal touchpoints (such as upon "successful login" or "registration completion"). 

    Once an anonymous visitor logs in and is successfully authenticated, the SDK automatically triggers the identity stitching mechanism, seamlessly merging the user's "pre-login" anonymous browsing footprint into their identified member profile. This effectively eliminates marketing fragmentation and truly achieves a User Identity Upgrade.  (Currently applicable only to self-hosted e-commerce clients)

    Cross-Device Tracking Integration

    As long as users pass in the same exclusive member ID (customerId) when logging in across different devices (such as mobile phones and computers), the browsing behavior (dialogue) on each device will be automatically linked under the same user record, allowing for precise tracking of cross-screen footprints.

    📕 To install SDK, please refer to: SDK install instruction

    *This feature currently only supports "CAAC - Web Chat" & "MAAC - Cart Remarketing 2.0"

    Crescendo Lab supports near real-time web behavior tracking, including the following events:

    Standard E-commerce Behavior Tracking

    • page_view (Page View)
    • view_product (Product View)
    • add_to_cart (Add to Cart)
    • remove_from_cart (Remove from Cart)
    • begin_checkout (Begin Checkout)
    • purchase (Purchase)

    [New] User Identification Event (clIdentity) Tracking (Currently applicable only to self-hosted e-commerce clients)

    • clIdentity (User Identification Event): Allows clients to proactively pass in information such as customerId (primary identifier) or email (secondary identifier) at appropriate times, like upon a successful login, to bind the current device's behavior to a specific member.

    ⚙️ Web Behavior Tracking Event Settings:

    Standard E-commerce Behavior Tracking (e.g., page_view, add_to_cart, purchase, etc.)

    E-commerce Platform (EC Platform)

    Applicable to SHOPLINE / 91App / Shopify / CYBERBIZ. No additional configuration is required, as the tracking plugin is already built into our exclusive SDK code.


    Self-hosted Website:

    Event recording (Please choose one of the following methods to record events. Do not use both methods simultaneously to avoid duplicate event recording.)

    [New] User Identification Event (clIdentity) Tracking Settings

    • Self-hosted Website Requires your technical team (IT) to push member information to the Google data layer within the frontend programming logic upon "successful member login" or "completed registration". Please refer to: Technical Guide
    • E-commerce Platform (EC Platform)  ⚠️ Note: This feature is currently NOT supported by the built-in tracking code for the four major e-commerce platforms (SHOPLINE / 91App / Shopify / CYBERBIZ).

    💡 How the User Identification Event Works:

    • Seamless Integration and Stability: Adopts the same window.dataLayer transmission mechanism as GA4.
    • Data Update Logic: When member data is transmitted repeatedly, the system applies the "New covers old" principle and will "Ignore null" values, ensuring no duplicate user data is generated.
    • Logout Mechanism: When switching users (logging out) on the same device, there is "no need" to call any method to notify the SDK. Maintaining the current state prevents the loss of dialogue records during page reloads. When a new user logs in and the customerId changes, the SDK will automatically establish a new dialogue.

    🎉 Now that you understand the new features and operational mechanisms mentioned above, please proceed to the next article: [📕 Setup Guide | SDK Web Behavior Tracking Tool], to begin the actual installation of your tracking codes and events!

    Related articles