Added adobe marketing cloud debugger on chrome and I am able to see the requests, but couldn't able to see anything on my AEM dashboard (page views, visits, ect). I am running the application form localhost. Can anyone help me to resolve this?
@btripple I think these events [ s.t(); ] are fired since I have this line [ var s_code=s.t();if(s_code)document.write(s_code) ] in my code. I had added adobe debugger for chrome which will show the request (image attached). There is something in my browser console as well (image attached).
julienp80647070 I have checked the configuration, and there is no exclusion of IP. Still not able to see the reports on my omniture dashboard. Do I need to mention/add the host(localhost) somewhere in the omniture dashboard?
My tracking server is j********n.sc.omtrdc.net and I am hitting from localhost is that a problem??
Hello Adobe community,
What reports in Adobe Analytics are you trying to view?
If you capture a list of variables, then if they are standard they will appear in the various menus and sub menus(Traffic Reports > Pages > Pages, is for Pagename as an example). If they are custom you may need to have some of the menu setting adjusted to allow you to view them.
Go over this get a idea on how to implement the basics. I think you also may have to look at what is called your data layer.
The work I with angular I was involved with we used the angular frame work to inject our header and footer when need as well as used direct call rules. This was very efficient and saved alot of the headaches you seem to be having.
btripple thankyou. Even I have the same doubt, there is a report suite for the mobile app on the omniture dashboard which has been created by the client. Do I need to create one for the website? or can I use the same.
selvasajin - I don't think that matters but some choose to separate web from app. I would ask them to verify they provided the right report suite ID. Ask for a screenshot of the ID within the interface, better yet gain admin access to confirm yourself.
Report suite ID's are in essence data silos - you're not going to see any data if the selected report suite in Adobe Analytics doesn't match the RSID in an image request.
If you've 100% verified the image request RSID matches the report suite you're trying to pull data from, open a new workspace project and bring the 'page' dimension. You should see at least 1 line item, with the value 's.landingPage'. This means the implementation is working.
The fact that you have some variable names when they should be variable values is an indicator that you've wrapped variables in quotes in your JS. You'll want to make sure the image requests are sending the variable values, not the variable names themselves.
Thanks Gigazelle for the update,
Actually I had tried these variables/variableValues in my sample page code as a part of development, still no reports on the omniture dashboard:
The s.events and s.channel remains same as strings
Here are the options that I had tried
/* You may give each page an identifying name, server, and channel on
the next lines. */
/* Conversion Variables */
Out of curiosity, why not use DTM? It is so much easier to implement Analytics, and legacy implementations are becoming increasingly obsolete.
Also, based on what I'm seeing, I don't see anything else that would impact data collection. In order to troubleshoot the issue any further, we will want a public URL that we can access to figure out exactly what's wrong.