Hi There, It completely depends on the business requirement how many
server calls need to be sent per page. ~6-7 server calls seem to be a
bit on the higher side. Generally, we see 3-4 calls max. However, if
each server call is sending different data then it might be useful for
the analysis as per the client's use case. If the data sent in the
server calls is the same then you may check the implementation and
rectify it.Hope this helps!
Hi there,Thanks for sharing the error ID. I checked back end logs and
below is what we are getting -"Error message returned by AMO search
account api= 'Login does not have access to the Advertising Account'\"Do
check that you have enabled advertising Analytics at report suite level
before creating the
integration.https://experienceleague.adobe.com/docs/analytics/integration/advertising-analytics/advertising-analytics-workflow/aa-provision-rs.html?lang=en#advertising-analyticsSecondly,
please che...
Hi,Unfortunately, this is not what the issue is.When some changes are
made in VRS, it is pre-selected in DWH. And then there is no warning, no
error message, no nothing. Anyways please ignore as I have raised a bug
for the same.
Description - As per current behaviour, as long as the Virtual Report
Suite is Data Warehouse compatible, you would be able to run the
request. However, if it is not compatible you will still be able to
create the request with this VRS, with failed status and no prior
warning.There should be a warning or an error message on selection of
Virtual reports which are not DWH compatible. Why is this feature
important to you - It is quite misleading as there are several VRS and
we won't remember which ...
Hi there,Product View Metric is only available with Reporting API 1.4
when the source is data warehouse. When the source is Adobe Analytics
(default reporting) then product view is not available. If you use the
following in the body of the POST request, you will be able to see
productviews:{"reportSuiteID": "reportsuiteid","reportType":
"warehouse"}https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-warehouse-api/index.md
Hi,I checked this error and below are the
logs-\"errorCode\"😕"insufficient_access\",\"errorDescription\"😕"No
access to Analysis Workspace granted\" Please reach out to admins to
provide you the sufficient access. Regards,Shefali
Sure. The reason for that is the oAuth integration created in Adobe I/O
should have https://www.getpostman.com/oauth2/callback as the "Default
redirect URI" and https://www\\.getpostman\\.com as the "Redirect URI
pattern".
Hi, The newest versions of app measurement code now can do post requests
as well as normal get requests. It automatically sends image requests
using HTTP POST if they are too long.AppMeasurement doesn't have an
option to manually force a POST call. It will, however, automatically
generate a POST call if the request size is greater than 2047 bytes.
When a POST is done the debugger will not show the request, you have to
take the post request information and run it through a url decoder like
http:/...
Hi there,This error seems to be coming due to the client ID and
credentials placed while retrieving the access token. You need to make
sure of the below settings:Go to Postman (preferably the latest
version).Under "Authorization" tab, select "OAuth 2.0" as the "Type".
Click on "Get New Access Token".Token Name: Enter any nameGrant Type:
Authorization CodeCallback URL:
https://www.getpostman.com/oauth2/callbackAuth URL:
https://ims-na1.adobelogin.com/ims/authorize/v1Access Token URL:
https://ims-...
Hi There, In order to disable "Offline Enabled" for Mobile Launch
property, you need to go to Launch property >> Adobe Analytics
extensions. A screen as below will appear to you:
https://docs.adobe.com/content/help/en/core-services-learn/implementing-in-mobile-android-apps-with-launch/configure-launch/launch-add-extensions.html
In case you want to change timestamp setting of the report suite,Go to
Adobe Analytics > Admin > Report Suites > Edit Settings > General >
Timestamp Configuration
.https:...