GA4: add_payment_info and add_shipping_info compatibility with

Hello there,

another finding that we have is that both add_payment_info and add_shipping_info events are being triggered right when our Checkout page is displayed even though only the billing information form is being displayed at that moment.

Clearly this is caused by the fact that we are using the MultiStep Checkout for WooCommerce plugin to split our checkout page into two screens for better UX. It is obvious that the hooks that you are using to print the tracking scripts are indeed called when the first page of our checkout page is displayed and that’s what’s causing the events to be fired too early.

I myself find it quite complicated to achieve compatibility with the plugin especially while users can even move the different sections of checkout page to the first or second page as they wish. Unless the authors of the plugin actually only render the HTML content when it really gets displayed.

Another solution (achievable without their assistance) I can think of would be to (optionally) disable those 2 events that are triggered on every checkout load and leave just the ones that are triggered by the user when changing shipping/payment option.

I am still discussing with our analyst whether this would make more sense but I though I would check with you whether this is something you would consider implementing.

Thanks in advance for your support!
Honza

Hello Honza,

Thank you for your input. We have forwarded your recommendations to the plugin developer. We will update you shortly with details on the implementation process.

Best regards
Mergado PACK Support Team

Hello Honza,

Thank you for bringing this issue to our attention. After thoroughly reviewing the situation, we have determined that the behavior you’re experiencing is due to the way the system is designed to handle radio buttons. The radio button always selects a default value. This ensures that if the user does not choose another option, their selection is still recorded in GA4.

Unfortunately, this default behavior is necessary for proper tracking and cannot be altered without affecting the consistency for all users. However, to address your specific case, we recommend the following workaround:

  • Disable the default event.
  • Send a custom event manually when needed.

This approach allows you to maintain full control over the tracking behavior. The option to disable the default event exists precisely for such use cases.

If you need assistance with implementing a custom event or have further questions, please don’t hesitate to reach out. We’ll be happy to guide you through the process.

Best regards,
Mergado Pack Support Team