ConversionCRM is a script tag and a REST API. If your app runs in a browser or has a backend, it integrates in under 10 minutes. No native connector needed.
ConversionCRM collects data two ways: a client-side script tag that auto-tracks page views, clicks, and time on page; and a REST API that accepts custom events from your backend with your workspace API key. Every user's behavior, scored and staged, regardless of where the event originated.
The script tag works with static HTML, React, Next.js, Vue, SvelteKit, Angular, or anything else that runs in a browser. SPA route changes are auto-detected.
Add the script tag to your root layout or _document.tsx. Call ccrm.identify() inside a useEffect after auth resolves. Route changes tracked automatically.
Load the widget in your app.vue or a plugin. Call identify() in the onMounted lifecycle hook after session is confirmed.
Paste the script tag before </body>. Echo the user ID and email from your session into the identify() call. Done.
Add the snippet to your base layout. Use the page store or route lifecycle to call identify() after session hydrates.
Payment processed, export completed, team member invited — these happen on your server. The REST API brings them into the same user timeline as the front-end behavior.
Call POST /api/track from your payment_intent.succeeded handler. ConversionCRM moves that user to Paid and removes them from all future lifecycle email immediately.
The API accepts JSON over HTTPS with your api_key as a bearer token. Works from any server language — no SDK required, though community wrappers exist.
Works from AWS Lambda, Vercel Edge Functions, Cloudflare Workers, or any other serverless runtime — a single fetch call is all you need.
Use the Webhook action in Zapier or Make to send events from CRMs, form tools, or payment processors into ConversionCRM without writing code.
ConversionCRM ships its own sending infrastructure via Resend. Or bring your own SMTP — switch takes 30 seconds in Settings.
Paste your app-specific password and sending address. Emails land from your real Gmail address; replies come back to you directly.
SMTP credentials from your SES verified domain. Full control over sending reputation, bounce handling, and compliance headers.
Both support SMTP relay. Use your Postmark stream or SendGrid API key as SMTP credentials and sending is immediate.
Microsoft 365 SMTP works with OAuth app passwords. Emails come from your company address and live alongside your other Outlook mail.
Yes — send a server-side event when a payment succeeds and ConversionCRM moves that user to the Paid stage and excludes them from all future lifecycle email. One REST call from your webhook handler is all it takes.
Yes. The script tag works on any web app including React, Next.js, Vue, and SvelteKit. SPA route changes are tracked automatically — no extra code for navigation events.
Yes. The REST API accepts server-side events using your workspace API key. Any server language works: Node.js, Python, Ruby, Go, or a serverless function.
You can send Segment track() and identify() events to ConversionCRM via the REST API from a Segment function or webhook destination. There is no native Segment connector yet — it is on the roadmap.
By default ConversionCRM sends via its own Resend-backed infrastructure. You can also provide any SMTP credentials — Gmail, Outlook, Amazon SES, Postmark, SendGrid — and emails send from your domain.
If it runs in a browser or has a backend, it integrates. Install in 3 minutes.
Free plan · no card · 3-minute install