Destinations

Custom HTTP destination

Last updated 2026-05-05

Overview

Custom HTTP destinations POST JSON to your internal automation, enrichment services, or niche SaaS tools. You control headers, exponential backoff, and optional HMAC signing for authenticity.

Steps

Choose Destinations → HTTP → Custom and set the base URL plus auth header template.
Define the JSON template with mustache-style placeholders pulling from the normalized event.

{
  "type": "tracklayer.forward",
  "user": "{{ userId }}",
  "event": "{{ event }}",
  "props": {{ propertiesJson }}
}

Optional: enable HMAC-SHA256 with a shared secret; TrackLayer adds X-TrackLayer-Signature and X-TrackLayer-Timestamp.
Dry-run a sandbox event and inspect your receiver logs for schema fit.

Troubleshooting

429 / backoff: Tune concurrency; TrackLayer honors Retry-After when present.
TLS failures: upload your custom CA if terminating TLS on-prem.
Large payloads: slim templates—attach deep objects only when the downstream API requires them.