Tracking Stripe checkouts and other conversions has been a particular challenge due to the inability to place tracking code on the Stripe checkout pages themselves.
Able CDP implements Stripe server-side tracking that relies on a direct server-side connection with Stripe to receive events, allowing it to achieve unparalleled attribution efficiency compared to traditional server-side integrations, such as server-side GTM, as well as to collect the conversion data throughout the entire customer lifecycle.
- Able's server-side tracking for Stripe supports all types of lifecycle events: invoice payments, subscriptions, cancellations, failed payments, and refunds. All such events are tracked entirely server-side, having received as webhooks from Stripe directly.
- Stripe conversions that follow completion of a sign-up or lead form are attributed throughout one of the customer identifiers.
- Stripe checkouts via buy buttons, payment links, and price tables are automatically tagged with a unique session identifier, allowing Able to associate each Stripe checkout and customer with the session.
- Stripe payments established on phone calls are linked with the call tracking data.
Each Stripe conversion is then sent to a server-side tracking API of ad platforms, along with the precise click id that Able server-side tracking associated with the Stripe customer, browser identifier used by server-side tracking APIs such as Facebook's Conversions API, as well as additional attribution details such as email and phone, available in Stripe webhooks.
By leveraging server-side tracking, you can ensure that your ad platforms receive a more comprehensive view of customer interactions, enabling better targeting and performance analysis.
See also: