Create new post
Login

Community
Product Communities
Adobe Experience Platform

Adobe Experience Platform

Welcome to the Adobe Experience Platform Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Experience Platform.

Adobe Experience Platform

6216 Total posts

Most replies

Most views

jkunzNew Participant

Adobe Experience Platform

[AAE] Add list vars (and purchaseID) to Adobe Analytics extension rules interfaceApproved

List Vars (s.list1, s.list2 and s.list3) are common enough variables (moreso than Hierarchy, I suspect) but right now we have to move to custom code to set them. I understand it gets trickier because of the list-y nature of them, but in most cases my Data Element is making the properly-delimited list I want, and I just need a way to reference it in my rules. Also, it's odd to have Transaction ID in the interface, but not purchaseID- they're very similar, and it would be nice to be able to set them side by side and not in custom code.

117434

6 years ago

thomas_amslerNew Participant

Adobe Experience Platform

[AAE] Natural order of eVars, props and eventsDelivered

It would be great if the order of these 3 elements would be natural, even if you add a lower number later on it should be shown in the correct order as it was in DTM. As an example I had the following eVarseVar1eVar9 Then I added eVar5 so the order when I open the Global Vars of the extension configuration or in a rule in the Set Variable element the next time should be the following and nto eVar5 at the end.eVar1eVar5eVar9

201429

6 years ago

MattCrupeEmployee

Adobe Experience Platform

Extension level permissionsApproved

Would love the ability to assign permissions at the extension level so specific users, or groups of users, could only make changes to extensions they had access to. This would reduce internal governance efforts by minimizing users' abilities to poke around where they shouldn't. It would be especially useful for enterprise level organizations and those with strict security or legal protocols (i.e. GDPR/COPPA).

41801

6 years ago

Jennifer_KunzNew Participant

Adobe Experience Platform

Make dev and staging libraries default to upstreamApproved

Currently, if there is no library assigned to a dev or staging environment, it 404s. This can (reasonably) bother developers and break analytics testing on dev/staging/QA servers.Ideally, if an environment does NOT have a library currently on it, it would just use whatever is currently upstream in prod.

100774

6 years ago

khai_wongNew Participant

Adobe Experience Platform

Enhanced Search & Global SearchDelivered

Hi there,Enhanced SearchI believe the current search feature, perform on the "title/name", which is good,Will be great the search capability is searching to the lowest granular for example searching "scripts" as well.Global SearchCurrently, search is enable for every "tab" for example rules, data element, etc ...Will be great if Launch has a Global search, something like the one for Adobe Analytics ...thanksKhai

142587

6 years ago

PhilipLa2New Participant

Adobe Experience Platform

Improve build/minification error reportingApproved

Right now the minification process when building just returns if there was an error and the error itself, but no context around what code is causing it. This makes it hard to debug since there is no way to search all custom code in Launch; users instead have to go rule by rule to find the error. For example, I could have the following (valid) custom code in a rule: let myVar = "foo";return myVar; But since this is ES6, the minifier will fail, saying "There was an error minifying your custom code": This does not provide any useful information on where/why the minifier is failing. It'd be nice to see the rule/extension/data element, as well as the line number of what is causing the issue: Even if just a stopgap, being able to see the raw JS file before it goes through the minifier to search for the error would be helpful.

120746

6 years ago

benAllenNew Participant

Adobe Experience Platform

Make Rule Name Search in Launch Case SensitiveNew

It would be great if the rule search feature in launch was case sensitive. Currently, we use abbreviations like "CC" in the rule names that have custom code in them. When you search that in Launch you get both that acronym and rules that contains words with "cc" in them. Example Rule Name: "Medicare Plans - Patient Plans Accordion" would come up if you inputted "CC" in the search box. 

19020

6 years ago

franzliNew Participant

Adobe Experience Platform

Have "Event Type" listed in Rule displayNew

Idea: Have Rule / Condition / Access Context to display on the rule overview page to help with reviewing.Goal: Have more context and avoiding a step in clicking a page view when looking at rules.  

40991

6 years ago

analytics_unionNew Participant

Adobe Experience Platform

Flicker when using Direct Call inside Launch itself

My developer brought up an interesting problem with Launch: on a slow network, he sometimes gets a flicker when a page is loading. After numerous tests in Google Chrome where I throttled my network speed to "Slow 3G", I traced the problem to some Direct Calls _satellite.track() that are used in some rules' actions (implemented as custom code), i.e. there are rules inside Launch that include _satellite.track() themselves to other rules. When I blocked those min.js scripts in Chrome, the flicker problem went away. I also have Adobe Target, though on the pages that he experienced the flicker, there were no running experiments. We have also implemented the pre-hide script provided by Adobe (https://docs.adobe.com/content/help/en/launch/using/extensions-ref/adobe-extension/targetv2-extension/adobe-target-extension-v2.html#adobe-target-extension-with-an-asynchronous-deployment). Has anyone noticed this flicker before with Direct Calls?

32831

6 years ago

benAllenNew Participant

Adobe Experience Platform

Add ReactNative Instructions to Launch Mobile Property Environments TabNew

When you create a Launch mobile property it only includes instructions for installing the AEP SDK for fully native Android and iOS applications. The ReactNative instructions are found in the Adobe documentation (see link below) but are not readily available in Launch and you must combine that code with the appropriate environment file ID from your Launch property as well. It would be nice if these ReactNative instructions were present under the Environments tab inside of Launch for all mobile properties, and were pre-populated with the environment file ID in a manner similar to how the fully native instructions are currently formatted. https://aep-sdks.gitbook.io/docs/getting-started/get-the-sdk - React Native Instructions

19240

6 years ago

thebenrobbEmployee

Adobe Experience Platform

Technical Advisory: Upcoming End of Support for TLS 1.1

About this time last year, we announced the end of support for TLS 1.0 for libraries being hosted by Adobe. In the same vein, we want you to know that in the early part of April 2020, DTM and Launch will end support for TLS 1.1. TLS 1.2 will be the minimum allowed version.  We will update this post with the exact date when it moves closer and we determine what it is.As before, this is a security requirement coordinated across many Experience Cloud solutions so that they can be in compliance with certain data security standards required for companies who do credit card processing.Effectively, this means that browsers that do not support TLS 1.2 and above will no longer be allowed to retrieve a hosted library over an HTTPS connection. If you are using HTTPS to load your DTM or Launch library, then those browsers will no longer be able to retrieve and execute that library.Browsers that support TLS 1.2 and above - and will continue to function as they do today - are:Chrome 30 and up (

20130

6 years ago

Dave_Hamel_2024New Participant

Adobe Experience Platform

Bring back notesDelivered

I used the notation field at the bottom every time to add a note about what change I made and why. (well, most of the time ) I would like to see that in brought back in Launch. It's a good habit to get into.

100855

6 years ago

rohank28605872New Participant

Adobe Experience Platform

Retrieving AAM UUID from AEP 5 SDK to set in context data variable

Hi, How do we retrieve AAM UUID from AEP 5. The client wants to retrieve this ID and set it in a context data variable for both Android and IOS. I understand that the method to do this with Adobe SDK 4 was getallidentifiersasync. What is the method that we can use for AEP 5. is it identity.getidentifiers? If yes how do I then set the AAM UUID in a context data variable? Thanks and regards

34211

6 years ago

abhinava3441956New Participant

Adobe Experience Platform

evars and props are not populated on Adobe analytics

Hi Team,When I am sending the evars and props from the React Native code, the value and their counts are not reflecting on the portal.While I send the events they are reflecting there but not getting their values. Reference links of which I have taken the help are:https://docs.adobe.com/content/help/en/mobile-services/universal-windows/analytics-univ-win-plat/event-serialization.htmlhttps://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#track-app-actions My code for evars and props  which I tried is: function trackActionFunc(action, payload) {ACPCore.trackAction(action, payload);} trackActionFunc("Sign-in Status", { "&&evars": "eVar12:Splash" }); // function call for evarstrackActionFunc("Page Name", { "&&props": "prop1:Splash" });  //function call for propstrackActionFunc("Sign-in Status", { "&&events": "eVar12:Splash" }); //function call for events Please suggest a solution with sample

31231

6 years ago

Antti_KoNew Participant

Adobe Experience Platform

Adobe Launch synchronously and self-hosting best practices for possible file loading issues

Pretty simple stuff, just want to be 110% sure and understand are there any best practices or caveats around these issues.1. When Launch is deployed synchronously, there are two embed codes, one which you put in the <head> and another which you put before the </body>.Let's say we are self-hosting the script through another domain/cloud (if this matters in any way)a) What happens in browser if the Launch script in header is not available. So url doesn't exists. I guess you could ask this question regarding any .js file. Maybe you get error message in console that url X is not available or gives 404. But this shouldn't have any effect to user browsing the site, right?b) what happens (to browser) at the bottom of the page when satellite.pageBottom is trying to call/load. Again, nothing too serious for the end-user, maybe just some kind of notification in console or?c) Would it be best practice to add try catch for that, e.g. <script type="text/javascript">try {_satelli

28381

6 years ago

IvanMi1Employee

Adobe Experience Platform

Migrating from Adobe Mobile SDK v4.x? Ask your migration questions here

We are currently working on documentation to help support migrating from Adobe Mobile SDK v4.x to the Adobe Experience Platform SDKs + Adobe Launch. Let us know what questions you have about this process.

161773

6 years ago

rupaljain2408New Participant

Adobe Experience Platform

Rule executing asynchronously on web page with Adobe Launch

Hi everyone, We have recently migrated our property from Adobe DTM to Adobe Launch. We wanted our script to load asynchronously, hence we had removed "async" from our header script. The execution call for Direct call Rule is written in following manner in our code : try { window._satellite.track('commonsPageLoad'); } catch (error) { console.error(error); } finally { window.digitalData = {}; }Now , the execution starts with "try" block and call to DCR [ _satellite.track('commonsPageLoad') ] , but somehow, the "finally" block gets executed next before completing execution of DCR. This leads to clearing of datalayer , and no data goes with Adobe's image request, which is a serious concern for me. If anyone knows the reason behind this and solution, if any, Please let me know. Many thanks in advance !

52662

6 years ago

robayzmaNew Participant

Adobe Experience Platform

IOS Certificate PEM File for Adobe Campaign Standard Mobile App

Hi All,We are trying to make Push work for an IOS app and need a little information.I am looking for the documentation regarding the instructions on how to create the IOS Certificate (PEM) file for Adobe Campaign Standard?  I seem to recall that both the prod and sandbox certificate has to be in one file that is uploaded but can't remember much else. Kind regards  Robert

60511

6 years ago

LJP88New Participant

Adobe Experience Platform

Prevent GA Cookie from dropping

Hi All, I have the GA extension and want to prevent the GA (_GA) cookie from dropping but it appears this happens due to the extension being present, even when I have not added the extension as a condition/event/action in any rule. This is the same for the ECID but the ECID gives me the option in the extension to not fire based on criteria.  I am trying to do this so NO cookies drop until explicit consent is given (I am using the Evidon UCP extension). While I know I can fire GA as a script and remove the extension, I want to avoid that.  Thanks in advance!

27661

6 years ago

mikeb55262024New Participant

Adobe Experience Platform

Data Element - Empty String Default Value Bug?

Setting default value for data element 'JavaScript Variable' when the actually JS value is an empty string doesn't return the 'Default Value' is set within the data element. An empty string is returned instead. Since an empty string is considered to be a false type in JS, developers might expect then to rely on the 'Default Value' to be populated instead.  Is anyone else experiencing this? If so, this should be updated if the JS path resolves but return an empty string vs a ref error, then the data element should fallback on the default value.  

43461

6 years ago

elizeo.benavidezNew Participant

Adobe Experience Platform

Upgrading Adobe Analytics Extension Causes Build to Fail

I just upgraded to Adobe Analytics Extension v1.8.1 and now I'm seeing an error when trying to build. All I did was click the Upgrade button in the Extensions section and changed an existing rule.  ERROR:The "Adobe Analytics" extension has been upgraded on this property. The upgraded version must be included in this library by selecting the "latest" revision. Add it to your library, then rebuild. SOLUTION:After upgrading Adobe Analytics, and after you make a change to a rule, you must go to Publishing > Resource Changes > Expand the rule that you changed > Select the Revision with the word "Latest" in parenthesis > Click "Select this Revision" and follow the prompts. You should be able to build successfully.

36761

6 years ago

ambikat677427New Participant

Adobe Experience Platform

Working Library is showing red

Hi Everyone,I have setup a new library and created a data element . When I save the changes to data element using the library, the library shows me red instead green .The failed error message is "The "Adobe Analytics" extension has been upgraded on this property. The upgraded version must be included in this library by selecting the "latest" revision. Add it to your library, then rebuild."How can I fix it ?

77771

6 years ago

francescob83277New Participant

Adobe Experience Platform

Implementation of push messaging in Android

Hi all, based on the official documentation https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics-mobile-services#set-up-push-messaging related to the integration of the push messaging there is no mention about the fact that in order to receive push messaging it is necessary to create a class that extend FirebasemessagingService and implement the onmessagereceive method (explained here https://firebase.google.com/docs/cloud-messaging/android/receive). The result is that if we follow only the official instructions (retriving and send the token to mobilecore throught the setPushidentifier function) messages aren't received and showed in the application. Could someome confirm that in every implementation it is necessary also to implement code to handle and show the messages sent by the Adobe Mobile Marketing console? ThankYou in advance

42161

6 years ago

_eanilsenNew Participant

Adobe Experience Platform

Debugging dynamically added JavaScript

Hi. Is there any way to add breakpoints so that I can step through the code in the dynamically loaded scripts coming from Adobe Launch? I have tried adding //# sourceURL=name_of_file.js, but it does not seem to be working. Any help would be appreciated, thank you! Kind regards,Even A. Nilsen 

93451

6 years ago

danielalversNew Participant

Adobe Experience Platform

Launch API filters

I have the Launch API working fine.  We'd now like to start filtering some of the requests to produce a response subset.   When monitoring the normal https://launch.adobe.com/companies interface we can see that filtering for a specific value requires 'EQ ' on the front of the request: https://reactor.adobe.io/companies/COxxxxxxxxx/properties?filter[name]=EQ PropertyA This requirement isn't documented here https://developer.adobelaunch.com/api/guides/filtering/ . Besides 'EQ' are there other qualifiers, such as greater than, older than etc? Thanks for any information

26483

6 years ago