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:...
Download link, custom & Exit links are not available in Power BI. As a
workaround, you can create a report in report builder and publish it to
power BI.
https://docs.adobe.com/content/help/en/analytics/analyze/report-builder/publish-powerbi/integration-power-bi.html
Hey Robert, Few things I would like you to check:1. You are using the
updated version of the browser.2. Disable non-Adobe
extensions(chrome://extensions/) or plugins like ghostery from your
browser. 3. Clear browser cache and try again. Let me know the insights!
Hi Shalinee, As far as I am concerned, Analytics itself doesn't make
large cookies. If you are getting cookies that are large in size then I
am assuming it would be like a custom plugin you might have implemented
storing some values in a cookie that keeps appending things. Other
scenarios I could think of is: retrieving values from the URL;
concatenating values to pass to Analytics et cetera.I believe you would
need to evaluate your plugins you are using.Also, we would be needing
steps to reprod...
Hey there, In order to enable Adobe Analytics API, you must have product
access to Adobe Analytics for that organization. Moreover, either system
admin or developer accesses are required via admin console of Experience
cloud(https://adminconsole.adobe.com).You need to reach out to your
existing system admins of Experience Cloud to provide you the requisite
access.https://www.adobe.io/apis/experiencecloud/analytics/docs.html#!AdobeDocs/analytics-2.0-apis/master/create-oauth-client.md
If it still ...
Hey there, As you already know, Adobe Analytics uses cookies to identify
visitors. Each cookie has its expiration as mentioned in the
document:https://docs.adobe.com/content/help/en/core-services/interface/ec-cookies/cookies-analytics.htmlThese
cookies are in place until expired, or browser cache is cleared or an
incognito window is used.Hope this helps!
Hey, There is no separate license for customer attributes. However, it
does get provisioned at organization level by our internal team. You may
contact the Adobe account manager of your organization who can further
point you to the right team. If you need account manager information,
please reach out to client care team[clientcare@adobe.com].
Hi Balak, There could be multiple scenarios why the report did not fetch
the expected results:1. The whole server call is excluded. This can be
analyzed by fetching data feeds at your end.2. It only impacted a
specific eVar because of the setting of an eVar et cetera.I know it is a
late post, but if you are still facing this issue, I would rather
suggest you raise a case with the client care team for review.
Hey Philip, The s.linkTrackVars variable is a string containing a
comma-delimited list of variables that you want to include in link
tracking image requests ( tl() method). I believe the reason eVar is not
set when same piece of code is written again is because it resets value
of linkTrackVars. For instance: s.linkTrackVars = "eVar1";s.eVar1 =
dataElementName;will set eVar1 s.linkTrackVars = "eVar2";s.eVar2 =
dataElementName;this will only set eVar2 To fire both the variables on
the same server ...
Hey Pradeep, It depends on multiple factors why a domain is not
considered as an exit link. There can be two scenarios when your
internal domain is redirected to external link. One is open a popup and
second is change the internal URL to external on the same page.To handle
both of the above scenarios, make sure you perform the below steps:1.
Please add javascript:, mailto:, tel: in Never track list.The
default value is a javascript command that returns the hostname of the
URL for the curre...
Hi there, Visitor ID service should serve the same MID as long as you
are using same Marketing cloud ORG ID in the configuration and the
demdex cookie is present. To get same mid across app and web, you may
implement appendVisitorIDsTo function and that will help your use case.
Hope this helps!
Currently, clearVars does not clear variable values of a context data
variable.We are assigning some context data variables to send in a
beacon. But we have multiple beacons fired on the same page, and we are
seeing the same context data variables are being sent every time and not
being cleared.I know, the recommended way would be to use ManageVars
plugin to clean up the value of multiple variables including context
data variables.However, it would be great to simplify the task and add
context d...
Hi,Using the methods trackState and trackAction you are able to send
additional data.Steps to perform. To answer your query, you will need to
migrate the processing rules to Analytics interface as mentioned here.
As you are familiar with "props and eVars" in Analytics, you will notice
that these variable names are not in the AEP SDK. All key/value data
coming from the SDK will be sent as contextData variables , and as such
will need to be mapped to props or eVars (or other variables) by using
Pr...
Hey,Sure you can.s.visitorID = "abc123";You can set it in Adobe
Analytics tool > Custom code.OR You can set custom value via DTM and
Launch too.Create a data element to populate the object with custom
value and assign it in Visitor ID text box as in my previous response.
Hey there, This is currently being worked upon by the Engineering team
and will be fixed in August release(13th August).Do reach out to client
care if issue persists after 13th.
Hey there, visitorID is now integrated in Adobe Analytics tool/extension
in DTM and Launch respectively. As rightly mentioned by you, it helps
you set custom unique identifier for the visitor.
https://docs.adobe.com/content/help/en/analytics/implementation/vars/config-vars/visitorid.html
You may go to DTM > Go to your property > Edit Adobe Analytics tool >
Cookies > Visitor ID: Similarly, you may set Visitor ID in Launch.Once
implemented, you will see 'vid' in the server call(Developer tool >
Ne...
Hey, The website can use either DTM staging or Launch staging embed
code. You can link DTM and Launch embed codes in production environment
but similar is not available for staging. After upgrade to Launch, for
staging you will have to use the Adobe Launch staging endpoint. It is
not possible to link the legacy DTM staging endpoint to the Launch
Staging Endpoint. So you will need to update the embedded code on your
staging websites.https://www.youtube.com/watch?v=4DyA1nqtgVgHope this
helps!
Hi there, The linking process allows you to take the DTM Production
embed code, with its matching host location, and use that same embed
code with your Launch production environment.The linked embed code will
load one of two things:1) The DTM Production library -or-2) The Launch
Production librarywhichever is most recently published.When we link one
DTM embed code to Launch, and publish it to production, the Launch or
DTM code will work for that website as per the existing rules/data
elements et...
Hi there, If you are using the Adobe Experience Platform Mobile SDKs
with Adobe Launch, you may also install the Adobe Analytics Mobile
Services extension to use Adobe Mobile Services features such as in-App
messaging, push notifications or Acquisition links. For more information
see Adobe Analytics - Mobile Services . For reference:
https://docs.adobe.com/content/help/en/mobile-services/using/home.html
Hope this helps!
Hi there,Editing configuration of the Launch web property will directly
take into effect(with no publishing required). Although the "Domain"
field is required, the Launch property will work on any domain where
it's implemented.Also, you may add multiple domains to the same property
as per your requirement. Hence, as a recommendation rather than deleting
the existing domain and replacing it with a new domain, you may directly
add a new domain to the list. Reference document:
https://docs.adobe.co...
Hi there, Unfortunately, there isn't any force build in DTM. However, if
you are still facing issues, you may contact the client care team and
they will help troubleshoot further.
