> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendway.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Server-side conversion tracking, the buyer-reputation registry, and outbound webhooks.

Open **Settings → Integrations**. Each card connects one outside account; they are independent of each other.

## Meta Conversions API

Available on **every plan**. Enter your **Meta Pixel ID** and a **Meta access token**, and Sendway reports purchases to Meta **server-side**, which is more reliable than the browser pixel alone. A test event code and a **Send test event** button let you confirm the connection before you trust it.

Server-side events fire for **every order the app creates, in either checkout mode**, including orders you entered by hand and orders where the buyer declined cookies.

<Warning>
  Because the server-side report does not depend on the buyer's cookie choice, mention it in your privacy policy alongside your other tracking disclosures.
</Warning>

## ChatGPT Ads Conversions API

Available on **every plan**. Enter your **OpenAI Pixel ID** and **Conversions API key**, then use **Test connection** to validate them without recording a conversion. If you run ChatGPT Ads, this is usually the only way the platform sees your orders at all.

## NEkorekten

**Starter and Pro.** NEkorekten is a shared Bulgarian registry of people who don't collect their cash-on-delivery parcels. Paste your **NEkorekten API key** and flagged customers get a badge on the [Orders](/orders/manage) page, so you can decide before you ship.

You need a NEkorekten account of your own; their free tier covers 30 checks a day. When you mint the key, whitelist `*` as the IP so the check works from Sendway's servers.

<Note>
  The badge informs, it never blocks. To actually stop an order, put the buyer on the [Fraud protection](/popup/fraud-protection) blocklist.
</Note>

## Webhooks

**Pro.** Send Sendway's events to your own system: an ERP, a warehouse, a Slack relay, anything that accepts HTTPS.

<Steps>
  <Step title="Set the endpoint">
    An HTTPS URL. Local and private addresses are rejected.
  </Step>

  <Step title="Copy the signing secret">
    Sendway sends it as the `X-Sendway-Webhook-Secret` header so your endpoint can verify the call. You can rotate it at any time.
  </Step>

  <Step title="Pick the events">
    Order created, accepted by courier, in courier office, delivered, returned, overdue at office, abandoned popup cart.
  </Step>

  <Step title="Send a test">
    The **Send test** button posts a sample payload. If your endpoint starts failing later, a banner on the card tells you.
  </Step>
</Steps>

## Conversion tracking (Google Ads)

The **Conversion tracking** card holds a single field: your **Google Ads Conversion ID**, in the form `AW-123456789/AbCdEfGhIjK`.

Meta, Google Analytics and TikTok need no setup: when a buyer orders in the popup, Sendway reports the purchase through the pixels already loaded on your store, respecting the buyer's consent. This card is the exception, because a Google Ads conversion label cannot be read from the page.

<Note>
  Browser-side conversion tracking is what [1 Step Checkout](/popup/direct-checkout) needs, since the buyer never reaches Shopify's own checkout. On a 2 Step Checkout shop the card stays editable but tells you it only becomes active in 1 Step Checkout.
</Note>