Analytics Testing

Avatar

Avatar

Scott_Landis

Avatar

Scott_Landis

Scott_Landis

25-10-2017

Hello,

I have an app in QA but have been, as of yet, unable to see successful analytic data reporting through AMS.

My expected process is to to create a project with a unique report suite name, go into AMS, add a new app and select the report suite name created in the On Demand Portal.

I am not seeing report suites that I create reflected in AMS.

The documentation, found here: Analytics in AEM Mobile say that the data should be passed through the same username and password that are used to login with AMS and to set up the Analytics in the Master account, but I'm seeing no data.

Does the application need to be live, and deployed through the App Stores, to successfully report? Or are there additional steps that can be taken to verify application reporting during test?

Thank you

-Scott

Accepted Solutions (0)

Answers (3)

Answers (3)

Avatar

Avatar

MatthewLaun

Employee

Avatar

MatthewLaun

Employee

MatthewLaun
Employee

27-10-2017

Scott,

Using back office tools, I found you as an admin under the Master Account Padi Worldwide Corp. That account doesn't yet have it's analytics login company set in the Master Settings. Only when that is registered do we (the royal we 😉 get notified to associate the report suites created for your projects with an Analytics login company (which I see as "Padi Worldwide Corp"). If you register the login company in Master Settings, it will initiate processes so the report suites are visible in AMS.

If you run into troubles, message me and/or create a support ticket in Daycare:

https://daycare.day.com/home/createaticket.html

Regards,

Matthew

Avatar

Avatar

MatthewLaun

Employee

Avatar

MatthewLaun

Employee

MatthewLaun
Employee

27-10-2017

Scott,

Glad to hear it. If you have a moment, please mark this as answered. It helps the odds that others with the same issue will find the answer.

Cheers!

Avatar

Avatar

Scott_Landis

Avatar

Scott_Landis

Scott_Landis

27-10-2017

Thanks Matthew, the question was in reference to another client under a different Adobe ID, but I spoke to the support team this morning and have solved the issue.