Analytics plugin sending incorrect number of items and amounts to GA

-- HikaShop version -- : 2.6.4
-- Joomla version -- : 3.6.5
-- PHP version -- : 5.6

Hi,

We are having a problem with HikaShop analytics plugin. We are using two payment methods on the site:
- standard PayPal
- PayPal Pro (credit card)

Standard Paypal method was sending zero revenue amounts to GA and credit card method was sending revenue and items number multiplied by 2,3 or even 5 in some cases.

Following a similar thread on the forum I decided to update analytics plugin to one from HikaShop version 3.0.1. After that, I got correct numbers for orders completed through standard PayPal plugin, but ones made with credit card were still having issues with multiplied values.

I am assuming that multiplication happens when somebody enters incorrect credit card data and tries again data gets multiplied by the number of retries, because some of the orders made by credit card actually show correct numbers (including two test ones I created).

Attached are the settings for the plugin:

Hi Jerome,

Sorry if I made my explanation to convoluted to understand.

Let me try again.

I already updated analytics plugin to one from hikashop 3.0.1, but that did not solve the problem.

Standard PayPal payment method now works fine, it sends correct number of products and revenue amount to analytics.

PayPal Pro payment method works well if I enter all the data correctly on the first try and complete checkout - it sends correct values for products and revenue to GA.

If I make a mistake when entering cc info, try again and succeed second time, number of products and revenue amount in GA for that order will be doubled. If I make mistake two times before succeeding, it will be tripled etc.

Payment method selection is on the last step of the checkout process, I don't know if that information is useful to you.

Does this information help?

Hi Jerome,

Thank you for your reply.

I will check with one of our developers, there might have been some changes within the code, so this error might have been created on our end.

If I need additional assistance, I will post my questions here.

Thanks.