Adobe Experience Platform Data Collection

In some cases, we are facing a problem with adobe sdk`s in our app (we see these logs in dynatrace and firease logs):  Thank you for any help / clues.  

Hello Everyone, I have published the library in production yesterday (21/05/2020), when I am checking in the console with _satitlight.buildinfo, instead of showing a build date 21/05/2020, it showing old published library date(16/05/2020).for your reference screenshots are below.@Andrey_Osadchuk @je...

Giving your users a great mobile experience means constantly evaluating how they are interacting with your app and quickly responding with updates and optimizations. Based on these guiding principles, we built Adobe Experience Platform Mobile SDK from the ground-up to be modular, flexible and dynami...

Last year, we announced that support for Adobe Experience Cloud's version 4 mobile SDKs would end on September 30, 2020. Customers were encouraged to migrate and adopt the latest Adobe Experience Platform Mobile SDKs at their earliest convenience. Recently, we have heard from multiple customers that...

Hi,We made a few changes to existing rules for testing purposes.We want to revert these rules back to reflect what's in production.When we build a new library and add changed resources, Launch is going to add all the changed rules.We want avoid anyone accidentally publishing the changed rules that a...

I've cleared variables and running Adobe Extension v. 1.8.3, as you click through, events concatenate and they end up looking like  event1, event1, event1 event1 on the event Events variable. Clearing vars is definitely happening but not sure why events keep repeating.

Vimeo offer the option to track performance of videos embedded on websites into Google Analytics. I have the instructions for setting up with Google Tag Manager but struggling to convert this to work in Adobe Launch. Has anyone come across this before or made sense of the below? Many thanks. https:/...

We're doing testing having migrated from DTM to Launch.  Most things look right but there's something odd going on with the Facebook pixel. The tag is added via a rule, and then various events are triggered via additional rules based on either page load, or on button clicks.In Launch, it looks like ...

When loading AppMeasurement.js from a custom URL in the Analytics extension:What's the right way to initialize a global "s" object so Launch can populate it with report suites?When I do this: var s = s_gi('') I get this console message: Error, missing Report Suite ID in AppMeasurement initialization...

What is the best practice of Adobe Launch implementation to minimize the page load speed?