Hi, we are not seeing any Web Pixel events firing when a customer switches the delivery method in checkout from Shipping to Pickup.
We are not certain whether this behavior is related to the checkout total remaining unchanged (for example, when both shipping and pickup are free), but it is one possible condition observed during testing.
We tested the following events:
-
checkout_shipping_info_submitted
-
checkout_address_info_submitted
-
checkout_contact_info_submitted
We also tested DOM-based events such as:
-
clicked
-
input_changed
-
input_focused
None of these events fire when the customer selects Pickup.
Hi,
The behavior you’re observing is expected. The Web Pixels API standard events distinguish between delivery options (Ship vs. Pick up) and shipping methods/rates (e.g. Standard, Express). These are separate concepts in the checkout form.
The checkout_shipping_info_submitted event specifically fires when a shipping rate is selected or confirmed — it does not fire when switching between delivery options like Ship and Pick up. Delivery option selection (Ship vs. Pick up) is not currently covered by a dedicated standard pixel event.
However, the chosen delivery option is included in the checkout data payload of other standard events that fire later in the flow, such as payment_info_submitted and checkout_completed. You can inspect the checkout.delivery.selectedDeliveryOptions array in those event payloads — the type field will reflect whether the buyer chose "shipping" or "pickup".
So while there’s no event that fires at the moment of switching, you can still determine which delivery option the buyer ultimately selected by reading the delivery data from downstream events.
1 Like
Thank you so much for the information. It would be great if we could at least listen for this change using a DOM event. In our application, we need to listen for it before processing the payment, so payment_info_submitted and checkout_completed aren’t useful to us.