Privacy & Security

JavaScript Overview
Last updated 1/24/2022

About ImpactProduct (“IP"):

ImpactProduct ("IP") was created to democratize product analytics. We deliver actionable insights to teams that are impacted by the product usage, but do not access traditional product analytics tools. We do so by removing the largest usage challenges of most analytical tools - namely, requirement of developer support for instrumentation,  confusing analytical dashboards and we focus on delivering insights, rather than raw data.

To remove the developer support requirement for instrumentation, IP accesses site usage data using IP’s own javascript added by its customers to their sites. The IP script pulls anonymous event data through the APIs. IP's JavaScript does not capture PII data of any kind. IP's Customers pass it's users ID so that IP can match site usage behaviors to specific users on IP's backend. IP stores all event data on Google Cloud. Data is encrypted both at rest and in transit. IP’s data capture is also asynchronous, so it doesn’t impact page load. More on that below.

Instead of showing analytics in a confusing dashboard, IP shows event data in a Chrome Extension that overlays your product. Individual users add IP's extension to their browser.

What is the ImpactProduct JavaScript code snippet?

ImpactProduct measures the user experience for any web page/product that has it’s JavaScript
code (“JS Script”) added to any HTML page.

How does the JavaScript code snippet work?:

The JavaScript allows ImpactProduct to measure click events and URLs per visit.
ImpactProduct does NOT capture Personally Identifiable Information (“PII”). All data is
aggregate and non-specific to any PII. ImpactProduct’s JS Script is an event listener that tracks
HTML DOM events for any HTML page which has its code. ImpactProduct’s code ties the
events to a specific element’s Selector. Below is an example of the Selector path that we would
pull from the “Subscribe Now” button on ESPN. We would show all event data for that
“Subscribe Now” button by linking it to it’s path. Thus there is NO need for custom event tags. If an element’s Selector changes, you can merge Selector data from different
elements into one chart.

Note: ESPN is not an ImpactProduct customer. This is an example to show that an element's selector path is publicly available information.

Will the JavaScript code snippet impact my page loading or site navigation?

The loading of the ImpactProduct JS Script should not impact page load. First, it is a small file,
approximately 10kb. Also, it is downloaded by a browser only once per user and stored in that
user’s browser cache.

Once the JS Script is loaded (after first visit), ImpactProduct uses sendBeacon API to send
page analytics requests to the server. This means that the data being sent does not impact site
navigation. A user would NOT need to wait for the request to be complete before the user could
navigate to the next page. Read more here:

Does the JavaScript track Personally Identifiable Information?

The ImpactProduct Javascript does NOT track any PII. It tracks HTML DOM events and aggregates the data. However, we require customers to pass use their User IDs for every session. We match the User ID to user email and sales information on our backend.

Where can I find the JavaScript code snippet for my account? 

When you initially sign up, you will get the code snippet in your setup wizard. See below screenshot:

Do I need to create tags for each event?

No. You do not need to create tags for each element that you want to track. We track all events without any extra tags created. We call it “No Code Analytics” because once you add our JavaScript code to the head tag, you do not need to involve developers in tracking events or user flows.

Does ImpactProduct Open Source its source code? 

We plan to open source code for our JavaScript.