Migrating from Firebase to Target a/b test in mobile apps | Community
Skip to main content
W
wl_mobile_team
March 10, 2025
Solved

Migrating from Firebase to Target a/b test in mobile apps

  • March 10, 2025
  • 1 reply
  • 429 views

We are currently using Firebase remote config for a/b test on our mobile apps. We want to switch to Target and use a/b test feature.

 

We have gone through the documentation (https://developer.adobe.com/client-sdks/solution/adobe-target/) and integrated SDK in apps. But we are not understanding how can i pass/add "LOCATION" mentioned in https://experience.adobe.com/#/@wowcher/target/activities/new/A-B dashboard. Could you please help us to understand about the "LOCATION" (NOT Geo-location)

 

 

Best answer by kandersen-1

Hi @wl_mobile_team 

You might find this documentation helpful: https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/experience-cloud/target#implement-target-in-your-app 

I'm not an app developer, so this will be on a high-level, but hopefully it will get you in the right direction. 

Locations are defined as decision scopes or mboxes. These are essentially named areas in your app where personalized content or offers can be delivered. Here’s how they are defined and used:

1 Naming the Location (mbox):
  • Each location in the app that you want to optimize or personalize must be assigned a unique name. For example, you might name it home-screen or hero-home-screen
  • The mbox name is used in API calls to identify the specific location where personalized content should be delivered.
2 Defining Decision Scopes:
  • In the Adobe Experience Platform Mobile SDK, decision scopes are used to define these locations. They act as containers for delivering offers and tracking interactions.
  • You can use APIs like onPropositionsUpdate to fetch and update offers for a specific decision scope (location).

I hope this is helpful.

 

 

 

1 reply

kandersen-1
Community Advisor
kandersen-1Community AdvisorAccepted solution
Community Advisor
March 10, 2025

Hi @wl_mobile_team 

You might find this documentation helpful: https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/experience-cloud/target#implement-target-in-your-app 

I'm not an app developer, so this will be on a high-level, but hopefully it will get you in the right direction. 

Locations are defined as decision scopes or mboxes. These are essentially named areas in your app where personalized content or offers can be delivered. Here’s how they are defined and used:

1 Naming the Location (mbox):
  • Each location in the app that you want to optimize or personalize must be assigned a unique name. For example, you might name it home-screen or hero-home-screen
  • The mbox name is used in API calls to identify the specific location where personalized content should be delivered.
2 Defining Decision Scopes:
  • In the Adobe Experience Platform Mobile SDK, decision scopes are used to define these locations. They act as containers for delivering offers and tracking interactions.
  • You can use APIs like onPropositionsUpdate to fetch and update offers for a specific decision scope (location).

I hope this is helpful.

 

 

 

Test forum signature
Terms & ConditionsAccessibility statement

Loading footer...