Send checkouts from Zapier or Make

Set up the connection and campaign

1. In Integrations, find Zapier or Make under Automation tools, press Set up, then Connect Zapier or Connect Make. Neither needs a key; ACR creates a secret for the connection.
2. Create a campaign and pick Zapier or Make under Where leads come from, in Automation tools and files. Its lead source step shows the campaign's Trigger URL and the secret.
3. Build the Zap or scenario as below.
4. Press Start reading on the connection, publish the campaign and switch its Checkout abandoned trigger on.

Webhooks by Zapier, which these steps use, needs a paid Zapier plan.

In Zapier

Add a Webhooks by Zapier action and choose POST. Paste the campaign's Trigger URL, set Payload Type to JSON, and under Headers add X-ACR-Secret with the secret. Under Data, map your trigger's fields to the keys below.

In Make

Add HTTP, Make a request. Paste the Trigger URL, choose POST and send the body as JSON, with a header X-ACR-Secret set to the secret.

To sign instead, send X-ACR-Signature as t=<unix seconds>,v1=<signature>, where the signature is the hex HMAC-SHA256 of <t>.<body> keyed with the secret. A signature whose time is more than 5 minutes off is refused.

The keys to send

acr_event      checkout/updated, or checkout/completed when they buy
unique_id      your checkout or cart id
email
phone          in international format, such as +14155550123
first_name
last_name
final_price
cart_link
consent_sms    true or false, from your own opt-in
consent_calls
consent_email

Send checkout/updated each time the checkout changes and checkout/completed once when the shopper buys, with the same unique_id. Each update restarts the 30-minute wait, and the completed event stops outreach and records the order. A phone number or an email is needed.

Blank fields are ignored. The consent keys take true, yes, 1 or subscribed as an opt-in, and false, no, 0 or unsubscribed as an opt-out, recorded as Consent sent with Custom API events, including from Zapier and Make. The other fields of the Custom API, such as country_code and context, work the same way.

What ACR answers

A request without the right secret or signature gets 401, and the connection counts it. While reading is off, or the trigger is off, the URL answers 200 and stores nothing. Other answers match the Custom API's.

The lead source step also shows a Field mapping box on these campaigns. ACR does not apply it to Zapier or Make events, so send each field under the key above.

Start a Zap or scenario from ACR

In Zapier, use a Catch Raw Hook trigger, which passes headers through. In Make, use a Custom webhook with Get request headers switched on. Add its URL under Webhooks in ACR. Each delivery has an X-ACR-Signature header you can check with your webhook secret.

Both connections have been tested against simulated requests only.