Skip to main content

Quick Start

Get up and running in under 10 minutes.

1. Create your account​

Go to dashboard.store-pilot.net/register, then open the confirmation link we email you — your first sign-in waits for it. If you were invited to a team, register from the invitation link instead and you are signed in straight away.

2. Add your site​

Sites → Add Site

The setup wizard asks for the site's name and domain, and shows the API key for it.

3. Install the plugin​

StorePilot is not in the WordPress.org directory yet, so the plugin is installed by upload: download the .zip from the setup wizard (or Settings → Installation), then in WordPress go to Plugins → Add New → Upload Plugin, upload it and click Activate. Updates arrive in Plugins like any other plugin's afterwards. See Installation for the details.

Then go to StorePilot → Settings in WordPress, paste the API key, and click Save Changes. There is nothing else to fill in: the plugin already knows where to send its data.

4. Choose what to collect​

Every switch lives in the dashboard, under Settings → Privacy for the site — session replay, canvas and console recording, exclusions, consent and retention. See Site settings. Errors, page views and WooCommerce checkouts are collected as soon as the key is saved.

5. Verify First Events​

Open your WordPress site in a browser, navigate a few pages. Within 30 seconds, check:

Dashboard → Sites → [Your Site]

You should see:

  • Pageviews counter incremented
  • Visitors counter incremented

To test error tracking, open browser DevTools and run:

throw new Error("StorePilot test error");

The error should appear in Dashboard → Errors within seconds.

What Happens Next?​

  • Errors are captured automatically — no code changes to your WordPress theme needed
  • Recordings are uploaded once a visit has shown something (a click, typing, an error or 30 seconds of footage), while Record session replays is on in the site's Settings → Privacy
  • Leads are captured when a visitor fills in WooCommerce checkout fields
  • Notifications fire on the first occurrence of each unique error and on each new lead

Explore the Documentation​