Adobe Experience Platform

At Adobe Summit 2018 in North America, we made Adobe Experience Platform Launch available to all Experience Cloud customers.  Since that time, we've seen rapid adoption of Launch and have helped thousands of customers migrate over from DTM.Last year, in early October, we announced (here and here) that we are going to sunset DTM.  This means that DTM will be kept up to date with security and bug fixes, but no more feature development work is happening and that it would be unavailable at the end of 2020.  We also said that we would be introducing progressive restrictions on its functionality to encourage users to begin planning and executing the migration process.We are now approaching the first DTM Sunset Milestone.  In about 60 days, on July 9th, we will remove the Add Property button in DTM (we had previously announced this date as July 1, but pushed it back a bit because of release cycles and company events).This change means that beginning with the release on Jul

Hi Team,I want to integrate Hybrid Mobile App (Polymer JS) - Adobe Launch integration .  App has developed (Android & IOS ) using Polymer JS  with PWA framework .How can i implement Hybird mobile to launch. Do you have any documentation or inputs please provide me the same.Thanks - Satish

I have created a data element called "UserSessionID" and would like to pass that value to an eVar. When I go to select that data element from the list, it is missing.Any ideas? The DE is enabled and active.

HiWe have different SPAs needs to integrate on a common platform and every SPA have different domain. For this common platform, we have Web property configured in the DTM with necessary Rules. This means the tracking of this common platform is working perfectly fine.My question is, for the tracking of every SPA, when we integrate the SPAs with different domains on this platform, should we have to define the Web Property of each SPA with its specific domain and generate the Header and Footer codes to integrate on each SPA? Thanks

I have a pageload rule defined that fires for all pages. I then defined a second pageload rule that fires conditionally on one specific page. This second rule is supposed to fire an Adobe Analytics event. When the specified page loads, there is no event sent to Analytics. I can verify that the rule fires by adding an eVar to rule. The eVar does get sent, but the event does not. I am able to send the event via a direct-call rule and a manual call.Should this work with a pageload rule?Is there a reason a pageload rule doesn't send an event but will send eVars?

Hi!Has anyone been successful in tracking the latest Analytics version via DTM? been assigned to either track this as a data element  + setting it to an eVar or setting this in the global custom code/or rule?? Many thanks for the guidance with this.Haven't been able to make it work via the recommendations I've seen online.I found this recommendation: _satellite.getToolsByType('sc')[0].getS().version - I can see it in console but it doesn't work when I set it in DTM.Thanks for any insight and guidancePaulina

How to Add Adobe Analytics SDK for iOS project via Carthage?

Hi everyone,is there any chance to access the Cusomter Attributes in People Core Service via Adobe Launch?Thanks in advance!

Hi All,I have created customer attribute example  like as below with 3 records with alias id (crs_id)idnameemail1Jackjack@email.com2Samsam@email.com3Ramsrams@email.comQuestion 1 : How to delete a particular record from data source ?Question 2 :  How to flush/erase all records without affecting customer attribute ?RegardsRams

Hi,I wonder how reliable is this tool https://www.searchdiscovery.com/solutions/partners/adobe/adobe-launch/dtm-launch-assessment/to check the migration effort of DTM to Adobe Launch.Is this a good practice to use and fix the unsupported methods in DTM based on this report?Thank you

I compared iOS sdk with Android sdk and noticed that in iOS sdk isn't provided the ability to send additional context data with application lifecycle.In Android sdk clearly stated that: To send additional context data with your lifecycle call by using Config.collectLifecycleData(Activity activity, Map<String, Object> contextData), you must override the onResume method for that Activity and ensure that you call super.onResume() after manually calling collectLifecycleData. Is it possible for iOS?

Hi,I've published a library to production and want to remove it again, is that possible?-Robert

Hi Team,I would like to know about any officially SDK or Library for the Adobe APIs integration. As we are facing numerous issue while implementing Adobe APIs. However, there is very less supporting tools are available online to figure out the errors. Let us know is there any assistance for the same and your suggestion will be appreciated. Thanks,

Hello,We are currently using ADBMobile SDK in our iOS and Android apps for analytics tracking. Currently the tracking data is funneled into a single server, however, our analytics teamed asked us if it would be possible to have tracking data split into two different servers.I checked the docs and it does not seem to be possible. Nor can I create multiple instances of ADBMobile, each pointing to a different server.Can someone confirm whether this is possible.below is what we want to achieve.==== iOS APP ====Instance 1 of ADBMobile ---> Server 1 (ser1_config.json)Instance 2 of ADBMobile ---> Server 2 (ser2_config.json)==== Android APP ====Instance 1 of ADBMobile ---> Server 1Instance 2 of ADBMobile ---> Server 2Thanks,

Adobe Launch is capturing contextData by default (see above).  I want to push this data into an eVar in Adobe Analytics.  How do I push contextData into an eVar in Adobe Analytics?Thanks

Hi,I have a client who is setting a custom Visitor ID using the s.visitorID variable in their iOS and Android apps (SDK 4.x).The will be setting the timestamp on every hit leaving the app.They are keen to enable Timestamps option on the report suite, but have read the documentation that this is not supported, and that it can lead to out of order data.Timestamps Optional Important: If you are using Timestamps Optional, then do not set s.visitorID on data that is already timestamped. This can lead to out-of-order data and negatively impact time calculations (such as time spent values), attribution (eVar persistence), visit number/visit counts, and pathing reports. Timestamps not allowed (setting s.visitorID supported)Timestamps required (setting s.visitorID not supported)Timestamps optional (setting s.visitorID supported but not on timestamped hits) What is the reason for this limitation, and is it likely that this limitation will be addressed in the near fu

It seems that the latest iOS Heartbeat library releases are targeting iOS 10 and up. Is there any particular reason for dropping support for iOS 9? Or is the linker warning ("...was built for new iOS version (10)...") something that can be ignored, i.e. the library has incorrect deployment target set?Br,Mikko