Connect Yampi to Nevian
Connect Yampi so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.
What you need
- A Yampi 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
In Nevian, open Integrations → Add integration (Connect provider in an empty workspace), choose Yampi and click Next with the platform open in another tab.

Copy the complete Webhook URL. Keep it private and leave this window open while you configure Yampi.

Open the webhook configuration for your Yampi store. The public API documentation describes webhooks, but the current dashboard route is not established here; use Yampi support if your account does not expose that configuration.

Subscribe to
order.created,order.paidandorder.status.updated. Paste the URL and, if you use a webhook secret, save the same secret in both accounts.
Return to Nevian, if you use the optional token, enter Webhook secret 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.

Send a controlled order and verify its order ID and status in Nevian. Keep sample orders in an isolated workspace with pixel test mode enabled unless the event carries a recognized test marker. Back in Nevian, look for Connected, then click Done.

Paid orders become sales; status changes update the same order. Cancellation after payment is treated as a refund. Yampi’s metadata guide explains which checkout data survives in order notifications.
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.
- Yampi checkout links are not decorated automatically. Install the tracking script and use its documented buyer-identification flow when your checkout can provide that identity; never send a second purchase from the thank-you page for the same order.
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.