The Install Code
Your code should look something like this:
You have a few options for installing the code:
Option 1: Copy code into your HTML
The script provided by Inspectlet (look above for an example) should be placed anywhere in your site's HTML (preferrably in the <HEAD> section). Inspectlet is loaded asynchronously in a non-blocking way so it doesn't slow down your site. If you're having trouble installing Inspectlet on your site, send us an email and we'd be happy to help!
Option 2: Installing on WordPress with our WordPress Plugin
We have a WordPress plugin that'll take care of placing the code in your site, please download it from here: Inspectlet WordPress Plugin.
Option 3: Segment.IO's 1-Click Installation
If you guys use Segment.IO, the fine folks there have made installing Inspectlet a one-click affair.
Handling Sensitive Data
We take privacy very seriously. Any data marked as sensitive is ignored by Inspectlet, therefore the data is never transmitted to our servers. You can mark both input fields (like the credit card textarea on a checkout form) and HTML content (like a tax report in a DIV or TABLE) on your page as sensitive.
Sensitive Data Entered Into Input Fields
To mark input fields as sensitive, simply add the inspectletIgnore class to them. Please note that this class is not needed for password fields, Inspectlet ignores those automatically. For example, the following credit card input field is tagged as sensitive and any text entered in it will not be recorded:
<input type="text" class="inspectletIgnore" name="ccnumber" />
Sensitive HTML Content on the Page
Sometimes you may want to not record or transmit certain information on the page, you can mark that HTML content as sensitive by adding the inspectlet-sensitive attribute to the element whose content and children you want to be shielded from recording. Inspectlet will not transmit any text inside these contains or any of its children.
For example, if you wanted to mark a div with the class of "tax-data" as sensitive, here's what that would look like:
<div class="tax-data" inspectlet-sensitive> ... </div>
Tagging User Sessions
Here's an example of tagging a session with the user's email address:
Tags are also useful for marking sessions where users exhibited interesting behavior, made it to the checkout page, encountered an error, etc. These tags will make sorting through numerous screen captures easier.
__insp.push(['tagSession', "viewed checkout"]);
A tag must be a string or integer and can be a maximum length of 100 characters. A tag can be applied at any time and only needs to be set once to tag the entire session. A session can have infinite tags.
Marking sessions where a sale is made
If you're interested in watching all screen captures where a visitor purchased something or made it to the shopping cart page, you can tag those screen captures with a marker like "purchase" like this:
How does Inspectlet work?
Inspectlet's screen capture is a component of the code that works by recording all the events that take place in the browser such as keystrokes, mouse movements, scrolling, clicking, and then sends this data (which is only bytes in size) to our servers. Once we receive this data, we compile a screen capture by overlaying the events onto the visitor's page. Inspectlet has two different techniques for screen capture, which allow it to be versatile enough to capture even the most complicated websites.
My site uses advanced technologies, will Inspectlet still work?
Will Inspectlet slow down my website?
Short answer: No, not at all.
How does Inspectlet handle subdomains?
It's completely up to you how you want to handle subdomains. Got a subdomain that needs to be tracked with another subdomain? With the main site? With a few other subdomains? Completely separately? Inspectlet doesn't care. Track your site any way you want by either making a new site from your Dashboard, or using the same embed code to track them together.
What happens if I go over my plan's quota?
By default, Inspectlet automatically staggers your monthly recorded sessions quota throughout the month. This means that Inspectlet may stop recording data after some time in the day to prevent your sites from exhausting your monthly quota before the end of the month and being left with a portion of the month without any data at all. For this reason it is recommended to keep staggering enabled. If you'd rather manage your quota yourself, you can disable this functionality.
If your usage exceeds the plan's limit then Inspectlet stops recording for that day if you have staggering enabled, otherwise for the month. Upgrading your plan will re-enable your account since since your quota is increased. We will never automatically bump you up to the next larger plan without your permission.
My site is larger than the largest plan available. What can I do?
If your needs exceed the highest plan we have available, get in touch with us and we can tailor something that fits.