Skip to main content

See which channel drives Paddle revenue.

Vero verifies every Paddle webhook and records the transaction. Pass the visit as custom data when you open the checkout, and the sale is credited to the source that earned it.

How it connects

The visit travels with the payment.

The visit’s session travels with the payment and comes back in the signed webhook.

  1. 1The visit

    The tracker gives each visit a session id, with no cookies.

    window.vero.session()
  2. 2The Paddle checkout

    You pass the session as custom data when you open Paddle.js.

    customData.vero
  3. 3The signed webhook

    Paddle posts the sale to Vero, signed with your site’s secret.

    paddle-signature
  4. 4Revenue by source

    Vero joins the sale to its visit: source, campaign, referrer, channel and entry page, without tax and less refunds.

    POST /api/revenue/paddle?s=SITE_TOKEN
Set it up

Three steps, no code.

  1. 1Add a Paddle webhook to Vero with transaction.completed, adjustment.created and adjustment.updated; the signature (ts;h1) is verified on every event.
  2. 2Open Paddle.js with customData: { vero: window.vero.session() }, and Vero reads the visit back from the transaction’s custom data.
  3. 3Transactions are stored without tax, and a renewal keeps the source of the customer’s first attributed payment. Revenue rolls up by source, campaign, referrer, channel and entry page.
URL for Paddle
https://[your-vero-host]/api/revenue/paddle?s=YOUR_SITE_TOKEN
Paddle events
transaction.completed
adjustment.created
adjustment.updated

What you get

  • Paddle signature verification (timestamped HMAC)
  • Completed transactions and refunds, duplicates ignored
  • Profit per source with your COGS and ad spend
  • Cookie-free, no IP stored
Lifecycle

One sale, from first payment to dispute.

  1. 1The first sale

    In the fictional public demo, a visit from news.ycombinator.com ends in a €99 purchase. Paddle sends transaction.completed with the visit in data.custom_data.vero, and Vero stores the sale without tax under that source. A transaction that charged nothing, such as a trial’s first one, is not stored.

  2. 2A renewal

    If that customer renews, Paddle sends another transaction.completed. When it carries no visit, Vero matches the Paddle customer id and credits the renewal to the source of their first attributed payment.

  3. 3A refund

    If that customer is refunded, Paddle sends an adjustment with action refund. Vero deducts it only once its status is approved, so a refund still pending waits for the adjustment.updated that approves it. It comes off the sale’s source, without tax, in the sale’s own proportion.

  4. 4A dispute

    Vero subtracts refunds only. Any other adjustment action, such as a chargeback, is ignored, so a disputed sale stays in its source’s revenue. Each event counts once, and if Vero fails while processing one it answers with a 5xx, so Paddle retries instead of the sale being lost.

Help

When the numbers do not add up.

The card says “Last attempt rejected: invalid signature”

Paddle signs every webhook in Paddle-Signature (ts=…;h1=…), an HMAC-SHA256 over the timestamp and the body. Vero checks it with the secret saved in Vero, so paste the secret of this exact webhook destination. A signature more than 5 minutes off is refused as well.

A transaction counts in the total but has no source

The transaction came back without data.custom_data.vero. Open Paddle.js with customData: { vero: window.vero.session() } wherever a checkout starts. The sale still counts, and takes the source of the customer’s earlier attributed payment when there is one. A visit id only counts if it names a visit of this same site.

A sandbox transaction adds nothing to revenue

Vero recognises a sandbox webhook by the IP addresses Paddle sends sandbox webhooks from, acknowledges it with a 200 and ignores it as test mode. The card shows “Last attempt ignored: test mode”, which proves the URL and the secret work. A wrong site token after ?s= gets a 404, and a missing one a 400.

Is the Paddle signature checked?

Yes: Vero verifies the timestamped HMAC (ts;h1) against a per-site secret, stored encrypted, before accepting an event.

Does it handle refunds?

Yes, once Paddle approves it. Subscribe the webhook to adjustment.created and adjustment.updated as well as transaction.completed. A refund comes off the transaction it reverses and off its source, without tax.

Cookies required?

No: the session travels as custom data on the checkout and comes back in the signed webhook.

Attribute your Paddle revenue

By joining you agree to receive launch updates and accept our Privacy Policy.

See the demo