analytics report suite not generating report for configured urls

[#1]

Hello Everyone,

we have recently created a report suite for one of our development environment with base url as  Ex:"mysite.com" and "internal.mysite.com" and "mysite.com" added in internal filters. Adobe launch library was built selecting the created development report suite and AppMeasurement.js was generated which has got the developemt report suite details.

When the script was embedded in web pages and tested locally we can see the hits coming from "localhost" but when same script is embedded in pages for "mysite.com" it's not sending the data to the report suite.

We have verified the changes using observepoint plugin and Adobe experience manager debugger which clearly shows the analytics instance configured with 200 response code.

Any pointers in this would be of great help.

Thanks,

Sayabanna

[#2 · Accepted solution]

Hi Pablo,

The issue is now resolved and it's found that the domain period was not set properly and privacy setting was enabled for desktop browsers which excluded the hits from browser.After correcting both it started working properly.

Thanks,

Sayabanna

[#3]

Is it possible you have some network proxy rule allowing you to see pages and 20 request but its blocking teh adobe beacons?

Are the pages in question a type of SPA single page application?

[#4]

Hi All,

We have noticed that the hits are going only mobile browser or mobile emulators but not from dektop/laptop browsers.

Our launch is configured for web platform and not mobile. if anyone has faced similar issue can provide some pointers here.

the requests going from both mobile and desktop browser end in 200 response code indicating no network blockers and proper response post request to Adobe analytics

Thanks,
Sayabanna

[#5]

Hi Pablo,

Thanks for your response.

We have verified everything from reportsuite and launch and it's proper as the same configs are working for dev environment.

The issue where we are getting is another environment where we can hits getting recorded when the pages are hit from mobile or devices out of company network. The urls are allowed from network as well.Strange thing is we get 200 response code when the request is hit directly from browser.

Thanks,

Sayabanna

[#6]

Make sure your code has the correct RSID defined for each version of domain into its respective report suite.

You also may have domain level restrictions in your s-code so that its either not setup for newer domains event though observepoint sees code firing.