When selecting where to integrate the Innerworks SDK, keep the following points in mind.

1

Pick a Page a User Visits Just Once Each Visit

We only need to check a user once, so something like a login page works perfectly. Whenever the user logs in, we can determine if that session is being run by a fraudulent or automated account. If it’s a page a user visits multiple times in a session then this creates redundant requests.

2

Pick a Page a User Must Visit

If a User is able to enter your platform through a route that does not have the Innerworks SDK then we cannot perform our analysis on those users. Make sure it is integrated on every entry point to the platform.

3

Pick a Page With User Interaction

The Innerworks SDK is designed to sit invisibly in the background to perform metric collection. To ensure optimal performance, the page where the SDK is instantiated should require the user to perform a set of actions. This should include entering text and mouse movements and/or clicks.

4

Pick a Page With a Trigger

There will need to be some event which should be hooked into to trigger the sending of the metrics to the Innerworks API. This is often a sign in button.

Typical locations to integrate the Innerworks SDK are sign in or sign up pages.