Connect Omnisend with automation webhooks

What you need

The Webhook block these automations use needs a paid Omnisend plan. You also need an Omnisend API key with access to contacts. ACR makes one read with it to check it works; after that, Omnisend's automations send each event to ACR and ACR reads nothing from Omnisend.

Connect and build the two automations

1. In Integrations, find Omnisend under Email and SMS platforms, press Set up, paste the key and press Test and save. The panel then shows a private address and a secret value. Only admins and owners see the secret.
2. In Omnisend, create an automation that starts on the started checkout event. Add a Webhook block as its first step, before any wait. Set the method to POST and paste the address.
3. In the same block, add a header named X-ACR-Secret with the secret value.
4. Paste the checkout body the panel shows. It sends acr_event set to checkout_started, with the cart id, cart link, total, currency, and the contact's email, phone and name.
5. Create a second automation on the placed order event, with the same address and header, and paste the order body.
6. Back in ACR, press Start reading and confirm.

How ACR reads each post

• Each checkout post restarts the idle clock. The checkout counts as abandoned after 30 minutes without another post, unless you change the wait on the trigger.
• An order stops outreach to that shopper. ACR matches it to the checkout by its cart id, and credits it to a campaign when the shopper used its code or engaged with the agent first.
• A tag Omnisend could not fill arrives as literal text, such as [[contact.phone_number]], and ACR treats it as empty. A post with no cart id or order id is ignored, and a checkout with neither phone nor email starts nothing.
• A post without the right secret is refused, and the panel counts refusals from the last day.

Consent from Omnisend

The bodies ACR gives you carry no consent. If you add email_consent or sms_consent to them, ACR records true as an opt-in and any other value, an unfilled tag included, as an opt-out, under the source Omnisend subscription status. Without them, the default consent rule lets no calls, texts or email reach these shoppers. See Consent.

Opt-outs do not reach Omnisend

The connection shows a Log activity in Omnisend switch for passing opt-outs back as unsubscribes. Omnisend's posts carry no Omnisend contact id, so ACR has no contact to update, and nothing is sent to Omnisend when a shopper opts out. Unsubscribe them in Omnisend as well.

This connection has been tested against a simulated Omnisend API only.