How conversions are sent

One conversion, two copies, one ID

Ad platforms learn from conversions they can tie to an ad click. The browser pixel sees the click’s cookies; the server sees the payment. Pingado sends each conversion from both, with the same event ID, and each platform keeps one.

Conversion	Where the event ID comes from
Lead	The snippet creates it when the form is submitted, fires the pixel with it, and sends it to Pingado, which sends the same ID from the server.
Trial started, Purchase	Pingado derives it from the payment provider’s IDs, so the same payment always has the same ID. The browser learns it on the confirmation page.

Linking a payment to a visitor

When a payment arrives, Pingado looks for the visitor in this order:

1. The visitor ID passed through checkout, such as Stripe’s client_reference_id.
2. The confirmation page: the browser that opened the confirmation page for that order, even if it left before the payment was confirmed.
3. An earlier lead with the same email.

If none of these match yet, Pingado waits a minute before sending, in case the confirmation page is still loading.

Attribution

Each conversion is credited to the visitor’s last ad click or campaign before it. Pingado matches on the click ID the platform adds to the ad’s URL first, then on UTM parameters, then on the referring site. Moving between your own domains never counts as a new source.