Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

mobile SDK 4 to SDK5 migration

Avatar

Avatar
Validate 1
Level 1
Analyptic
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
Analyptic
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
Analyptic
Level 1

08-02-2021

Hi All,

I am new to mobile analytics.  We are upgrading from SDK 4 to SDK 5 (Mobile AEP SDK) I havew a couple of questions that I hope someone can help me with?

We already have context variables being sent from the SDK 4, I have created the mobile property, added the necessary mobile extensions including Adobe.  My questions are:

1.  Do I need to create data elements and rules to attach the SDK 5 data or will the data continue to be sent to Adobe analytics, without intereference from me?

2.  Do we still have to use processing rules to map this data to exisiting eVars and props, or could this be done in the attach data event in a rule within Launch?

 

Many thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 3
Level 2
Uditgupta1
Level 2

Likes

3 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Boost 3
Level 2
Uditgupta1
Level 2

Likes

3 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
Uditgupta1
Level 2

18-03-2021

Hi @Analyptic ,

 

For new mobile implementation you have to do some necessary changes in App and Analytics:-

 1) You have to change the Config.trackAction/trackState to MobileCore.trackAction/trackState for Android and for iOS it will be ACPCore.trackAction/trackState, refer the document.

https://aep-sdks.gitbook.io/docs/

2) In Analytics, you have to use processing rules to map the evar and prop.

 

Hope this will help you in migration

Answers (0)