Describe the bug
Default ps_googleanalytics module does not track anything in Prestashop backoffice. It is important to track cancelled and refunded orders.
Error is detected by Tag Assistant as well as manual check, even after 48 hours, nothing changed.
There are 2 year old bug reports in the module repo, but they are closed without a solution. (???)
To Reproduce
Steps to reproduce the behavior:
Additional information
PrestaShop version: 1.7.6.2
Google analytics module: 3.2.0
PHP version: 7.1
Hi @Hlavtox,
I have the same behavior as PS1.7.6.3 and PS1.7.5.2 and ps_googlenalytics v3.2.0.

But, I think, it could a good improvement for the module.
@Hlavtox, what do you think, can we update this issue from bug to improvement?
Thanks!
@khouloudbelguith
I discovered this, because I went to add another functionality for the BO (https://github.com/PrestaShop/ps_googleanalytics/pull/43). And 2 days later, I was wondering why the transaction still does not appear, and I discovered that it does not work at all in BO. 馃槃
I think it's definitely a bug, because there is functionality for refund in the code. It is indended for it to work like this. The module is hooked to actionProductCancel, displayBackOfficeHeader etc.
Look at the existing code:
It is probably some JS error, but my console is clear, I have no idea.
@Hlavtox, thanks for your feedback.
I鈥檒l add this to the debug roadmap so that it鈥檚 fixed. If you have already fixed it on your end or if you think you can do it, please do send us a pull request!
Thanks!
@khouloudbelguith False alarm, it shows the error because there is no pageview action sent.
My refund PR works fine!!! 馃嵑
Shouldn't we write this somewhere, that is it not a bug? I am like the third person to open this... 馃槃
@Hlavtox,
My refund PR works fine!!!
this PR: https://github.com/PrestaShop/ps_googleanalytics/pull/43?
Thanks!
@khouloudbelguith Yes :-)
@Hlavtox,
Shouldn't we write this somewhere, that is it not a bug?
What do you think about updating the Readme.md?
Yes :-)
I will close this issue as it is not a bug.
Thanks!
@khouloudbelguith Hi, I added a note to readme. :-)