Skip to main content
Connect a video event to anything Zapier or Make can reach: a spreadsheet, a Slack message, an SMS, your own CRM if it is not ActiveCampaign or GoHighLevel. Both run on the same signed webhook machinery documented on the Webhooks page.

​
Zapier

Zapier subscribes and unsubscribes itself. You never copy a webhook URL by hand.
1

Mint an API token

In TrackPlay, go to Settings → API tokens and create one with the webhooks:write scope. See Authentication.
2

Start the Zap

In Zapier, search for TrackPlay as your trigger app.
3

Connect the account

Paste the token into the API Key field on Zapier’s connection screen.
4

Pick a trigger

Choose one of the triggers below.
5

Test the trigger

Zapier pulls a sample payload to build your field mapping. If no live event has fired yet, it uses a representative sample instead of failing the setup.
Zapier’s REST-hook subscribe call creates a normal TrackPlay webhook subscription scoped to that one trigger, with its own signing secret. Turning off or deleting the Zap removes it the same way deleting any other webhook would.

​
Available triggers

Each trigger maps 1:1 to a TrackPlay webhook event. New Conversion is conversion.created, Play Milestone Reached is play.milestone, and so on. See Webhooks for the full event list, including two that have no Zapier trigger yet: lead.hot and lead.known_customer.
Every event carries the same envelope: id, event, workspace_id, created_at, and a data object specific to the trigger. Use Zapier’s own field-mapping screen after the test step to see exactly which data fields your trigger sends.

​
Make

Make does not have a native TrackPlay app. Use its Webhooks module against a TrackPlay webhook subscription.
1

Add a Custom Webhook module

In your Make scenario, add Webhooks → Custom webhook and copy the URL Make gives you.
2

Create the webhook in TrackPlay

Go to Settings → Webhooks, click New webhook, and paste Make’s URL. Pick the events you want, or All events.
3

Save the signing secret

Shown once. Copy it if you plan to verify the X-Trackplay-Signature header (see below).
4

Send a test

Click Send test in TrackPlay, then Run once in Make to capture the payload shape for the rest of your scenario.
Make sees the event before your webhook secret has ever mattered: subscribing and testing works with no verification at all. Verify the signature only if your scenario needs to trust that a payload really came from TrackPlay, not only that something posted to the URL. The header format and the HMAC steps are on the Webhooks page.

​
When it does not work

The token needs the webhooks:write scope specifically. A token minted for videos:read or another scope authenticates for other API calls but is rejected here.
Confirm the event has actually happened since you connected. A play or a sale from before the Zap was turned on does not replay. For New Conversion specifically, confirm the underlying cart integration or Conversions API call shows conversions landing at all; a Zap cannot trigger on an event TrackPlay never recorded.
Check Settings → Webhooks → Recent deliveries in TrackPlay for the subscription’s HTTP status. A Make webhook URL that expired or was regenerated on Make’s side returns a 404 that TrackPlay logs and keeps retrying with backoff for up to 8 attempts before marking that one delivery dead. The subscription itself stays active regardless, so fix the URL in TrackPlay (delete the old webhook, add the new one Make gives you) as soon as you notice, rather than waiting for TrackPlay to notice for you.
Reconnecting mints a fresh REST-hook subscription; the old one is orphaned in TrackPlay’s webhook list until Zapier’s own cleanup unsubscribes it, or you remove it by hand from Settings → Webhooks.