Connect CheckoutChamp with postback profiles

How the connection works

CheckoutChamp posts each partial and completed order to a private address that belongs to one campaign. CheckoutChamp cannot sign its posts, so a secret header in the profile proves a post came from you. No API key is involved, and ACR writes nothing back to CheckoutChamp.

Connect it in ACR

1. In Integrations, find CheckoutChamp under Checkout platforms, press Set up, then Connect CheckoutChamp. ACR creates the secret.
2. Create a campaign and choose CheckoutChamp under Where leads come from. Its lead source step shows this campaign's address and the secret next to the steps below.

Build the two profiles

These steps happen in CheckoutChamp under Admin, Exports, with a merchant admin login.

1. Add an export profile of type Postback named ACR Partial Orders, with the campaign's address as the Postback URL. Leave Export Delay empty: anything there delays the first message.
2. Add four mappings with Field set to Static: header:Content-Type = application/json, header:httpMethod = POST, header:X-ACR-Secret = the secret, and acr_event = partial.
3. Add the data mappings below, Export Name on the left and CheckoutChamp's field on the right. Export Names must match exactly, including case.
4. Duplicate the profile as ACR Completed Orders and change acr_event to completed.
5. In Profile Routing, route ACR Partial Orders with customer type Partial and ACR Completed Orders with customer type New Sale, leaving products and campaigns on All. The Abandoned Cart customer type sends nothing.
6. Back in ACR, press Start reading, then publish the campaign and switch its trigger on.

unique_id     =  orderId
order_date    =  dateCreated
first_name    =  firstName
last_name     =  lastName
email         =  emailAddress
phone         =  phoneNumber
country_code  =  country
final_price   =  orderTotal
currency      =  currencyCode
cart_link     =  salesUrl
customer_id   =  customerId

Without the completed profile, nothing tells ACR that a shopper paid, and the agent keeps contacting people after they buy.

Timing and what is skipped

• A partial order counts as abandoned after 45 minutes by default. CheckoutChamp exports about every 15 minutes, so a shopper hears from the agent about an hour after leaving.
• A new profile replays the last day of orders. ACR records them, but a partial order more than two hours old starts nothing, so the first runs can take a few hours to appear.
• ACR reads order_date in the connection's time zone, which is the store's by default, unless the date carries its own offset. A partial order whose date ACR cannot read is skipped.
• A partial order without a phone number starts nothing.

For consent, map your opt-in field to the Export Name contact_opt_in. ACR reads true, 1, yes or y as an opt-in to texts and email and anything else as an opt-out, under the source CheckoutChamp contact opt-in.

This connection has been tested against simulated CheckoutChamp posts only.