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

    (@duracelltomi)

    Hi @bossyaka,

    Normally my plugin flags every order as being tracked once so when you reload the order received page for the same order, it should not include transaction data again to prevent tracking the same order multiple times.

    HiggySmalls

    (@nworbnosgihderf)

    I’m also having this issue of duplicate orders. So Analytics is counting multiple transactions against one order ID. Is there a setting that I’ve missed to prevent this from happening?

    Thanks!

    Plugin Author Thomas Geiger

    (@duracelltomi)

    @nworbnosgihderf without mentioning the URL of your site I can not give you any specific advise. Usually this is because you have another Google Analytics related plugin active which also sends the transaction data next to this plugin

    HiggySmalls

    (@nworbnosgihderf)

    @duracelltomi the URL is https://www.dowsingandreynolds.com – there is just the GA tag that is measuring conversions. It seems to be an intermittent issue as I’ve tried reloading an order-received page and that didn’t duplicate, but others are. If I look into the issue by date, the duplication lines up with this plugin being used.

    Thanks!

    Plugin Author Thomas Geiger

    (@duracelltomi)

    @nworbnosgihderf could you segment your data by device type? Maybe this is something related to only mobile phones, perhaps only a specific mobile operating system/browser?

    I also have similar issues when customers re-visit the order-received page, duplicate transactions are being tracked in GA. I only use this plugin to implement my tags and there is no other plugin related to GA on my website. https://holisticlub.com

    The duplicate transactions do not share a consistent pattern. Device type can be iPhone or Android mobile, whereas payment gateway can be Stripe or Paypal.

    Plugin Author Thomas Geiger

    (@duracelltomi)

    I did some testing during the last weeks but still I was not able to identify the exact case where this might be an issue.

    My only idea is that there might be some cache plugin active on those sites where the cache plugin stores the original page source, including the ecommerce data and while users revisit those pages, my plugin’s code never gets executed again (filtering out ecommerce data) but the cached page is being loaded.

    I will exclude the checkout page in my cache plugin and see if this will help to solve the issue. Thank you for sharing your idea. Much appreciated!

    I would like to report back that there is still duplicate transaction recorded in GA after disabling cache on cart and checkout pages. This time it happens on desktop with Chrome browser. When I had a detailed look into all the duplicate transactions data, they could happen on both mobile (iPhone & Android) and desktop as well as Safari and Chrome browsers. Although all of them involved users starting a new session to enter my website’s checkout page directly, there were others doing the same but didn’t get double tracked. I am just wondering if it has something to do with their browser setting of either blocking cookies or deleting cookies when existing from each session?

    Plugin Author Thomas Geiger

    (@duracelltomi)

    Hi @lamrica,

    Thanks for getting back to here.
    Since I can not place a test order on your page because of the need of a credit card during checkout, I can not tell you any reason for this kind of behavior.

    Do you see pageviews in the Behaviour -> Site content -> All pages report on order received pages of past orders?

    I usually try to figure out what could had happened by comparing the pageview stats on URIs containing the “order-received” string with the transaction IDs. Since URIs also contain the order number, this could give you a clue whether duplicate transaction tracking could be because of repeated visits to the order received page.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘How it work then I reload order-received page’ is closed to new replies.