Connect CheckoutChamp to Nevian

Time needed: about 10 minutesLast updated:

Connect CheckoutChamp so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.

What you need

  • A CheckoutChamp account with permission to configure notifications.
  • An active Nevian plan and an owner, admin or member role. Viewers cannot connect integrations.
  • Keep the checkout and Nevian tabs open side by side.

Steps

  1. In Nevian, open Integrations → Add integration (Connect provider in an empty workspace), choose CheckoutChamp and click Next with the platform open in another tab.

    Drawing: Connect CheckoutChamp. 1 · Open platform: Have your account open in another tab; 2 · Copy the URL: Next creates your private connection URL
  2. Copy the complete Webhook URL. Keep it private and leave this window open while you configure CheckoutChamp.

    Drawing: Connect CheckoutChamp. Webhook URL: https://track.example.com/wh/checkoutchamp/••••••••; Webhook token: Required account fields are saved with Next
  3. In CheckoutChamp, open ADMIN → EXPORTS, click the green +, name your profile and choose Postback. Edit the created profile.

    Drawing: CheckoutChamp · webhook configuration. Export type: Postback; Postback URL: Paste the Nevian URL without extra parameters; Field Mappings: Use the mappings below
  4. Paste the URL into Postback URL and add the field mappings below. Save, return to Export Profiles, then add Profile Routing for your campaigns and all the listed customer types.

    Drawing: CheckoutChamp · delivery settings. Destination: Your private Nevian Webhook URL; Scope: The products and events described in this step
  5. Return to Nevian, if you use the optional token, enter Webhook token and click Next to save it before sending an event. Use the same value configured for this webhook; for a token you generate yourself, use that exact value in both places. Leave an optional token empty in both places if you do not use it.

    Drawing: Connect CheckoutChamp. Webhook token: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link
  6. CheckoutChamp does not export test-card orders and exports run about every 15 minutes. Verify the next authorized real order, or use an isolated workspace and pixel test mode before a controlled paid test; refunding later does not undo an already-sent ad event. Back in Nevian, look for Connected, then click Done.

    Drawing: Connect CheckoutChamp. Connection: Connected; Last event: Received just now

The optional token is a long random value you choose. Add static fields header:httpMethod = POST and, if you configured a token, header:X-Webhook-Token = that same token.

Export NameField
order_idorderId
order_statusorderStatus
triggercustomerType
order_totalorderTotal
total_pricetotalPrice
shippingtotalShipping
has_upsellshasUpsells
currencycurrencyCode
emailemailAddress
phonephoneNumber
first_namefirstName
last_namelastName
ipipAddress
product_idproductId
product_nameproduct1_name
original_order_idoriginalOrderId
chargeback_datechargebackDate
orderCustomFieldsorderCustomFields

Route New Sale, Upsell, Recurring Order, COD Pending, Decline, Rebill Decline, Full refunds, Partial refunds and Chargeback. Upsells within one order form one aggregated upsell line. Full refunds change the whole order; partial refunds are logged.

Check that it works

  • Open Logs → Webhooks and confirm the provider, order ID, event and result. A delivered webhook can be logged without creating a sale when the event is informational.
  • Add cc_custom_btk={btk} to the link from your page to the first CheckoutChamp page. The Nevian script fills in the visit ID; include orderCustomFields in the export so it comes back.

Problems

Waiting for the first event…

Check the complete URL, event subscriptions and product scope. If you rotated the integration key, replace the URL in the provider too.

The call was rejected

Read the reason in Logs → Webhooks. Check the secret when one is configured, then resend the original event after fixing the configuration.

No matching click

Check the click ID instructions above on a real ad visit. A provider test usually has no ad click; that alone does not mean delivery failed.

Still stuck? Write to [email protected].

Images are our own drawings and configuration diagrams, not screenshots. Use the current values from your account; the examples contain no live credentials.