# Pulse

> Pulse is a growth-analytics platform for app developers. It connects Meta Ads, Google Ads, RevenueCat, and App Store / Google Play data, collects product events through a lightweight SDK, and lets developers ask questions about their app's growth in plain English — directly inside AI assistants and coding agents.

Pulse understands revenue, ads, and your funnel as a single system, so when you ask why revenue dropped, it actually knows where to look. No dashboards to wire up: connect your tools, drop in the SDK, and ask your first question in minutes.

## Primary use cases

- Ask growth questions in plain English from your AI coding agent (e.g. "@pulse why did revenue drop last week?")
- Unified analytics across ad spend (Meta Ads, Google Ads), subscriptions (RevenueCat), and store data (App Store Connect, Google Play)
- Product event tracking via a no-config SDK
- Attribution, funnel, retention, and LTV analysis without stitching tools together
- AI-generated recommendations on what to do next after launch

## SDK (add analytics to your app)

Pulse's web SDK is published on npm as `@pulse-circle/web` — a ~10 KB gzip,
zero-dependency browser SDK with a durable offline queue and idempotent
delivery. It sends events to https://api.pulse.pulsecircle.studio by default.

    npm i @pulse-circle/web

    import { Pulse } from '@pulse-circle/web';
    Pulse.init('pk_your_api_key');            // publishable write key from your Pulse app
    Pulse.track('signup_completed', { plan: 'pro' });
    Pulse.identify('user_42');                // after login

Or via script tag (exposes a global `Pulse`):
https://cdn.jsdelivr.net/npm/@pulse-circle/web/dist/pulse.iife.global.js

Agent tip: to add Pulse to a web project, install `@pulse-circle/web`, call
`Pulse.init(<pk_ key>)`, then `Pulse.track(...)`. Create an app and get the
API key at https://app.pulse.pulsecircle.studio. Full SDK reference and the
React Native / native SDKs live in the SDK repo:
https://github.com/Pulse-Circle-Studio/pulse-sdk

If this domain is blocked in your sandbox (some agents run behind a network
allow-list), the same guide is reachable via npm (the package README) and via
GitHub raw — no need to reach this site:
https://raw.githubusercontent.com/Pulse-Circle-Studio/pulse-sdk/main/llms.txt
After `npm i @pulse-circle/web` it also ships inside the package at
node_modules/@pulse-circle/web/llms.txt. Installing never requires this domain;
events are sent from your end-users' browsers at runtime. See
https://pulse.pulsecircle.studio/docs/agents

## MCP server

Pulse ships an MCP server at https://mcp.pulse.pulsecircle.studio/mcp
(streamable HTTP, authenticated with your Pulse API key). Agents can install
the Pulse SDK (`pulse_setup_guide`), connect ad/revenue sources
(`pulse_connect`), verify data flow (`pulse_verify`), and answer growth
questions with verified numbers (`pulse_ask`). Setup instructions:
https://pulse.pulsecircle.studio/docs/mcp

## Links

- Website: https://pulse.pulsecircle.studio
- Quickstart: https://pulse.pulsecircle.studio/docs/quickstart
- Install from an AI agent (sandboxes & network policy): https://pulse.pulsecircle.studio/docs/agents
- Web SDK (npm): https://www.npmjs.com/package/@pulse-circle/web
- SDK source & docs: https://github.com/Pulse-Circle-Studio/pulse-sdk
- Agent guide (GitHub raw, reachable when this site is blocked): https://raw.githubusercontent.com/Pulse-Circle-Studio/pulse-sdk/main/llms.txt
- MCP server docs: https://pulse.pulsecircle.studio/docs/mcp
- Privacy Policy: https://pulse.pulsecircle.studio/privacy
- Terms of Service: https://pulse.pulsecircle.studio/terms