Send SourceTrack conversion events to Zapier or Make through outbound webhooks. SourceTrack posts a signed JSON payload to a URL you give it, and your Zap or scenario takes it from there.
There is no SourceTrack app in the Zapier or Make directories. The connection is a plain webhook to a catch-hook URL, so anything that can receive a JSON POST can use it.
What SourceTrack sends
By default a webhook receives conversion events: conversion.created, conversion.offline and conversion.refunded. A conversion payload contains:
- The conversion: type, value and currency (each
nullwhen not reported, never a made-up zero or default currency), order id and a unique event id you can use to de-duplicate. - The visitor: the anonymous visitor id and the user id, if your site set one.
- Attribution: source, medium, campaign, content, term, channel, AI source, and ad click ids.
- The page: page URL and referrer, with personal data removed from the URLs.
- Your custom properties from the conversion.
If the visitor sent Global Privacy Control or Do Not Track, the payload is still sent to your endpoint, but with the ad click ids removed and a privacy flag added.
Lead and contact events (lead.created, contact.created) are opt-in per webhook. They carry visitor ids and an event id. The email address is added only if you switch on Include the email address for that webhook.
Every request has two headers: X-SourceTrack-Event with the event name and X-SourceTrack-Signature with a timestamped HMAC-SHA256 signature of the body, made with your webhook’s secret. Check it on your side if the endpoint is not private.
What SourceTrack does not do
- It does not send customer names, phone numbers or company names with conversion events.
- It does not wait for your endpoint to finish your workflow. It only checks that your endpoint accepted the request.
- Delivery is retried a fixed number of times; after the retries below, it is marked as failed.
Step-by-step setup
Step 1: Create a catch hook
In Zapier, add a Webhooks by Zapier trigger and choose Catch Hook. In Make, add a Custom webhook module. Copy the URL it gives you.
Step 2: Add the webhook in SourceTrack
- In SourceTrack, open Integrations and find the Webhook Conversion Adapter section.
- Add a webhook with your URL. The URL must be a public HTTPS address.
- Choose which events to send, and optionally add conditions such as conversion type or value.
How many webhooks you can add depends on your plan. Multiple webhooks, event selection and conditions are rolling out behind a setting that is off by default, so you may see a single webhook field instead. A free plan has a monthly cap on deliveries.
Step 3: Send a test and map the fields
Use Send test in SourceTrack. The test payload is sample data and carries "test": true in its properties. In Zapier or Make, open the received sample and map its fields to your next step.
How delivery and retries work
SourceTrack tries a delivery up to three times in a row, with a short pause between tries. A client error such as a 400 or 404 is not retried, because it would fail the same way. If the first round fails, a background worker tries again after about 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. After that the delivery is marked dead, and an owner or admin can replay it from the dead-letter list.
Common problems and fixes
- Nothing arrives. Check that the URL is public HTTPS and that the webhook is active. A private or local address is refused.
- Duplicates in your Zap. Retries can deliver the same event twice. Use the event id to de-duplicate.
- Signature check fails. Sign the exact raw request body, prefixed by the timestamp and a dot, with the webhook’s secret. Rotating the secret in SourceTrack changes it.
- Leads have no email. The email is added only when you opt in per webhook.
Related guides
Frequently Asked Questions
Can Zapier or Make send conversions into SourceTrack?
SourceTrack has an inbound webhook endpoint and an API for conversions, which a Zap or scenario can call with an HTTP request. There is no ready-made Zapier or Make app for it. See the REST API reference.
How fast are webhooks sent?
SourceTrack sends a webhook after it records the conversion. It does not publish a delivery-time figure.
What if Zapier or Make is down?
Failed deliveries are retried on the schedule above, and a delivery that still fails can be replayed by an owner or admin.
