PopzIQ
One customer-journey system

Make customer journeys pop.

Forms, popups, email, leads and automations built around one customer record. A submission becomes an event, the event becomes a trigger and nothing ever needs to sync.

Create your workspaceSee how it works

Five minutes from signup to your first published form. That is the bar we build against.

  • 32

    event types recorded today

  • 9

    routes on the public /v1 API

  • <30KB

    gzipped embed loader

  • 5 min

    from signup to first capture

One customer record

Every module reads the same person

A form submission, popup conversion, email click, lead update and payment are events on the same person. Forms, email and leads never keep their own copy of a customer, so there is nothing to sync, reconcile or explain.

Open a profile and the whole story is already there: identity, source, consent, lead status and a timeline you can read top to bottom.

  • One profile

    Identity resolved on normalized email.

  • No copies

    No module keeps a second customer table.

  • Append only

    Corrections are new events, never edits.

  • Consent on board

    Status, source and timestamp from day one.

M

Mia Torres

mia@espresso.studio · via exit popup

  1. Form submitted
  2. Contact created
  3. Welcome email delivered
  4. Email opened
  5. Pricing page clicked
  6. Customer replied
  7. Assigned to Sarah
  8. Lead moved to Qualified
  9. Payment completed
  1. Inline
  2. Popup
  3. Slide-in
  4. Floating bar

Capture

Forms that pop

Build a form once. Display mode is a setting, not a second product: the same form ships as an inline embed, a popup, a slide-in or a floating bar. Exit intent, scroll depth and URL rules decide when it appears.

One builder, one submission pipeline, one place to read the results. Tweak a field and every surface updates without a deploy.

The data model

Everything is an event

A submission, a new contact, a consent checkbox, a delivered email: each one is an append-only row in one stream, tied to one person. Nineteen kinds of event are recorded today and every part of the product reads the same log.

That is why nothing in PopzIQ syncs. Analytics counts the rows, automations trigger on them and webhooks relay them to your stack. One write, three outcomes, zero connectors.

  • Analytics

    Every number traces back to a row.

  • Automations

    Any event can become a trigger.

  • Webhooks

    Your stack hears it signed, in order.

The whole loop

From first signal to next action

The common customer-growth workflow runs on one event stream. No exports, no glue code and no five tools pretending to be one.

  1. 01

    Capture

    A form, popup or API call collects the first signal.

  2. 02

    Understand

    The signal lands on one profile with source and consent.

  3. 03

    Communicate

    A welcome email goes out from the same record.

  4. 04

    Automate

    Events become triggers. Logic runs without syncing.

  5. 05

    Convert

    A lightweight pipeline moves the lead to won.

  6. 06

    Learn

    Every number traces back to a real moment.

The platform

The whole map, honestly labeled

Capture, email, leads and automations are live in production today, all on the same customer record. Payment forms are the one thing still to come, and this map says so rather than quietly implying otherwise.

Developers

An API you can trust with production email

Every send is traceable from API request to delivery event. Test and live keys, writes you can safely retry and signed webhooks you can verify in one line.

send-welcome.ts
import { PopzIQ } from "@popziq/node";

const popz = new PopzIQ(process.env.POPZIQ_API_KEY);

await popz.email.send({
  from: "hello@espresso.studio",
  to: "mia@espresso.studio",
  subject: "Welcome",
  html: "<h1>You're in</h1>"
});
POST https://api.you.dev/hooks
Popziq-Signature: t=1787172127,v1=9f2ac1…

{
  "type": "email.delivered",
  "contact": "ct_9m4k2",
  "email": "em_7h2df",
  "occurred_at": "2026-08-20T09:42:07Z"
}
API keysTest and live modesSigned webhooksEvent catalogIdempotency
Read the developer overview: every event, every /v1 route and the embed

The seams

Four tools, one action each

Each of those products is genuinely good at its job. The cost is the seams between them: four subscriptions, four copies of your customer and glue code you now maintain.

  • A form builder

    an embed for the form on your site

    Build the form once and publish. The embed is one script tag under 30KB.

  • A popup tool

    its own targeting rules, on its own subscription

    Flip the same form to popup. Exit intent, scroll depth and URL rules are settings.

  • A CRM sync

    a connector pushing submissions into contact records

    Every submission already resolves to one contact. There is nothing to sync.

  • A webhook relay

    middleware fanning your events out to other tools

    Subscribe an endpoint. Every event arrives signed, retried and logged.

One customer record underneath means the popup conversion, the welcome email and the webhook are the same story, not three reports that disagree.

Security and trust

Boring where it counts

Trust is a foundation here, not a compliance sprint before the enterprise deal. Every promise below is live today and covered by tests that run before anything ships.

  • Your workspace stays yours

    Nothing is shared between workspaces. Every request answers only for the workspace it signed in to. Anything outside it comes back as not found.

  • Roles that hold

    Give each teammate a role and every read and write is checked against it. A missing permission is a refusal, not a warning you can click past.

  • Signed webhooks

    Every delivery is signed so your endpoint can prove it came from us and arrived untouched. Anything older than five minutes is rejected.

  • An audit trail nobody can edit

    Every action is written once and can never be changed or deleted, not by us and not by an admin. Corrections arrive as new entries, so the history you read is the history that happened.

  • Consent and suppression built in

    Consent status, where it came from and when it was given sit on every contact from day one. Unsubscribes and suppressions are honored on every send.

  • Export and deletion that stick

    Take your whole workspace out in one click: contacts, submissions and history. Delete a person and they stay deleted, so a later import cannot quietly bring them back.

Read how it is built

Pricing

Three plans, no riddles

These are the plans in the product today. Every workspace starts on Free with no card, and you can move up from Settings the day you outgrow it.

  • Free

    For trying the whole loop on a real project.

    • Forms with every live display mode
    • Contacts with the full timeline
    • The complete event stream
    • Email, leads and automations
    • Test API keys
    • CSV import with a migration report
    Start free
  • Most complete

    Starter

    For a business capturing customers every day.

    • Everything in Free
    • Live API keys and signed webhooks
    • Higher capture limits and 5 seats
    • Workspace export
    • Email support
    Start free

  • Growth

    For teams that outgrow the starter limits.

    • Everything in Starter
    • Higher limits across the board
    • 15 seats with roles
    • First access to new modules
    • Priority support
    Start free

No card to start, no trial clock and no surprise emails. See what is in each plan.

Questions

Asked before you had to

What will PopzIQ cost?

Three plans: Free, Starter and Growth. Free carries 500 contacts, 1,000 submissions a month and 2 seats, and it stays genuinely usable: you run the whole loop on it, not a seven-day demo of it. Starter and Growth raise those limits and their prices are shown in Settings before you are asked to pay.

Who owns my data and can I get it out?

You do, completely. A one-click export takes your whole workspace: contacts, submissions and the event stream. Contact deletion leaves a tombstone, so a later import cannot quietly bring a deleted person back.

Will the embed slow my site down?

The loader ships under 30KB gzipped, loads async and lazy-loads the renderer only when a form is about to show. One script tag, no dependencies, no layout shift while it loads.

Where does PopzIQ stand on GDPR?

Consent status, source and timestamp are first-class columns on every contact, recorded from the form checkbox onward. Unsubscribes are honored on every send, every action lands in an audit trail nobody can edit and deletion plus export are built in, not a support ticket.

Can I migrate from another form or email tool?

CSV import is live and ends with a migration report that names what was imported, mapped, skipped or needs review. Nothing is silently dropped. Direct importers for specific tools arrive later and run through the same pipeline.

Is there a real API?

Yes. It is the same engine the app uses. /v1 covers forms, submissions, contacts and events with scoped test and live keys, idempotency keys on writes and signed webhooks with a logged delivery history. Start at popziq.com/developers.

How finished is it, honestly?

Live in production: forms and display modes, contacts and the event stream, import and export, the developer platform, email with templates and broadcasts, the leads pipeline and automations. Payment forms are the one module still to come. You can sign up and use all of it today.

Get started

Start capturing today

Create a workspace, publish your first form and watch the events land on a real customer record. The free plan runs the whole loop.

Create your workspaceSee what is in each plan

No card to start. No trial clock. No newsletter and no spam.