view_item_list event + parameters only once

  • drasier

    (@drasier)


    3 years ago

    Hello,

    1o Your plugin is awesome.

    2o Your page and tutorials are even more awesome. Thanks.

    3o I’m using the setting ‘Products per impression’ as you recommend. Not sure if we were missing page views though. The problem with this is that we have some custom parameters on that event (view_item_list) and we need those parameters to be sent only once (per page view). And now we are getting 4-6 view_item_list events every time a user visits a product archive page messing up with our reports regarding those custom parameters.

    Is there any way to send those parameters only in the first event? Probably that’s not the best solution but I can’t come up with anything else. Accepting suggestions ?? Another approach could be sending those parameters in the page_view event, but I feel that the “correct” way to do it is in the “view_item_list” event…

    Our parameters have information about the brand and category of the archive page and also the name of the item list (related products, editor’s choices, best sellers, etc).

Viewing 1 replies (of 1 total)
  • Plugin Author Thomas Geiger

    (@duracelltomi)

    1o & 2o – Thanks ??

    3o – event names are crucial for ecommerce tracking in GA4. Missing a view_item_list event or other ecommerce event will break your reports.

    The name of the list where a specific product was shown is included in the item_list_name parameter of each product in the view_item_list event. If you would like to customize this, you should rather hook into the gtm4wp_compile_datalayer filter and change the values there so that GA4 gets your names instead of the default recognized names of GTM4WP.

    If you are talking about the brand and category of an archive page: that sounds to me an attribute of the page_view event, I would send these parameters there instead of the view_item_list event.

Viewing 1 replies (of 1 total)
  • The topic ‘view_item_list event + parameters only once’ is closed to new replies.