Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ecommerce metrics not aggregated #7945

Closed
Guite opened this issue May 20, 2015 · 13 comments
Closed

Ecommerce metrics not aggregated #7945

Guite opened this issue May 20, 2015 · 13 comments
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@Guite
Copy link

Guite commented May 20, 2015

Since the 30th of April (Piwik 2.13.0) no ecommerce metrics are aggregated anymore (like amount of orders, amount left in cart, etc.).
I first thought it could be related to #6986 but the config values mentioned there make no difference. Even with browser-based archiving enabled all ecommerce values keep 0.

Of course there is still data available which is also shown in the ecommerce log tab.

Any idea how to track this down?

@mattab
Copy link
Member

mattab commented May 20, 2015

Hi @Guite

can you please upgrade to 2.13.1 first?

if you still have the issue could you post here a screenshot? thanks

@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label May 20, 2015
@mattab mattab added this to the 2.14.0 milestone May 20, 2015
@Guite
Copy link
Author

Guite commented May 20, 2015

Hi @mattab

I am using 2.13.1 already. Just wanted to mention that the problem seems to exist since 2.13.0.

Here is a screen:

screen_ecommerce_metrics

@mattab
Copy link
Member

mattab commented May 21, 2015

Hi @Guite

If possible for you, can you try upgrade to 2.14.0-b1 ? the beta version works well and fixes an issue in Ecommerce which maybe fix your problem. if it does not fix it, we will do our best to help you and resolve this issue before next release

@Guite
Copy link
Author

Guite commented May 21, 2015

Hi @mattab

I successfully upgraded to 2.14.0-b1. On the first glance nothing has changed. Can I somehow remove aggregation data for the last four weeks in the database to let the archive script recreate them?

@tsteur
Copy link
Member

tsteur commented Jun 8, 2015

I can't reproduce it and have no idea how to track it down. @Guite do you still have any config settings left from #6986?

Re removing invalid aggregation data you could maybe try to delete the archives for one or two days and re-archive. Here's a FAQ how to do it: http://piwik.org/faq/how-to/faq_155/ You can specify multiple dates comma separated, but would first try it only for one

@Guite
Copy link
Author

Guite commented Jun 8, 2015

Would it help if I'd provide access credentials to hello at piwik.org so that you can check my installation?

@tsteur
Copy link
Member

tsteur commented Jun 9, 2015

Yes, that would help

@mattab mattab modified the milestones: 2.14.1, 2.14.0 Jun 16, 2015
@Guite
Copy link
Author

Guite commented Jun 19, 2015

Any update yet? I sent the credentials at the 9th of June, did you receive them?

@tsteur
Copy link
Member

tsteur commented Jun 22, 2015

I'll have a look now. Sorry the mail went into the spam folder

@tsteur
Copy link
Member

tsteur commented Jun 23, 2015

The problem seems to be actually not in Piwik itself. When tracking ecommerce items it sends a wrong JSON and it cannot track the items.

For example if you go to the actual website of id 34 and execute the following in the console

JSON.stringify([1, "test"]);

we get this output:

[1, \"test\"]

But expected output is:

[1,"test"]

We tried to find what causes this but couldn't 100% identify it. We presume it is caused by prototype.js library. Maybe you have an idea what causes this? Can you let us know so we can create an FAQ entry for this?

@Guite
Copy link
Author

Guite commented Jun 23, 2015

Hi @tsteur
thanks for elaborating. I tested that on a few sites and doubt that prototype.js is causing this problem, because it is also used on a few other sites where the test works successfully. I am going to try identifying where this comes from and report back afterwards.
Weird that all this worked before the update though.

@Guite
Copy link
Author

Guite commented Jun 23, 2015

Intermediate results: it is indeed related to prototype.js (in case an older version is used).
I dumped a page to a local test file and iteratively removed stuff. I can reproduce the problem with an almost empty file where only prototype is loaded in version 1.6.1. On another site I had briefly tested version 1.7.1 is used where everything works fine. Further investigating...

@Guite
Copy link
Author

Guite commented Jun 23, 2015

Confirmed: updated prototype to latest version 1.7.2 and it works.
Going to update this on all affected sites now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

3 participants