Revenue providers

Connections are per website. Every provider follows the same three steps:

  1. Under Integrations, pick the provider and click Get webhook URL.
  2. In the provider's dashboard, add a webhook with that URL and tick the events listed below.
  3. Back in DataFair, save the signing secret and click Save and finish.

Some providers create the signing secret for you and show it after the webhook exists. Others let you choose it, and DataFair makes a random one you paste in both places.

Stripe

Signing secret: Stripe creates it. Copy it after adding the webhook.

  1. Open Stripe and go to Developers, then Webhooks (in Workbench).
  2. Click Create an event destination. Older dashboards call it Add endpoint.
  3. Choose events from Your account and tick the events listed below.
  4. Choose Webhook endpoint and paste your DataFair webhook URL as the endpoint URL. Create it.
  5. On the new destination, click Reveal next to Signing secret and copy it.

Events: checkout.session.completed, checkout.session.async_payment_succeeded, invoice.paid, invoice.payment_failed, charge.refunded, charge.dispute.created, customer.subscription.deleted

Test mode and live mode keep separate webhooks, each with its own secret. Connect the one you are using.

Matching: Payment links are tagged automatically by the script. For Checkout sessions you create yourself, add df_visitor_id and df_session_id to the metadata. If one Stripe account sells for several websites, also add df_site_id with this website id, so each payment lands on the right one.

Lemon Squeezy

Signing secret: you choose it, and type the same value in DataFair and Lemon Squeezy.

  1. Open Lemon Squeezy and go to Settings, then the Webhooks tab.
  2. Click the + button to add a webhook.
  3. Paste your DataFair webhook URL into Callback URL.
  4. Paste your signing secret into Signing secret. It must match the one saved in DataFair exactly.
  5. Tick the events listed below and click Save webhook.

Events: order_created, order_refunded, subscription_payment_success, subscription_payment_failed, subscription_payment_refunded, subscription_cancelled

Test mode and live mode keep separate webhook lists. Add it in the mode you are selling in.

Matching: Checkout links on your site are tagged automatically by the script, through checkout[custom].

Paddle

Signing secret: Paddle creates it. Copy it after adding the webhook.

  1. Open Paddle and go to Developer tools, then Notifications.
  2. Click New destination and choose Webhook.
  3. Paste your DataFair webhook URL, tick the events listed below, and save.
  4. Open the destination you just made and copy its Secret key.

Events: transaction.completed, transaction.payment_failed, adjustment.created, adjustment.updated, subscription.canceled

The sandbox has its own destinations and secrets. Use sandbox-vendors.paddle.com while testing.

Matching: Pass df_visitor_id in customData when you open Paddle Checkout.

Dodo Payments

Signing secret: Dodo Payments creates it. Copy it after adding the webhook.

  1. Open Dodo Payments and go to Developer, then Webhooks.
  2. Click Add endpoint and paste your DataFair webhook URL.
  3. Tick the events listed below and click Create.
  4. On the endpoint’s Overview tab, copy the Signing secret.

Events: payment.succeeded, payment.failed, refund.succeeded, subscription.cancelled

Test mode and live mode keep separate endpoints. Add it in the mode you are selling in.

Matching: Checkout links are tagged automatically by the script.

Polar

Signing secret: you choose it, and type the same value in DataFair and Polar.

  1. Open Polar and go to your organization’s Settings, then Webhooks.
  2. Click Add Endpoint and paste your DataFair webhook URL.
  3. Set Format to Raw.
  4. Paste your signing secret into Secret. If you let Polar generate one instead, copy it back into DataFair.
  5. Tick the events listed below and save.

Events: order.paid, order.refunded, subscription.canceled

The sandbox at sandbox.polar.sh has its own webhooks.

Matching: Add df_visitor_id to the checkout metadata you send to Polar.

Shopify

Signing secret: Shopify creates it. Copy it after adding the webhook.

  1. Open your Shopify admin and go to Settings, then Notifications, then Webhooks.
  2. Copy the signing secret shown on that page, under “Your webhooks will be signed with”.
  3. Click Create webhook. Choose the event Order payment, format JSON, paste your DataFair webhook URL, keep the latest API version, and save.
  4. Repeat Create webhook for Refund create and for Dispute create, with the same URL.

Events: orders/paid, refunds/create, disputes/create

Matching: Add df_visitor_id as a cart attribute to get a direct match. Otherwise payments match by email.

WooCommerce

Signing secret: you choose it, and type the same value in DataFair and WooCommerce.

  1. In WordPress, go to WooCommerce, then Settings, then Advanced, then Webhooks.
  2. Click Add webhook. Set Status to Active and Topic to Order created.
  3. Paste your DataFair webhook URL into Delivery URL and your signing secret into Secret.
  4. Set API version to WP REST API Integration v3 and click Save webhook.
  5. Add a second webhook the same way with the Topic Order updated.

Events: Order created, Order updated

Never leave Secret blank: WooCommerce would then sign with your API key instead.

Matching: Save df_visitor_id as order meta to get a direct match. Otherwise payments match by email.

Creem

Signing secret: Creem creates it. Copy it after adding the webhook.

  1. Open Creem and go to Developers, then Webhooks.
  2. Add a webhook and paste your DataFair webhook URL.
  3. Tick the events listed below and save.
  4. Copy the webhook’s signing secret.

Events: checkout.completed, subscription.paid, refund.created, dispute.created, subscription.canceled

Test mode and live mode keep separate webhooks. Add it in the mode you are selling in.

Matching: Payment links on your site (creem.io/payment/…) are tagged automatically by the script. For checkouts you create through the API, add df_visitor_id to metadata.

Whop

Signing secret: Whop creates it. Copy it after adding the webhook.

  1. Open your Whop dashboard and go to the Developer tab.
  2. Click Create webhook and paste your DataFair webhook URL.
  3. Tick the events listed below and save.
  4. Copy the secret from the Secret column. It starts with ws_ and is only shown once.

Events: payment.succeeded, payment.failed, refund.created, refund.updated, dispute.created, membership.deactivated

The sandbox at sandbox.whop.com has its own webhooks.

Matching: Add df_visitor_id to the metadata of the checkout configurations you create. Whop checkout links can’t carry it, so other payments match by email.

Gumroad

Signing secret: Gumroad creates it. Copy it after adding the webhook.

  1. Open Gumroad and go to Settings, then Advanced.
  2. Paste your DataFair webhook URL into the Ping endpoint field.
  3. Turn on signing for pings, and copy the signing secret it shows.
  4. Save, then click Send test ping to check the connection.

Events: sale, refund

Gumroad sends every sale and refund to the ping URL, so there are no events to tick. Signing must be on: unsigned pings are refused.

Matching: Product links on your site (gumroad.com/l/…) are tagged automatically by the script. Gumroad passes the tags back as url_params.

PayPal

Webhook ID: PayPal creates it. Copy it after adding the webhook.

  1. Sign in at developer.paypal.com with your PayPal business account and open Apps & Credentials.
  2. Choose Live (or Sandbox while testing) and open your app. If there is none, click Create App.
  3. Under Webhooks, click Add Webhook and paste your DataFair webhook URL.
  4. Tick the events listed below and save.
  5. Copy the Webhook ID shown next to the new webhook.

Events: PAYMENT.CAPTURE.COMPLETED, PAYMENT.CAPTURE.DENIED, PAYMENT.CAPTURE.REFUNDED, PAYMENT.SALE.COMPLETED, PAYMENT.SALE.REFUNDED, CUSTOMER.DISPUTE.CREATED, BILLING.SUBSCRIPTION.CANCELLED

PayPal has no signing secret. DataFair checks every delivery against PayPal’s own certificate and this Webhook ID, so no API keys are needed. Sandbox and Live have separate webhooks.

Matching: Set custom_id on the purchase unit (or the subscription) to the visitor’s df_visitor_id. PayPal doesn’t send it otherwise, so untagged payments stay unattributed.

How attribution works

Each payment is matched using the strongest signal available: checkout metadata and return pages (high confidence), the same customer or a matching email (medium), or a single unambiguous checkout click just before payment (low). Credit goes to the last visit that came from somewhere. Payments with no match are reported as unattributed.

Planned

Historical import from providers isn't available yet, so revenue starts from when you connect. More providers are on the roadmap, and the payments API covers anything else today.

Documentation