Webhook API

If you prefer to send conversion events from your server rather than the browser, you can POST directly to the Pruuv webhook endpoint. This is useful when you already have lead data in a CRM or backend system and want to forward it to Pruuv without adding JavaScript to your pages.

Authentication

All requests must include a Bearer token in the Authorization header. The token is the Webhook Token shown alongside each funnel stage in Connections > Funnel Webhooks.

Endpoint

POST https://app.pruuv.io/api/webhooks/funnel/{stageId}
Authorization: Bearer YOUR_WEBHOOK_TOKEN
Content-Type: application/json

Example request

curl -X POST https://app.pruuv.io/api/webhooks/funnel/YOUR_STAGE_ID \
  -H "Authorization: Bearer YOUR_WEBHOOK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "reference":    "CRM-REF-001",
    "utm_source":   "google",
    "utm_medium":   "cpc",
    "utm_campaign": "brand-search",
    "gclid":        "EAIaIQobCh...",
    "revenue_value": 250,
    "currency":     "GBP"
  }'

Payload reference

All fields are optional except reference.

Responses

Deduplication and enrichment

Events are deduplicated on the combination of stage_id + reference (+ item_reference if present) using a unique index — this is a permanent deduplication, not a time-window. Sending the same reference twice will never create two rows. This makes it safe to retry on network errors.

However, if the second event arrives with new data that the first event lacked — for example, a CRM posts UTMs first and the Pruuv Pixel fires moments later with fbc/gclid/ttclid — Pruuv performs an enrichment merge: it fills in any NULL fields on the existing row from the new payload, without overwriting anything already stored. The response is still { received: true, duplicate: true }, but the row now has both datasets.

Enrichable fields: fbc, fbp, gclid, wbraid, gbraid, ttclid, msclkid, click_timestamp, email_hash, phone_hash, user_agent, revenue_value, currency, identity_user_id, first_touch.

Integration paths compared