Step 3: Handle Remote Config parameter values in your app's code
| Introduction: Test new AdMob ad format adoption using Firebase |
|---|
| Step 1: Use AdMob to create a new ad unit variant for testing |
| Step 2: Set up an A/B test in the Firebase console |
Step 3: Handle Remote Config parameter values in your app's code |
| Step 4: Start the A/B test and review the test results in the Firebase console |
| Step 5: Decide whether to roll out the new ad format |
At the end of the last step, you created a Remote Config
parameter
( SHOW_NEW_AD_KEY
). In this step, you'll add the logic to your app's code for
what your app should display based on the value of that parameter — true
(show the new ad) versus false
(do not
show the new ad).
Add the required SDKs
Before using Remote Config in your application code, add both the Remote Config SDK and the Firebase SDK for Google Analytics to your project build files.
Apple platforms
Add and install the following pods in your podfile:
pod 'Google-Mobile-Ads-SDK'
pod 'Firebase/Analytics'
pod 'Firebase/RemoteConfig'
Android
Add the following library dependencies to your build.gradle
file:
implementation
'
com
.
google
.
android
.
gms
:
play
-
services
-
ads
:
24.5.0
'
implementation
'
com
.
google
.
firebase
:
firebase
-
analytics
:
23.0.0
'
implementation
'
com
.
google
.
firebase
:
firebase
-
config
:
23.0.0
'
Unity
Download and install the Firebase Unity SDK, then add the following Unity packages to your project:
-
FirebaseAnalytics.unitypackage -
FirebaseRemoteConfig.unitypackage
Configure Remote Config instance
To use the Remote Config parameter values, configure the Remote Config instance so that it's set up to fetch new values for the client app instance.
In this example, Remote Config is configured to check for new parameter values once every hour.
Swift
remoteConfig
=
RemoteConfig
.
remoteConfig
()
let
settings
=
RemoteConfigSettings
()
settings
.
minimumFetchInterval
=
3600
remoteConfig
.
configSettings
=
settings
Objective-C
self
.
remoteConfig
=
[
FIRRemoteConfig
remoteConfig
];
FIRRemoteConfigSettings
*
remoteConfigSettings
=
[[
FIRRemoteConfigSettings
alloc
]
init
];
remoteConfigSettings
.
minimumFetchInterval
=
3600
;
self
.
remoteConfig
.
configSettings
=
remoteConfigSettings
;
Java
mFirebaseRemoteConfig
=
FirebaseRemoteConfig
.
getInstance
();
FirebaseRemoteConfigSettings
configSettings
=
new
FirebaseRemoteConfigSettings
.
Builder
()
.
setMinimumFetchIntervalInSeconds
(
3600
)
.
build
();
mFirebaseRemoteConfig
.
setConfigSettingsAsync
(
configSettings
);
Kotlin
remoteConfig
=
Firebase
.
remoteConfig
val
configSettings
=
remoteConfigSettings
{
minimumFetchIntervalInSeconds
=
3600
}
remoteConfig
.
setConfigSettingsAsync
(
configSettings
)
Unity
var
remoteConfig
=
FirebaseRemoteConfig
.
DefaultInstance
;
var
configSettings
=
new
ConfigSettings
{
MinimumFetchInternalInMilliseconds
=
(
ulong
)(
new
TimeSpan
(
1
,
0
,
0
).
TotalMilliseconds
)
};
remoteConfig
.
SetConfigSettingsAsync
(
configSettings
)
.
ContinueWithOnMainThread
(
task
=
>
{
Debug
.
Log
(
"Config settings confirmed"
);
}
Fetch and activate Remote Config
Fetch and activate the Remote Config parameters so that it can start using the new parameter values.
You'll want to make this call as early as possible in your app's loading phase because this call is asynchronous and you'll need the Remote Config value pre-fetched so that your app knows whether to show the ad.
Swift
remoteConfig
.
fetch
()
{
(
status
,
error
)
-
>
Void
in
if
status
==
.
success
{
print
(
"Config fetched!"
)
self
.
remoteConfig
.
activate
()
{
(
changed
,
error
)
in
// ...
}
}
else
{
print
(
"Config not fetched"
)
print
(
"Error:
\(
error
?.
localizedDescription
??
"No error available."
)
"
)
}
self
.
loadAdUnit
()
}
Objective-C
[
self
.
remoteConfig
fetchWithCompletionHandler
:^
(
FIRRemoteConfigFetchStatus
status
,
NSError
*
error
)
{
if
(
status
==
FIRRemoteConfigFetchStatusSuccess
)
{
NSLog
(
@"Config fetched!"
);
[
self
.
remoteConfig
activateWithCompletion
:^
(
BOOL
changed
,
NSError
*
_Nullable
error
)
{
// ...
}];
}
else
{
NSLog
(
@"Config not fetched"
);
NSLog
(
@"Error %@"
,
error
.
localizedDescription
);
}
[
self
loadAdUnit
];
}];
Java
mFirebaseRemoteConfig
.
fetchAndActivate
()
.
addOnCompleteListener
(
this
,
new
OnCompleteListener<Boolean>
()
{
@Override
public
void
onComplete
(
@NonNull
Task<Boolean>
task
)
{
if
(
task
.
isSuccessful
())
{
boolean
updated
=
task
.
getResult
();
Log
.
d
(
TAG
,
"Config params updated: "
+
updated
);
}
else
{
Log
.
d
(
TAG
,
"Config params failed to update"
);
}
loadAdUnit
();
}
});
Kotlin
remoteConfig
.
fetchAndActivate
()
.
addOnCompleteListener
(
this
)
{
task
-
>
if
(
task
.
isSuccessful
)
{
val
updated
=
task
.
result
Log
.
d
(
TAG
,
"Config params updated:
$
updated
"
)
}
else
{
Log
.
d
(
TAG
,
"Config params failed to update"
)
}
loadAdUnit
()
}
Unity
remoteConfig
.
FetchAndActivateAsync
().
ContinueWithOnMainThread
(
task
=
>
{
if
(
task
.
IsFaulted
)
{
Debug
.
LogWarning
(
"Config params failed to update"
);
}
else
{
Debug
.
Log
(
"Config params updated: "
+
task
.
Result
);
}
LoadAdUnit
();
});
Your app is now ready to handle the Remote Config parameter that you created during the A/B test set up earlier in this tutorial.
Use the Remote Config parameter value
Use the pre-fetched Remote Config
value in the loadAdUnit()
function to
determine whether the app instance should show (parameter value of true
) or not
show (parameter value of false
) the new rewarded interstitial ad unit.
Swift
private
func
loadAdUnit
()
{
let
showNewAdFormat
=
remoteConfig
[
"users"
].
boolValue
if
showNewAdFormat
{
// Load Rewarded Interstitial Ad.
// This should load your new implemented ad unit
// as per AdMob
instructions (the first step of this tutorial).
}
else
{
// Show the existing ad unit.
}
}
Objective-C
-
(
void
)
loadAdUnit
{
BOOL
showAds
=
self
.
remoteConfig
[
@"SHOW_NEW_AD_KEY"
].
boolValue
;
if
(
showAds
)
{
// Load Rewarded Interstitial Ad.
// This should load your new implemented ad unit
// per AdMob instructions (the first step of this tutorial).
}
else
{
// Show the existing ad unit.
}
}
Java
private
void
loadAdUnit
()
{
boolean
showNewAdFormat
=
mFirebaseRemoteConfig
.
getBoolean
(
SHOW_NEW_AD_KEY
);
if
(
showNewAdFormat
)
{
// Load Rewarded Interstitial Ad.
// This should load your new implemented ad unit
// per AdMob
instructions (the first step of this tutorial).
}
else
{
// Show the existing ad unit.
}
}
Kotlin
private
fun
loadAdUnit
()
{
var
showNewAdFormat
=
remoteConfig
.
getBoolean
(
SHOW_NEW_AD_KEY
)
if
(
showNewAdFormat
)
{
// Load Rewarded Interstitial Ad.
// This should load your new implemented ad unit
// per AdMob instructions (the first step of this tutorial).
}
else
{
// Show the existing ad unit.
}
}
Unity
void
LoadAdUnit
()
{
bool
showNewAdFormat
=
remoteConfig
.
GetValue
(
"SHOW_NEW_AD_KEY"
).
BooleanValue
;
if
(
showNewAdFormat
)
{
// Load Rewarded Interstitial Ad (new implemented ad unit)
// per AdMob instructions (the first step of this tutorial).
}
else
{
// Show the existing ad unit.
}
}
Add other checks for the parameter value
There are other areas in your application code where you'll need to check the value of this Remote Config parameter to dictate which ad experience will be loaded. For example, you can decide whether to reload an ad after the user has finished viewing the current one.
The fetch and activate calls should be made first to get any parameter value changes — for example, if you decide to end or create a new experiment.
From there, you can always check the value for the parameter using the following calls:
Swift
remoteConfig
[
"showNewAdKey"
].
boolValue
Objective-C
self
.
remoteConfig
[
@"SHOW_NEW_AD_KEY"
].
boolValue
;
Java
mFirebaseRemoteConfig
.
getBoolean
(
SHOW_NEW_AD_KEY
)
Kotlin
remoteConfig
.
getBoolean
(
SHOW_NEW_AD_KEY
)
Unity
remoteConfig
.
GetValue
(
"SHOW_NEW_AD_KEY"
).
BooleanValue
These calls will always return the same value for an app instance depending on whether it was placed in the control group or the new ad variant group, unless any changes were made in the Firebase console that were fetched and activated in the previous calls.
Step 2 : Set up an A/B test in the Firebase console Step 4 : Start the A/B test & review test results
