Send events to your own system
A custom webhook sends a JSON event to an HTTPS endpoint you control. It does not need an advertising pixel ID.
When to use this
Use this when a developer or automation system needs to receive Snackle events. Standard advertising setup does not need a webhook.
Where to find it
Models → select model → Conversion tracking → Custom webhook.
What to copy and where to find it
HTTPS endpoint: Get the receiving URL from the service you are connecting, or ask your developer to create one. It must be a public HTTPS endpoint that accepts POST requests.
Signing secret: Optional: choose a strong random secret and configure the same value in Snackle and the receiving system to verify incoming requests. Leave blank for unsigned delivery.
How it works
The JSON includes schemaVersion, deliveryId, eventId, eventType, eventTime, model, page, source, campaign, and purchase data when applicable. Page and campaign values may be absent or null.
When a secret is configured, developers can verify x-snackle-signature against HMAC-SHA256 of the x-snackle-timestamp value, a dot, and the exact raw JSON request body. The signature header starts with v1=. Validate timestamp freshness and use deliveryId to avoid processing duplicates.
Enable Custom webhook in the link editor’s Conversion tracking settings after saving the model connection. Without a signing secret, requests omit the signature and timestamp headers.
Example: verify the connectionYour developer sees eventType snackle.test in the receiver log and confirms the signature is valid. That proves the test reached your receiver; it does not demonstrate that live link delivery is enabled.
How to use it
- Prepare the receiving endpoint and its signature verification.
- Enter the HTTPS endpoint and signing secret in Snackle, then Save.
- Click Test. Snackle sends a snackle.test event to that endpoint, signed if a secret is configured.
- Check the receiving service’s logs and Snackle’s result. The endpoint should accept the POST and return a successful response promptly.
- Before relying on live delivery, verify that the relevant link is actually connected to the webhook destination.
Good to know: Keep the signing secret private. A webhook URL from another tool is only suitable if that tool can accept Snackle’s request format and handle authentication appropriately.