Usermaven
Dark mode

Send events to Usermaven with Zapier

What you'll build: a Zap that turns anything happening in your other tools, a closed CRM deal, a signed contract, a qualified lead, into a Usermaven event. Time: about 10 minutes. You'll need: a Zapier account with access to Webhooks by Zapier, and permission to create integrations in Usermaven.

If a tool isn't in the Event Sources catalog, Zapier is usually the fastest bridge. Any Zapier trigger, from thousands of apps, can send its data to Usermaven with a single Webhooks by Zapier action. No code, no developer.

Before you start

  • Know which moment you're tracking, and give it one clear event name (like deal_won or contract_signed). One Zap, one event, one source.

  • Check that the trigger app provides an email or user ID for the person, that's how Usermaven matches the event to someone.

  • If the trigger app has a stable record ID (deal ID, order number), plan to send it, it's your protection against duplicates when Zapier retries.

Step 1: Create the source in Usermaven

  1. Go to Events → Event sources and click New event source.

  2. Pick Zapier from the catalog.

  3. Name the source (for example, HubSpot deals won) and click Create webhook URL.

  4. Copy the URL and leave this page open, Usermaven is listening for your test.

image.png

Step 2: Build the Zap

  1. In Zapier, create a Zap with your trigger app and event (for example, Deal stage changed to Won).

  2. Add an action: Webhooks by Zapier → POST.

  3. Paste your Usermaven webhook URL and set Payload Type to json.

  4. Add data fields from the trigger:

Field

Value

Why

email

The contact's email

Matches the event to a person

user_id

Your app's user ID, if you have one

The strongest possible match

amount

Deal or order value

Revenue in your reports

currency

Three-letter code like USD

Keeps revenue accurate

external_id

Deal or order ID

Prevents duplicates on retries

occurred_at

When it happened

So the event lands at the right time

Step 3: Test the Zap

Click Test step in Zapier. Back in Usermaven, the wizard shows "Test event received — review it below" with exactly what Zapier sent.

Step 4: Map, review, and activate

  1. Map the detected fields, email or user ID for identity, your revenue and time fields, and the external ID.

  2. Set a fixed event name like deal_won rather than mapping one from the payload, it keeps your reporting predictable.

  3. Check the revenue preview: Zapier sends amounts as-is, so 129.99 should stay 129.99. Only pick a minor-units transform if your app genuinely sends cents.

  4. Click Preview event, confirm it looks right, then Save source and activate.

  5. Finally, turn the Zap on in Zapier.

image.png

Verify it's working

Trigger one real occurrence (or run the Zap's test again). In the source's Event log, you should see an Accepted delivery. Then open Events activity, filter by this source, and confirm the event shows the right person and revenue.

If the event shows Identity unresolved, the email matched more than one person in Usermaven. Add a stable user_id or anonymous_id field to the Zap, Usermaven will never guess between people.

If something goes wrong

  • Duplicate: Zapier re-sent a record you've already counted. That's the External ID working. Only change an External ID if it's genuinely a different conversion.

  • No usable identity found; the Zap ran but the identity field was empty for that record. Check the trigger data.

  • Event time could not be parsed, send ISO 8601 format, like 2026-07-01T12:30:00Z.

  • Rate limited, Zapier will honor the retry automatically. Don't create a second source to "help" — you'll get duplicates.

More outcomes and fixes: Event Sources Troubleshooting.


Was this article helpful?