Agent setup: authorize Sight MCP and ask your agent to call
get_tracking_setup. It configures this integration automatically.
Wordpress
A real WordPress plugin — settings page for the API key, then the same
<script src="…/script.js?k=…"> collector the other Sight integrations
use, enqueued site-wide via wp_enqueue_script.
Part of Sight, split across repos under the sightapp org — see
sightapp/sight-backend's
SPEC.md for the full picture, and tasks/plan.md there for how this
repo fits the site-integrations roadmap (Track B). WordPress is the
wave-1 CMS checkpoint in that plan.
Install
- Zip this folder (or clone it into
wp-content/plugins/sight-analytics). - In WP Admin: Plugins → Add New → Upload Plugin (or activate if
it's already in
plugins/). - Settings → Sight Analytics.
- Paste the project's API key from the Sight dashboard.
- Save. Visit the site once, then check Sight dashboard → Overview.
The ingest key is a public collector credential (the same ?k= on
/script.js). It cannot read revenue or mutate the project. Do not put a
dashboard JWT or a Stripe secret here.
What this records
- Pageviews on every public page, including client-side navigations
(the script hooks
history.pushState/popstate). - The
<noscript>pixel as a fallback for JS-off visitors, and for AI crawlers that fetch images but don't execute JS. - Crawlers that fetch
/script.jsitself are counted by the backend from the User-Agent on that GET — this plugin does not also POST from PHP, so a bot that both renders the page and fetches the script isn't double-counted. For origin-side crawler capture (Express etc.), seesight-express.
WooCommerce checkout / product events live in a separate plugin:
sight-woocommerce.
If you only need pageviews, this plugin is enough.
Verify
Load a public page while logged out (or in a private window), then:
A pageview for the path you visited should appear within a few seconds (ClickHouse flush is 500ms / 1000 events).