Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

Android Setup

Avatar

Level 1

I'm trying implement the Analytics package into an Android app for the first time. The company I work for has used Omniture for ages, and provided me with source code for earlier projects as an example to configure it for the one I'm now working on. My problem is, what they used seems to be a very different implementation that the current SDK I'm working with. They import import com.adobe.adms.measurement.ADMS_Measurement and use an ADMS_Measurement object to handle everything. The newer SDK is com.adobe.mobile.Analytics, has different method calls, and requires me to set up ADBMobileConfig.json This is where I've hit a wall. I was provided with an rsid and a server to use, but the config file wants to know target: clientCode and an audienceManager server, and I can't find exactly what those are supposed to be in any of the documentation I've looked through. If anyone could get me pointed in the proper direction, it would be very much appreciated.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

If you are implementing for the first time, you might be be better off looking at the demo app that is available at https://github.com/Adobe-Marketing-Cloud/mobile-services/tree/master/samples/Android rather than at a project that uses an earlier SDK. As you noticed the code and approach have changed significantly. If you do end out looking at the older SDK, this topic describes the changes between versions: https://marketing.adobe.com/resources/help/en_US/mobile/android/migration_v3.html

 

You can ignore the Target clientCode and audienceManager for now, the 4.x SDK supports integrations with those solutions but they aren't required for Analytics. For now if you just update the rsid and server you'll be set for Analytics (I can see how the docs are confusing here, we'll get this clarified).

One gotcha for first time set up is you need to find out if the rsid you were given is timestamp enabled (for offline data). If it is timestamp enabled, make sure you set offline enabled to true. If not set it to false.

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

If you are implementing for the first time, you might be be better off looking at the demo app that is available at https://github.com/Adobe-Marketing-Cloud/mobile-services/tree/master/samples/Android rather than at a project that uses an earlier SDK. As you noticed the code and approach have changed significantly. If you do end out looking at the older SDK, this topic describes the changes between versions: https://marketing.adobe.com/resources/help/en_US/mobile/android/migration_v3.html

 

You can ignore the Target clientCode and audienceManager for now, the 4.x SDK supports integrations with those solutions but they aren't required for Analytics. For now if you just update the rsid and server you'll be set for Analytics (I can see how the docs are confusing here, we'll get this clarified).

One gotcha for first time set up is you need to find out if the rsid you were given is timestamp enabled (for offline data). If it is timestamp enabled, make sure you set offline enabled to true. If not set it to false.