User Interaction Capture (SDK) FAQ

Introduction

Not sure about something UIC related? Below you’ll find answers to some common questions you may have on the Discover UIC. Also, please feel free to use the search, it's a great feature of the guidebook that can quickly reveal pages with answers. If you still can’t find the answer you’re looking for, contact your account manager, assigned TA or support if a customer or business partner!

Questions & Answers

What is the size of the SDK?

Un-minified 700kb, minified approximately 170kb.

What is captured by the SDK?

The premise of the SDK is to capture user interactions and page DOM to facilitate data analysis. Other data items are either captured by default or can be added to the SDK configuration to extend data capture to: page performance metrics; data layer; AJAX calls; etc.

Will the SDK slow down my page?

The SDK is optimized to reduce load on both web server and browser-based web pages. The UIC is structured for asynchronous loading and caching by the browser.

Where within the page is it best to load the SDK?

To ensure as much data is captured as possible, the SDK is best loaded after the pages HEAD element This is covered in the UIC Quick Start.

The payload is getting blocked by content security policy (CSP), what can I do?

Allow the domain where the data payload is to be posted to, to be added to the allow list of the relevant content security policies defined on the website.

What web technologies can data be captured from?

Without additional config, Discover is agnostic of web technologies. In a few situations, additional configuration tuning may be required.