Connect Pepper to Nevian

Time needed: about 10 minutesLast updated:

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

What you need

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

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

    Drawing: Connect Pepper. Webhook URL: https://track.example.com/wh/pepper/••••••••; Account token: Required account fields are saved with Next

  3. In Pepper, open Integrações → Webhooks and add a webhook integration for the products you want to track.

    Drawing: Pepper · webhook configuration. Integrações: Webhooks; Webhook version: 2.0; URL: Paste the Nevian URL

  4. Use webhook version 2.0, paste the URL and include all payment methods, payment statuses and subscription changes, then save.

    Drawing: Pepper · 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 Account 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 Pepper. Account token: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Send a controlled order in an isolated test workspace. Pepper does not provide a recognized native test flag, so use pixel test mode before sending an event that should not reach live ads. Back in Nevian, look for Connected, then click Done.

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

The optional Account token must match the value Pepper includes in the event. The URL key already authenticates the connection when no extra token is configured.

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.
  • Keep the tracking script on the page linking to go.pepper.com.br or checkout.pepper.com.br. It adds src so the webhook can identify the visit.

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.