What changed with InitiateCheckout in GoHighLevel?
Since October 12, 2026, the Meta Pixel InitiateCheckout event in HighLevel fires when a buyer reaches checkout, not when they submit payment. AddPaymentInfo now also sends order value, currency, product IDs and hashed customer details. Expect higher InitiateCheckout counts from that date.
The source is the HighLevel changelog entry Meta Pixel: Improved InitiateCheckout Accuracy & Enhanced AddPaymentInfo Data, first published October 12, 2026. It applies to funnels, websites and stores that have the Meta Pixel set up with InitiateCheckout enabled. HighLevel says no action is required and the update applies automatically.
The change brings HighLevel closer to Meta's own definition. Meta's standard events reference describes InitiateCheckout as "When a person enters the checkout flow prior to completing the checkout flow," with the example "A person clicks on a checkout button."
Why did my InitiateCheckout count go up?
Because the event now counts everyone who starts checking out, including people who leave without paying. Before October 12, HighLevel sent InitiateCheckout at payment submission, so it counted roughly the same buyers as AddPaymentInfo. The rise is expected and does not mean your traffic or ads changed.
HighLevel's own wording: "InitiateCheckout counts will go up. This is expected." The practical effects:
- Cost per InitiateCheckout will drop in Ads Manager, because the same spend now buys more counted events.
- Automated rules that pause or scale ad sets on cost per InitiateCheckout may fire differently. Review their thresholds.
- Week-over-week reports that cross October 12 compare two different definitions. Mark the date in your reports. For attribution inside HighLevel itself, see our note on the Lead Source Report drill-down.
- Purchase does not change. HighLevel says PageView, ViewContent and Purchase fire at the same moments as before.
When does each checkout event fire now?
InitiateCheckout fires on page load for store checkout pages and for pages where you added it at page level. Everywhere else it fires on the buyer's first click, tap or keystroke in an order form. AddPaymentInfo fires when payment details go in, and Purchase when the order completes.
Checkout events in order, from October 12, 2026
| Event | Before October 12, 2026 | From October 12, 2026 |
|---|---|---|
| InitiateCheckout (store checkout page) | At payment submission | When the checkout page loads |
| InitiateCheckout (added at page level) | At payment submission | When that page loads |
| InitiateCheckout (added at funnel, website or webinar level) | At payment submission | First click, tap or keystroke in the order form |
| InitiateCheckout (Apple Pay and other express wallets) | At payment submission | When payment starts, even if the form was never touched |
| AddPaymentInfo | Sent, with less order data | Sent with order value, currency, product IDs and hashed email, phone, name and external ID when available |
| Purchase, PageView, ViewContent | Unchanged | |
Source: HighLevel changelog, October 12, 2026. The "before" column follows HighLevel's description that InitiateCheckout used to fire "when they submit payment." The entry covers one-step, two-step and popup order forms, plus the new order form.
HighLevel also lists safeguards. InitiateCheckout fires at most once per page visit even with several order forms. Browser autofill, password managers and auto-focused fields do not trigger it. When a buyer returns through an abandoned-cart link, the event waits for the saved cart so it carries the cart value and products.
What is the difference between InitiateCheckout and Purchase?
InitiateCheckout means a person started checking out; Purchase means they finished and paid. Meta defines Purchase as "When a purchase is made or checkout flow is completed." The gap between the two events is your checkout drop-off, which HighLevel's old timing hid.
With the new timing you can read the funnel in three steps: InitiateCheckout (started), AddPaymentInfo (entered payment) and Purchase (paid). A large drop between the first two usually points to the form itself: too many fields, a surprise shipping cost, or a slow page. A large drop between the last two points to payment problems such as declined cards. Those diagnoses are our reading of typical checkout data, not something HighLevel's entry states.
Two-step order forms in GoHighLevel funnels already save the contact in step one, so you can follow up with people who start checkout and leave. Our follow-up that converts page shows the kind of recovery sequence we build for that. AI Studio checkouts got a similar two-step option on October 15, 2026; our earlier note covers AI Studio payments.
What should I do in Meta Ads Manager now?
Add an annotation for October 12, 2026, review any automated rules based on InitiateCheckout, and keep optimizing campaigns for Purchase if that is your goal. Nothing needs changing in HighLevel, though page-level settings can take up to 24 hours on pages already published.
- Note October 12, 2026 in your reporting sheet or dashboard as the date InitiateCheckout changed meaning.
- Open Ads Manager → Automated rules and check any rule that uses cost per InitiateCheckout.
- Compare InitiateCheckout to Purchase for the last 7 days. That ratio is your real checkout drop-off. If you want this as a live report instead of a manual check, see automated reporting.
- If you added InitiateCheckout at page level and want it live now, edit and save the page. HighLevel says it can otherwise take up to 24 hours.
- In Events Manager, watch Event Match Quality for AddPaymentInfo. HighLevel expects it to improve because more customer details are sent.
HighLevel says consent still works as before: if a visitor has not accepted advertising cookies, nothing is sent. With the Conversions API on, browser and server events are still sent together and deduplicated in Events Manager.
What is still unknown?
HighLevel does not say how much counts will rise, whether past data is restated, or how this affects campaigns already optimizing for InitiateCheckout. The rise depends on how many of your visitors start checkout and leave.
- Size of the change: no figure is given. It will differ by funnel. Common tracking and setup mistakes are collected in common GoHighLevel mistakes.
- Historical data: the entry does not mention restating old events, so treat earlier InitiateCheckout counts as the old definition.
- Campaigns optimizing for InitiateCheckout: HighLevel says Meta gets better signals, but does not describe any learning-phase effect. Watch these campaigns for a week before changing budgets.
Frequently asked questions
Do I need to change my Meta Pixel settings in GoHighLevel?
No. HighLevel says your Meta Pixel settings work as before and the update applies automatically. The only optional step is for pages where you set InitiateCheckout at page level: those can take up to 24 hours to update, and editing and saving the page applies the change right away.
Will this change my Purchase numbers?
No. HighLevel says PageView, ViewContent and Purchase fire at the same moments as before. Only InitiateCheckout timing changed, and AddPaymentInfo now carries more data. Orders fully covered by a gift card now send AddPaymentInfo with a value of 0, which is the one other change to note.
Does InitiateCheckout fire for Apple Pay buyers in GoHighLevel?
Yes. HighLevel says buyers who go straight to Apple Pay or another express wallet without touching the form are still counted, and for them InitiateCheckout fires when payment starts. Before the change, every buyer was counted at payment submission, so express wallet buyers were already included at that point.
Is this change only for GoHighLevel stores?
No. HighLevel says it applies to funnels, websites and stores that have the Meta Pixel set up with the InitiateCheckout event turned on. If InitiateCheckout is not enabled on your pixel, nothing changes. The timing differs by page type, as the table above shows.
Sources
- HighLevel changelog, Meta Pixel: Improved InitiateCheckout Accuracy & Enhanced AddPaymentInfo Data, first published October 12, 2026, checked 2026-10-16.
- Meta for Developers, Meta Pixel reference: standard events, no update date shown, checked 2026-10-16.
