Connect Adoorei to Nevian
Connect Adoorei so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.
What you need
- A Adoorei 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 Adoorei 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 Adoorei.

In Adoorei, open Configurações → Webhook. Enter a name and paste the Nevian URL.

Use order-created, order-updated and payment-status notifications, including approved and refused orders. If you set TOKEN, copy it to Nevian before sending the real order; the registration ping only checks reachability.

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.

Create a controlled order and follow its payment change. Adoorei’s registration ping returning HTTP 200 does not prove that a sale has been received. Back in Nevian, look for Connected, then click Done.

Adoorei sends the optional token in X-Adoorei-hash. Use an isolated test workspace and pixel test mode for sample orders without a test marker.
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.
- Adoorei links are not decorated automatically. Use the script’s buyer-identification flow on your pages where applicable. If the same order also exists in WooCommerce or Shopify, connect only one source for that 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.