How InitiateCheckout and AddPaymentInfo Work in Meta Pixel Tracking
Meta Pixel tracks checkout activity in Chat To Clients CRM funnels, websites, and stores. InitiateCheckout identifies when buyers begin checkout, while AddPaymentInfo tracks when they proceed to payment. These events help you understand checkout abandonment and provide Meta with information for campaign optimization.
TABLE OF CONTENTS
- How InitiateCheckout Tracking Works
- How Duplicate Events Are Prevented
- Abandoned-Cart Recovery
- Express Wallet Payments
- What Information Does AddPaymentInfo Send?
- AddPaymentInfo for Free Orders and Gift Cards
- How These Changes Affect Checkout Reporting
- Do You Need to Update Your Meta Pixel Settings?
- When Do Page-Level Changes Take Effect?
- Cookie Consent and Conversions API
- Frequently Asked Questions
How InitiateCheckout Tracking Works
InitiateCheckout fires when a buyer starts the checkout process. The timing depends on where the event is configured and which checkout experience the buyer uses.
| Checkout Experience | When InitiateCheckout Fires |
|---|---|
| Store checkout page | When the checkout page loads |
| Page-level event configuration | When the configured page loads |
| Funnel-level tracking | When the buyer first interacts with an order form |
| Website-level tracking | When the buyer first interacts with an order form |
| Webinar-level tracking | When the buyer first interacts with an order form |
| One-step, two-step, popup, and new order forms | On the buyer's first click, tap, or keystroke, unless page-level tracking applies |
When InitiateCheckout is configured at the page level, the event fires on page load without waiting for an order-form interaction.
How Duplicate Events Are Prevented
InitiateCheckout fires at most once per page visit. This applies even when a page contains multiple order forms or more than one configured trigger. The following actions do not trigger InitiateCheckout:
Browser autofill
Password-manager autofill
Automatic field focus when the page loads
Abandoned-Cart Recovery
When buyers return through an abandoned-cart recovery link, InitiateCheckout waits until the saved cart loads. This allows the event to include the restored cart value and products.
Express Wallet Payments
InitiateCheckout also tracks buyers who use express payment methods, such as Apple Pay, without interacting with the order form. In these cases, the event fires when payment begins.
What Information Does AddPaymentInfo Send?
AddPaymentInfo sends additional order and customer information to Meta when available.
| Data | Information Sent |
|---|---|
| Order value | Value associated with the order |
| Currency | Order currency |
| Product IDs | Product identifiers associated with the order |
| Hashed customer email | |
| Phone | Hashed customer phone number |
| Name | Hashed customer name |
| External ID | Hashed customer external ID |
This additional information helps Meta match conversion events to customers and improve event attribution. Invalid or blank values are not sent. Events associated with the same order use a consistent currency.
AddPaymentInfo for Free Orders and Gift Cards
AddPaymentInfo is not sent when an order requires no payment details. However, orders fully covered by a gift card now send AddPaymentInfo with an order value of 0.
How These Changes Affect Checkout Reporting
InitiateCheckout may report more events because it now captures buyers earlier in the checkout process. Previously, InitiateCheckout and AddPaymentInfo often counted the same buyers. You can now distinguish buyers who begin checkout from those who proceed to payment.
When reviewing campaign performance, consider these changes before comparing:
InitiateCheckout counts before and after the update
Checkout abandonment rates
Cost per InitiateCheckout
Automated rules based on InitiateCheckout
An increase in InitiateCheckout events does not necessarily indicate an increase in completed purchases.
Do You Need to Update Your Meta Pixel Settings?
No configuration changes are required. The updated tracking behavior applies automatically to supported funnels, websites, and stores with InitiateCheckout enabled. If InitiateCheckout is not enabled, this change does not affect the pixel's existing behavior.
When Do Page-Level Changes Take Effect?
Changes to page-level InitiateCheckout settings may take up to 24 hours to take effect on previously published pages. To apply the changes immediately, edit and save the page.
Cookie Consent and Conversions API
The update does not change existing cookie-consent behavior. When visitors have not accepted advertising cookies, tracking events are not sent to Meta.
If Conversions API is enabled, browser and server events continue to be sent and deduplicated in Meta Events Manager. The timing of PageView, ViewContent, and Purchase events remains unchanged.
Frequently Asked Questions
Why did my InitiateCheckout count increase?
InitiateCheckout now tracks buyers at the beginning of checkout rather than waiting until they proceed to payment. More buyers are included, even when they abandon checkout.
Can InitiateCheckout fire multiple times on the same page?
InitiateCheckout fires at most once per page visit, even when multiple order forms or triggers exist.
Does browser autofill trigger InitiateCheckout?
No. Browser autofill, password managers, and automatically focused fields do not trigger the event.
Does InitiateCheckout work with Apple Pay?
Yes. When buyers use an express payment option without interacting with the order form, InitiateCheckout fires when payment starts.
Does the update change Purchase tracking?
No. Purchase continues to fire at the same point as before.
Do I need to reconnect my Meta Pixel?
No. The update applies automatically to eligible existing configurations.