Native Target App - Mobile - profileParameters

Avatar

Avatar

garora8

Avatar

garora8

garora8

12-06-2020

For the mobile app- Native implementation we are trying to add a banner dismissal code so that we know that user has dismissed this banner and they should see the next activity in the list. After following the Adobe documentation we are sending it as profile parameters as you can see below request but for some reason, the profile is not getting attached to the user so we don't know if the user has dismissed the banner or not and the user seeing the same banner again and again.


Also - In the target, I don't see user.mobile_banner_dismissed_clicked_AS00839_AI_SA_ALL_SG_DM_ACAI0240_XT is coming back so I am not sure what I am doing wrong here.

Any more questions let me know

 

Any help would be highly appreciated as I am stuck don't know how to move forward. Please help

"execute" : {
    "mboxes" : [
      {
        "index" : 0,
        "name" : "dashboardMiddle_NonsecureAccT3",
        "parameters" : {
          "a.OSVersion" : "Android 2.0"
          
        },

       "profileParameters":{
                "mobile_banner_dismissed_clicked_AS00839_AI_SA_ALL_SG_DM_ACAI0240_XT":"true"

      }
        
View Entire Topic

Avatar

Avatar

emdobrin

Employee

Avatar

emdobrin

Employee

emdobrin
Employee

17-06-2020

Hi @garora8,

 

The request body fragment with profileParameters you shared looks correct to me. As long as you are sending these profile parameters in the Target API calls it should show in the Target UI. Please note that it usually takes a few minutes until they become available in the UI after you sent them for the first time from the mobile app. Then you should be able to create new audiences with this Visitor Profile parameter like in the screenshot below and use it in your activities:

Screen Shot 2020-06-17 at 4.23.50 PM.png

 For Charles setup, I recommend following the charlesproxy documentation. Alternatively, you can enable verbose logging mode in your app:

MobileCore.setLogLevel(LoggingMode.VERBOSE);

and check the logs in Android Studio. You should then see the Target requests sent by the Mobile SDK.

Let us know if this is working for you and your development team. 

 

Thank you,

Emilia Dobrin

 

 

garora8
Thanks, Emilia, It has been more than 5 days since we made a call via API to the profile pararmetere and it's not showing in the Target UI. Next step would ask sdk devleopers to add log(MobileCore.setLogLevel(LoggingMode.VERBOSE);may be this would help. Thank you very much for your help.)
garora8

HI Emila - It is working fine now. The values are coming back in the Target UI and everything is working as expected. Not sure why it was not coming in the profile list earlier. Thank you very much for your help 🙂

emdobrin
Great, thank you for the confirmation. All the best, Emilia Dobrin
garora8

hI emordin,

 

I have another problem now - wondering if you can help

 

We have a mobile-native implementation- we have found an issue where we set up a standard A/B/C Test with the equal user split but for some reason, users are stuck in experience B and everyone is getting experience  B



Some of the troubleshooting done already
Experience C to 100% > outcome still see the experience B
Experience B deleted > started seeing experience C then but now stuck in Experience C can't get to Experience A
Experience C now-deleted > able to see the experience A

I was expecting random traffic to go through as normal and random to Experience A , B or C

Any response will be appreciated