When developers install your package, it signals real product usage. With Reo.Dev, you can now identify and monitor installs of your NPM packages. This short guide will walk you through how this works and how you can set it up.

<aside> 💡

Note: NPM install tracking works for developers installing packages via the terminal as well. No additional setup is required.

</aside>

How NPM Install Tracking Works

Once reo-census is added to your package:

1. A developer installs your package using npm install.
2. The reo-census script runs automatically during installation.
3. Installation metadata is sent to Reo’s telemetry endpoint.
4. Reo processes the data and surfaces it as developer activity signals in your dashboard.

Pre-requisites

Before setting up NPM install tracking, please ensure the following are in place:

1. Share your NPM package URL with Reo

Provide your NPM package link (e.g. https://www.npmjs.com/package/your-package) to the Reo team so we can configure tracking on our end.

2. Configure Product Usage Metrics in Reo

You’ll need to create a metric to track installs:

• Go to Configurations > Product Usage
• Click on Create New
• Create a metric named: npm_install

This ensures all install events are correctly captured and surfaced as signals in your dashboard.