Support » Plugin: DuracellTomi's Google Tag Manager for WordPress » Duplicating revenue when page reloads

  • Been using your plugin the last couple of months and it seems to work OK except for the odd instance when order details are being duplicated (presumably if the /order-received/ page is reloaded by the user), leading to inflated revenue and conversion value in Analytics and AdWords.

    Before we added the plugin, I used a custom GTM variable which stopped ecommerce data being sent if the page was recognised as a reload, but that solution doesn’t seem to work with the plugin.

    Most orders that come through are fine, so it’s not as if every one is being duplicated like others have asked about – it’s just the occasional one. But it’s enough that my conversion rate and associated data is inaccurate.

    What would you suggest?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author duracelltomi

    (@duracelltomi)

    Hi,

    A placed a test order on your site and after reloading the order received page, the transaction data is not present in the data layer which is the expected behavior.

    You might want to use the checkbox that prevents orders as being set to be tracked which will cause order data to be present on each reload of the same order received page. With that, you might be able to utilize your script that prevents duplicate tracking on its own.

    Sorry, the wording is a little confusing – so if I check the box “Do not flag orders as being tracked” (which is currently unchecked), will that solve the problem? I have also noticed that our transaction numbers are way above the actual number of orders – will it solve/impact that too?

    Plugin Author duracelltomi

    (@duracelltomi)

    Sorry for confusing you, let me clear this up:

    Checking the “Do not flag” option will not solve your issue alone, but it could help you to use your original solution that you mentioned before:

    Before we added the plugin, I used a custom GTM variable which stopped ecommerce data being sent if the page was recognised as a reload, but that solution doesn’t seem to work with the plugin.

    Some people use custom codes to read the transaction ID and store it into a cookie so that when the same transaction ID is present on an order received page, the transaction data could be removed from the Google Analytics hit. I thought you were referring to this kind of custom GTM variable.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.