Migration from DTM Mobile to Adobe Launch Mobile

[Luca_Lattarini]

Hello everyone,

I am working on the migration from DTM to Launch. Currently I have only one DTM property for both Mobile and Web (Same Web property) and Adobe Mobile Service. Seeing that Adobe Launch allows to create one  web property for web site and one web property for Mobile, is it a good choice to split DTM into two different web properties by considering that I have an Hybrid Mobile App implementation? 

In addition I noticed that it is possible to install Adobe Mobile Service  as extension in Adobe Launch, could you explain me which benefit of it?

Thanks

Luca

[VaniBhemarasetty]

Hi @Luca_Lattarini , 

Splitting one property into two web properties, completely depends on one's choice, however you need to be mindful of rules, custom codes, data elements which are applicable of web property and mobile property. 

Also , below are the reference links for migration from DTM to Adobe launch 

https://docs.adobe.com/content/help/en/launch/using/reference/upgrade/upgrade-preparation-guide.html

https://docs.adobe.com/content/help/en/launch/using/reference/upgrade/upgrade-faq.html

When it comes to advantages of using Adobe mobile services for a mobile app, below are some of them 

• Acquisition: In Acquire, you use paid, owned, and earned media to drive user acquisition for app downloads across the leading app stores. Acquisition feature of Adobe mobile services can help you with
  • Tracking links across app stores
  • Deep linking into apps
  • Post back integration with advertising networks
  Using Adobe Mobile Services, you can accelerate the app user acquisition process.
• Location:You can define geographical locations that you can use for correlation purposes in reports, target with in-app messages, and
  more.
• Messaging: In - App messaging, Push messages can be delivered to users in real-time based on their actions using Adobe mobile services

You can also refer to these links to know more about Adobe mobile services 

https://marketing.adobe.com/resources/help/en_US/mobile/mobile.pdf

https://docs.adobe.com/content/help/en/mobile-services/using/get-started-ug/gs.html

Hope this helps

[Luca_Lattarini]

Hello Bhemarasetty_vani, thank you for your feedback. I just noticed that the Mobile App tracking comes from Adobe Mobile Service. In Adobe Mobile Service I can see the mapping with my Report Suite but I dont see the rules to track mobile App. Do you have any suggestion, how to verify that??

[Ishan_Sinha_]

Hi @Luca_Lattarini ,

In addition to what @VaniBhemarasetty mentioned, you will need to use a mobile property in Launch if you were to leverage the AEP Web SDK for mobile tracking. Further you can use Adobe Analytics - Mobile Services extension in Launch and retrieve the existing app from Mobile Services to use it in rules, etc.

Here's a doc that talks about it - https://aep-sdks.gitbook.io/docs/getting-started/create-a-mobile-property

I hope this helps!

[Luca_Lattarini]

Hello @Ishan_Sinha_,

In case we dont use  AEP Web SDK for mobile tracking but only Adobe Mobile Service. Can I use Adobe Mobile Services with the Experience Platform mobile SDKs?

Thanks

[Ishan_Sinha_ · Accepted solution]

Yes, @Luca_Lattarini .

You can continue using the 4.x SDK along with the Mobile Services. However, it's support will end on August 31, 2020. So, it's recommended that you switch to AEP SDK (5.x SDK) as that will be eventually done.

Thanks!

[Luca_Lattarini]

Hi @Ishan_Sinha_ it means that it is better to migrate the current tracking (evar, prop, event) from Adobe Mobile Service to Adobe Launch. Do you have some tutorial where I can find how to migrate Adobe Mobile Service? Thanks