Order confirmation pages
When a customer lands on your confirmation page, Pingado reads the order ID from the URL, such as Stripe’s session_id, and asks Pingado’s servers whether the payment provider confirmed it. Until then the answer is pending, and Pingado checks again for up to about 30 seconds.
Once the payment is confirmed, the browser pixels receive the trial or purchase with its value, currency and the event ID the server sends. Nothing fires before the payment is confirmed, and each order fires once, even if the page is reloaded.
If the customer leaves before the payment is confirmed, the server still sends the conversion, and it stays linked to that visitor.
| Provider | Order ID in the URL |
|---|---|
| Stripe | session_id={CHECKOUT_SESSION_ID} |
| Polar | checkout_id={CHECKOUT_ID} |
| Lemon Squeezy | order_id=[order_id] |
| Dodo Payments | payment_id or subscription_id |
| Paddle | none needed, see Paddle |
If your confirmation page uses a parameter Pingado does not recognise, add pg_provider and pg_ref to the URL, or call window.pingado.confirm('stripe', orderId).