Session tracking is one of Noibu's primary functions. The NoibuJS script collects data from every unique shopper session on your eCommerce site and records a video of each session in the Sessions table. The session video tracks everything the shopper did, indicates where they encountered errors, and highlights the errors may have prevented them from completing their purchase. When examining session recordings, you can filter the Sessions index by several data points–like URLs visited, web vital scores, user clicks, Session Symptoms, and more–to find sessions that meet specific conditions or highlight certain behaviours.
Noibu tracks a range of standard session data, but most eCommerce sites are built with unique identifiers–like customer_id, coupon_id, or version_id–that aren't tracked by default. This is where the NoibuJS software development toolkit–or SDK–comes into play. The NoibuJS SDK allows you to track up to 10 custom attributes in session data so you can quickly isolate a specific session, a capability that adds value to customer support, quality assurance, and health monitoring workflows.
SDK Use Cases
The SDK comes in handy whenever you need to isolate a specific shopper session that would be difficult to find without a unique identifier. Use cases for the SDK are numerous, but some of the most popular uses include:
- Investigating Shopper Complaints: Most eCommerce sites track clients through unique identifiers, and you can prompt the NoibuJS script to collect these identifiers in session recordings so you have an easy way to associate a shopper complaint to a session recording. For example, if a shopper reports an issue and your NoibuJS script tracks customer_id, you can filter the Sessions table by the shopper's ID value to pull their session.
- Tracing Survey Responses: If you collect shopper feedback through a help desk or an in-app survey, filling out the survey may be captured as part of a session recording, and you can use this to trace the shopper's session from the survey response. The survey may provide a unique, anonymized identifier–QualtricsID, TealiumID, etc.–and you can configure the SDK to track this identifier in session recordings.
- Facilitating A/B Testing: Collect custom ID values that correspond with each page variant in an A/B test, which gives you an easy way to sort sessions on each variant to see which option results in the best conversion rates.
- Tracking Coupon Usage: Do you have a promotion going on? Configure the SDK to track the promotion_id or coupon_id so you can monitor how the promotion is affecting sales.
Implementing the NoibuJS SDK is a simple process, and we're happy to help! If you have questions about this process, contact our solutions engineering team at support@noibu.com.
Advanced Error Capturing
Another perk of implementing the SDK is capturing a wider range of errors. Sometimes, errors are hidden from the NoibuJS script by JavaScript frameworks like Vue.js and React. Noibu has developed SDK functions built for each framework to uncover errors that were previously invisible to Noibu. Follow the installation instructions linked below to enable advanced error capturing:
Please note that if your website uses Vue.js or React and you do not implement these SDKs, a majority of errors on your site will not be captured, so implementing the Vue or React SDK may be necessary for your Noibu console to function properly. React dev tools, or tools like Wappalyzer, can be used to confirm if your site uses one of these frameworks.
Note: If your domain uses React's server side rendering, you will not need the Noibu React SDK to capture errors.
Learn more about how to Optimize ROI with Noibu.