You can use Remote Config to provide custom experiences for users based on
the date and time they first open your app, including the following use cases:

- Provide different onboarding flows as users join your app.
- Expose incentives or features hidden behind feature flags or toggles to new users after a certain date.
- Provide custom experiences to users who joined during a specific time period.

Let us say that you want to provide an in-game gift to new users to encourage
initial engagement and retention, *and* you want to provide a different reward
to a group of longtime users. You can create a parameter named
`extra_coin_splash` that controls a dialog that offers free in-game currency
with a customizable message, number of bonus coins, and maximum number of times
to re-display the offer if the user has not accepted the offer. You can use the
in-app default value as the parameter default, and then create two conditions.

First, add a **Conditional value** to your
`extra_coins_splash` Remote Config parameter that targets a specific
Android or iOS app, set **First open** to a date and time in the future, and
then set the parameter value to:

    {"banner_text": "Welcome! Enjoy some extra coins!", "bonus_coins": 15, "max_display_retries": 2}

Next, add a condition for an existing user group that you want to reward, for
example, all users who joined in July and are still using your game in October.
To do this, add another **Conditional value** to the `extra_coins_splash`
parameter with **First open** set between July 1 and August 1, and set the
parameter value to:

    {"banner_text": "Thanks for being a loyal user!", "bonus_coins": 30, "max_display_retries": 2}:

Your final `extra_coins_splash` parameter will look like the following:

![Remote Config parameter with conditional
values](https://firebase.google.com/static/docs/remote-config/images/RCUC_5_NewUserTargeting_1.png "Remote Config parameter with conditional values")

After you publish your config with this parameter, both groups of users will
receive the extra coin parameter values you configured after their next fetch.

As a next step, try an [A/B Testing experiment](https://firebase.google.com/docs/ab-testing.md.txt) or
[Remote Config personalization](https://firebase.google.com/docs/remote-config/personalization.md.txt) with your
parameters and targeting conditions, using different banner messages and bonus
coin amounts.