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.
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.
code (“JS Script”) added to any HTML page.
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.
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: https://golb.hplar.ch/2018/09/beacon-api.html
When you initially sign up, you will get the code snippet in your setup wizard. See below screenshot: