Connect Next Commerce to Nevian

Time needed: about 10 minutesLast updated:

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

What you need

  • A Next Commerce 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 Next Commerce and click Next with the platform open in another tab.

    Drawing: Connect Next Commerce. 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 Next Commerce.

    Drawing: Connect Next Commerce. Webhook URL: https://track.example.com/wh/nextcommerce/••••••••; Webhook secret: Required account fields are saved with Next

  3. In Next Commerce, open Settings → Webhooks → Create Webhook.

    Drawing: Next Commerce · webhook configuration. Settings: Webhooks; Target URL: Paste the Nevian URL; Events: order.created · order.updated · dispute.created · dispute.updated

  4. Use the full URL and subscribe to order.created, order.updated, dispute.created and dispute.updated. Copy the webhook signing secret into Nevian before testing.

    Drawing: Next Commerce · delivery settings. Destination: Your private Nevian Webhook URL; Scope: The products and events described in this step

  5. Return to Nevian, enter Webhook secret and click Next to save it before sending an event. Copy it from the same account and webhook you just configured.

    Drawing: Connect Next Commerce. Webhook secret: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Create a test-card order. Test orders are excluded from regular totals; use the webhook’s Detail action to inspect delivery. The order and dispute updates should refer to the original sale. Back in Nevian, look for Connected, then click Done.

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

Use Actions → Update when changing the endpoint or event subscriptions. Subscription charges are tracked, but this connection does not calculate MRR.

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.
  • Put attribution_metadata.btk on the order, or use clickid={btk} on the campaign link from your tracked page. This connection also recognizes legacy 29 Next payloads.

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.