Pro Feature

Webhooks

Push session and conversion events to any URL. Send attribution data wherever you need it, with no CRM plugin or form connector required.

What webhooks do

Webhooks let you send attribution data to external systems at the moment something happens. When a new session is logged, or when a conversion is recorded, a POST request goes out to the URL you configure, carrying the attribution data for that event as a JSON body.

This removes the dependency on a specific CRM plugin or form plugin connector. If your CRM, data warehouse, or automation tool accepts an HTTP POST, you can send attribution data there directly.

Session webhooks

A session webhook fires each time a new session is classified. The payload includes:

  • Session token
  • Channel (e.g. AI Referrer, Organic Search, Email)
  • Source domain
  • UTM values (source, medium, campaign) if present
  • Landing URL
  • Timestamp

Session webhooks are dispatched via the WordPress background task queue. They do not add latency to the page load that triggered them.

Conversion webhooks

A conversion webhook fires each time a conversion event is recorded. The payload includes all session fields above, plus:

  • Conversion type (e.g. woocommerce_order, cf7_submission, custom)
  • Real value and currency (if a monetary value was recorded)
  • Estimated value (if configured for this conversion type)
  • Conversion timestamp

Setting up a webhook

Go to Attribution → Webhooks and add a destination URL. You can configure separate URLs for session events and conversion events, or send both to the same endpoint. Each webhook can be individually enabled or disabled without deleting the configuration.

Payload format

All webhook payloads are sent as HTTP POST with Content-Type: application/json. The receiving endpoint should return a 2xx status to indicate successful receipt. Non-2xx responses are logged as failed deliveries.

Webhook questions

← Integrations Pro Features →