- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi Sonny,
Yes, the Google Analytics/Adobe Analytics idea is bad, it was if the location to find comes from the website(s) that your company manages by their own.
For the past webApp calls:
Httpd access log files is the king for getting full view. But huge files...
Many tools are dedicated to analyse log files, and some for httpd access files.
But being on Cloud hosted, you won't be able to use them.
I don't know if Adobe support team will accept to send you an extract of httpd log files, filtered on your webApp and sub-domain name prefix of the url, so you could analyze like this sample record (for IIS httpd server).
Here true record, replaced by sample value:
Ask for filtering on https://yoursubdomainhostedbyadobeoncloud/webApp/yourwebappinternalname
2019-09-05 00:01:21 <AdobeCampaignIPaddressserver> GET /nl/gen/min/WA-fr-8af691832ebdf28de8c5eb70fa258844.js - 443 - theclientIPaddresstocheck Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_14_5)+AppleWebKit/605.1.15+(KHTML,+like+Gecko)+Version/12.1.1+Safari/605.1.15 https://yoursubdomainhostedbyadobeoncloud/webApp/yourwebappinternalname?origin=yourspecificvalue 200 0 0 0.
For the coming calls:
Please modify your webApp, add some Javascript code to collect information about http referrer and other useful information (http headers, etc, store these values into web.log files (with logInfo()) or better in database tables (such as webapplog schema extended custom field) and republish it, so for coming calls, you will be able to have detailed information and better understanding.
Regards
J-Serge