Connect server checkout exits to Nevian

Time needed: about 10 minutesLast updated:

Report a checkout redirect from your own server so a later payment can find the visit even when the browser cannot report the exit.

What you need

  • Owner or admin access in Nevian and an active plan.
  • A checkout redirect you control on a server, plus permission to store its server secret.
  • The Nevian script on the page before the redirect.

Steps

  1. Open Tools → Tracking script and find Checkout exits from your server. Copy Endpoint from this workspace.

    Drawing: Tracking script. Checkout exits from your server: Report redirects from your server; Endpoint: Copy the workspace endpoint

  2. Select Create server key and store the revealed value as a secret on your server. Never put it in HTML, browser JavaScript, a public repository or a URL.

    Drawing: Server key. Server-only secret: ••••••••••••••••; Storage: Your server environment

  3. Under Report the exit from your redirect, choose your server platform and copy the generated example. Keep the redirect fast: send the exit in the background, using the visit ID and the checkout destination.

    Drawing: Report the exit from your redirect. Platform: Select the runtime you use; Example: Copy the generated code unchanged first

  4. Open a tracked page, follow its buy button through your redirect and return to the recent exits on this card. Confirm the checkout host and How it was linked.

    Drawing: Recent checkout exits. Checkout host: checkout.example.com; How it was linked: Visit reference; Last received: Just now

Check that it works

  • One redirect creates one recorded checkout exit, and the customer still reaches the checkout promptly.
  • Then verify the actual provider sale against the same visit. An exit records intent to enter checkout; it is not a purchase.

Problems

No exits received

Check the copied endpoint, server secret and outgoing HTTPS request. Browser-only code cannot safely use the server key.

The previous key is still in use

After rotation, update your server secret before the previous key’s 24-hour grace period expires.

A key was exposed

Revoke it and create a new server key, then update the server secret. Revocation may take up to a minute to take effect.

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.