Netcore Unbxd Analytics Integration

The following sections explain how Netcore Unbxd Analytics works and how to integrate it with your website. This guide is intended exclusively for customers who have integrated using our V2 integration method. For more details on the various integration versions, refer to this documentation.

As part of our ongoing upgrade initiative, we are gradually transitioning all customers to the latest SDKs. Please note that older SDK versions will be deprecated. We strongly recommend migrating to the upgraded SDK to leverage the newest features and improvements.

💡
Important Point to Remember
To ensure a smooth, fast, and scalable analytics setup, Pulse is the recommended onboarding method for all customers. It provides automated event tracking, and faster go-live with minimal engineering dependency.
Use other methods (JS, GTM, API) only in cases where Pulse cannot be implemented due to specific technical reasons.
Refer to the given document to learn more about Pulse Integration.

Why is it essential to set up Netcore Unbxd Analytics?

Analytics plays a pivotal role in unlocking the full potential of the Netcore Unbxd platform.

By integrating Analytics into your digital storefront, unique tracking codes are embedded across your properties. These codes trigger events interactions like:

Search queries
Product clicks
Impressions
Add to Cart actions
Orders

Each event is captured per visitor using browser cookies, enabling our AI/ML models to build precise visitor profiles with preferences such as category, brand affinity, and price sensitivity.

These profiles are instrumental in:

Delivering personalized search results
Enhancing recommendation relevance
Generating insightful reports

📘
Note
A complete and accurate analytics integration is essential for delivering high-conversion personalization. Incomplete or broken tracking leads to poor search relevance and underperforms AI capabilities.

Integration Methods

The Analytics tracker must be installed on every version of your site (desktop, mobile, tablet). We support several integration methods to match your technical needs.

Netcore Unbxd Pulse (Recommended)

Add a single line of code and let our experts manage the rest.

API Implementation 🔗

Use API references for each event you want to track. Ideal for teams needing customized integration logic.

JavaScript Implementation

Add a custom JavaScript tracker to your site’s HTML to trigger and manage event tracking.

Tag Manager Implementation

Use GTM, Tealium, or any tag manager platform to insert the analytics tracker easily into your website.

What types of events are tracked?

Analytics captures user behavior across all touchpoints using two broad categories:

Global Events

Track standard site-wide interactions:

Visitor
Page Views
Product Clicks
Product Add to Cart
Product Orders

Feature-specific Events

Capture behavior related to specific Unbxd features:

Search Queries
Product Impressions
Autosuggest
Category Page Interactions
Browse Impressions
Recommendations

Events We Track

Visitor Event

The first event created when a shopper visits your site. It tracks and builds profiles using browser cookies for two types of visitors: first-time users and repeat users.

Site-level information are stored as cookies and are titled as,

User ID: unbxd.userId
Visit ID: unbxd.visitId
Visit Type: unbxd.visit

Search Hit

Triggered whenever a shopper clicks a product or product image from any Product Listing Page (PLP), Category page, or Recommendation widget. It will capture the clicked product’s unique ID and the page where the click activity occurred.

This data can be used to highlight ‘Popular Products’ and create personalized ‘Recommended For You’ lists, ensuring a more customized shopping experience.

Product Click

This data can be used to highlight ‘Popular Products’ and create personalized ‘Recommended For You’ lists, ensuring a more customized shopping experience.

Add to Cart

Triggered each time a user adds a product to their cart, regardless of the originating page—whether it’s the Product Detail Page (PDP), Product Listing Page (PLP), historical orders, or any other page. For users incrementally adding products, the event should fire once per product addition, and the qty parameter should reflect the quantity added during that specific action.

Order

Triggered when a purchase is completed on your site. This event should be fired for each product in the order, capturing valuable data such as the product ID, quantity, and order details.