Integrations

How to use Zapier with VSL Max

Zapier works both ways: it receives events from VSL Max and sends sales from any checkout into VSL Max.

6 min read

Both directions

The Zapier card, in Settings › Integrations, has two tabs:

  • Send events: VSL Max notifies your Zap when there is a sale, a refund, a video becomes ready and other events. Use it to feed a spreadsheet, a CRM, Slack or anything else Zapier reaches.
  • Receive sales: a checkout that is not on our platform list sends the sale to VSL Max through a Zap, and the sale is attributed to the video.

Send events to Zapier

  1. In Zapier, create a Zap with the Webhooks by Zapier trigger, Catch Hook option. Zapier generates a URL.
  2. In VSL Max, open the Zapier card, Send events tab, and paste the URL into Catch Hook URL. Only URLs starting with https://hooks.zapier.com/hooks/catch/ are accepted.
  3. Give it a name (optional) and pick the events. If you don't pick any, the four sale events are used: sale approved, refund, chargeback and sale canceled.
  4. Click Connect Zap.
  5. Use Test to send a test event now. In Zapier it shows up as a sample so you can map the fields in the next steps of the Zap.

When you connect, VSL Max shows a signing secret once. In Zapier it is optional; use it if your Zap forwards the event to a server that verifies the signature. Events, body format and signature are the same as the generic webhook: see Generic webhook.

Available events: sale approved, refund, chargeback, sale canceled, video ready, low play balance and account suspended. You can connect up to 5 Zaps.

Receive sales through Zapier

Use this when your checkout is not on the Conversions platform list. It also works with Make and n8n.

  1. In Conversions, create a conversion with the Zapier platform (or Make, or n8n). The Receive sales tab has a shortcut for this.
  2. Enter your checkout domains (1 to 10). They tell the player which links on the page lead to the checkout and should carry the tracking key.
  3. Copy the conversion URL, shown after you save.
  4. In the Zap, use your checkout's trigger (sale approved, for example) and the Webhooks by Zapier action, POST, with the conversion URL.
  5. Map the fields listed below. The key comes from the tracking parameter your checkout returns with the sale.
  6. Link the conversion to the video, on the video screen. See Linked conversion.

The accepted body is compatible with VTurb's: if you are migrating, just change the URL in the Zap.

Accepted sale fields

  • Key (conversion_key or key): needed to attribute the sale to the video. Without it, the sale comes in unattributed.
  • Amount: required. In cents, as an integer, in order_amount_cents or amount_cents. As a decimal, with a dot or comma, in amount or value.
  • Currency (currency): three letters. Defaults to BRL.
  • Status (status, category or event): approved, paid, sale or purchase become an approved sale; refunded, chargeback and canceled are also accepted. Defaults to approved.
  • Order ID (order_id, transaction_id, sale_id or id): always map it. Without it, two sales with the same amount and date can be counted as one.
  • Date (order_created_at, occurred_at or created_at): ISO 8601 or epoch. Defaults to the time it was received.

Product name and buyer IP are accepted and discarded: VSL Max does not store the buyer's personal data.

If something doesn't arrive

  • The event doesn't reach the Zap: open the Zap's details in the list and check Latest deliveries. Each delivery shows the HTTP status and how many attempts were made.
  • The sale arrives without a video: the key is almost always missing. Check that the checkout domain is registered on the conversion and that the Zap sends the key field. See Tracking parameter.

More in this section