Menu

Send purchase events from the server, not only from the thank-you page
📰

Send purchase events from the server, not only from the thank-you page

DEV Community: postgres·RAMO·2 days ago
#dbHLIKTR
#devtopostgresql#devto#dev#order#null
Reading 0:00
15s threshold

For a long time, the usual advice for store purchase events has been: the customer lands on the thank-you page, a script runs, and each ad or analytics pixel is told "this order happened, here's the value".

It works most of the time. The trouble is "most of the time" is a weak guarantee for the one event an ad budget is often optimized on.

Here are common ways it fails:

The customer pays, the payment provider redirects back, and the tab is closed before the redirect finishes. No thank-you page, no event.

An ad blocker or a strict browser setting drops one pixel but not the others. The platforms then disagree about how many orders there were.

Someone refreshes the thank-you page, or opens it again from an email link. Without careful dedup, that's a second purchase.

A bank transfer or phone order is confirmed by staff hours later. There is no browser session at all.

None of this is exotic.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.