yuhuisg

Re: Chatbot interactions - Adobe Analytics implementation best practices - Adobe Analytics

As with all measurement, you need to consider your business objectives. Usually, it boils down to determining what is considered "using the chatbot". Besides opening the chatbot, it could be number of messages, time between replies, etc etc. After you define that, then you'll know what and how to measure.

Re: Upgrading extensions — best practices - Adobe Analytics

Your understanding is correct.If the error is at your end, e.g. the extension introduces something new in its components that your rules/data elements break, then you have no choice but to fix your rules/data elements.If the error is at the extension's end, like what had happened with the Adobe Target v2 extension, then you can still build your libraries in development (and staging), but don't publish the extensions to production until the extension has been fixed.

Re: DEFERRED: Collecting metrics on downloaded files - Adobe Analytics

There are 3 requirements for AA to track download links automatically:You must have enabled "trackDownloadLinks" in AppMeasurement. See https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/trackdownloadlinks.html?lang=en .Your link's extension, "xd" in your case, must be in the list of file extensions that AppMeasurement recognises as downloadable file types. See https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/linkdownloadfiletypes.h...

Re: Upgrading extensions — best practices - Adobe Analytics

Usually, I "close my eyes and upgrade" for the following because they're 99% safe (note: I have not verified that percentage! 😜😞CoreExperience Cloud ID ServiceAdobe AnalyticsAdobe Client Data LayerAdobe Experience Platform Web SDKI'd put Adobe Target v2 in that list too, but there was one problematic update a few months back, and so that has made me more careful with that extension.Nonetheless, after performing extension updates, you should definitely test your Launch implementation extensivel...

Re: Entry path - Adobe Analytics

Answers to:Question #1: The second column is a breakdown of first action taken by the user (entry dimension (eVar40)).Question #2: Yes. (Or first occurrence of the dimension within a visitor, if your visualisation's setting has been set to "Visitor".)

Re: Better Control over Data Element Evaluation - Adobe Experience Platform Data Collection

Launch evaluates data elements when they are referenced. In your case, you should use your data element with a relevant rule that runs after a suitable "delay initial execution" period.That means when your Custom Event/Direct Call/other event triggers, then you should assume that your data element will be able to evaluate as expected. If you can't assume that, then you need to delay your Custom Event/Direct Call/other trigger until the data element can evaluate as expected.

Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection

@pradeep_nextrow instead of struggling to run the Processing Rules with the XDM variables directly, how about running those Rules with the mapped Analytics variables instead?E.g. instead of using "c.a.x.web.webPageDetails.name", use "Page" instead, since AA would have auto-mapped from "web.webPageDetails.name" to "Page" already. That's what I do.

Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection

@pradeep_nextrow shouldn't you be mapping from the 2nd column in the table at https://adobe.ly/3Ira5zD?So in your screenshot, instead of using "a.x.media.mediaTimed.starts.value", you should be using "c.a.media.view". Note: I don't use Adobe Video Analytics, so I am unsure if this will solve your problem. So the above is based on my understanding of the mapping in that help page's table.

Re: Multiple entry pages in same visit - Adobe Analytics

You're welcome! Glad that I could help. 😀

Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection

One thing that you can do is to use the Adobe Debugger to verify your assumptions.Sign into the Adobe Debugger and toggle to your appropriate organisation. Then, in Logs > Edge, enable logging by clicking "Connect". Now, when you send Web SDK events, you should see logs for Adobe Analytics. You can then see what are the fields that Adobe Analytics is receiving. Then you can use whatever is listed there in your Processing Rules.Here's an example of what I get from a single Web SDK event:I don't s...

Re: Multiple entry pages in same visit - Adobe Analytics

Oops, I should have said to use the Tracking Code Instances. Or in your case, the eVar Instances.Here's what I'm thinking: there are some of your users who were already visiting your website, then followed a link that has a tracking code to enter another part of your website, but still within the duration of a visit. Something like this:12:00pm: Open page A.12:03pm: Open page B.12:20pm: Open page C + tracking code.12:22pm: Open page D.Entry Page would be page A. And all 4 pages were opened in th...

Re: Multiple entry pages in same visit - Adobe Analytics

Instead of the Visits metric, try the Marketing Channel Instances metric instead.AA doesn't create a new visit when a new tracking code is detected.

Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection

Are you prefixing your XDM variables with "a.x...."?The following works for me:

Re: Page Name Report - Adobe Analytics

Awesome!FYI the old "Reports" interface will be disappearing soon (according to an AA product manager), so you should use Workspace all of the time now.

Re: Don't use clearVars! - Adobe Analytics

@PratheepArunRaj , manageVars runs inside s.doPlugins, so it manipulates your variables before they are sent to AA. My recommendation in this article, on the other hand, is focussed on clearing out variables after the hit has been sent and before the next hit. I suppose you could use manageVars to clear out unneeded variables before the hit is sent, but it has to be done properly so you don't clear out wrong ones incorrectly.

Re: Metrics to uncover technical reasons why pages have high bounce rates - Adobe Analytics

Out of the box, Adobe Analytics does not have any page load time metrics. You have to measure those by yourself in the tracking implementation.

Re: Page Name Report - Adobe Analytics

It sounds like you're running your report outside of the Adobe Analytics environment, e.g. not using Analysis Workspace. Is that correct? If so, could you describe the tool that you're using, or show some screenshots?

Re: I am getting this warning while loading the launch - Adobe Experience Platform Data Collection

Update all of your extensions. Almost all updated extensions have resolved this error message.

Re: date format in Adobe Analytics - Adobe Analytics

Unfortunately, Adobe has decided to follow the US date format, which the rest of the world doesn't use. 😂 So we'll just have to live with this US-specific quirk.

Re: Once the Web Vitals extension is installed, Data elements are created - How to create the rules? - Adobe Analytics

Here you go! I basically created data elements from what was available in my extension, and then log them out when a Web Vitals event occurs. console.group(event.$rule.name); console.log(event); console.group('Metric ID: ' + _satellite.getVar('Web Vitals ID', event)); console.log('Metric name: ' + _satellite.getVar('Web Vitals full name', event) + ' (' + _satellite.getVar('Web Vitals name', event) + ')'); console.log('Metric value: ' + _satellite.getVar('Web Vitals value', event) + ', delta: ' +...

Re: Once the Web Vitals extension is installed, Data elements are created - How to create the rules? - Adobe Analytics

Here are screenshots of an example rule that sets eVar43, eVar44 and eVar45 using the Web Vitals data:

Re: CNAME Setup - Adobe Analytics

I believe so.You can bring this up with Client Care too and see what they say.

Re: CNAME Setup - Adobe Analytics

The CNAME setup has nothing to do with your website's SSL certificate.The SSL certificate enables your website to be served to your users' web browsers via a secure HTTPS connection.The CNAME setup is to allow Adobe's tracking servers (2o7.net) to be recognised as subdomains of your own website.So yes, you still need to go ahead with the CNAME setup.

Re: WebTrends data migration to AA - Adobe Analytics

The WebTrends visitor ID is generated by WebTrends itself, right? So once you're 100% on AA, you will never be able to use that WebTrends visitor ID any more.Personally, I think you can import your WebTrends visitor ID into the required "visitorID" field in the batch file(s). But for all new data, you should just rely on the visitor ID that AA uses, whether it's ECID or something else.Point is, you can leave your report suite's timestamp setting alone.

Re: WebTrends data migration to AA - Adobe Analytics

See if the Bulk Data Insertion API is suitable for you: https://www.adobe.io/apis/experiencecloud/analytics/docs.html#!AdobeDocs/analytics-2.0-apis/master/bdia.mdBut in general, I wouldn't encourage importing historical data from somewhere into Adobe Analytics. For one thing, AA auto-deletes old data (https://experienceleague.adobe.com/docs/analytics/technotes/data-retention.html?lang=en). For another, your business reporting requirements might have changed or you might want to relook your requi...

Re: How to track and analyze the performance of my digital campaigns in Adobe Analytics? - Adobe Analytics

Elaborating on this: for step 2:Common query parameter:Most times, we use "cid" or "cmp" or "campaign", but it's really up to you. Whatever parameter you choose, your final landing page URL will be something like https://www.website.com/landingpage?cmp=campaign-tracking-code.The "campaign-tracking-code" is a single string that contains all of the information that you need to report on the campaign ad. Your organisation should have already defined the format of this string.Conversion variable (eV...

Re: Issue with AEP debugger - Adobe Analytics

I noticed that this problem is happening with your dev report suite, suggesting that you're testing in your website's development environment.Does the same problem happen in production too?

Re: How to ONLY count the non-repeating instances for a sepcific eVar in Adobe analytics? - Adobe Experience Platform

Must the media team count the green instances only? If not, would using the Visits metric be enough for them?Also, FYI there's an Analytics-specific forum at https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/bd-p/adobe-analytics-qanda

Re: Find page view in a visit between 2 specific pages - Adobe Analytics

Fallout! Yes, that's what I meant.I wonder if you could get your final segment by using a combination of "Only Before Sequence" and "Only After Sequence" too.

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe