Skip to main content

What is Click to Load in Mobile Experience Builder?

In this article you will learn how Click to Load works in Mobile Experience Builder, and how to set up a reward that guests claim with a tap on the NextGen App Dashboard.

Written by Matt Ford

Overview

Click to Load lets you offer guests a reward that they have to claim. Instead of loading automatically, the reward appears as a button on the Dashboard of the NextGen App. When a guest taps the button, the reward loads to their account straight away. Guests who don't tap don't receive the reward. Click to Load is available on the NextGen App.

Click to Load helps you:

  • Drive app visits: give guests a reason to open the app more often.

  • Boost engagement: guests need to take action, which builds a habit of checking the app.

  • Keep offers targeted: only guests who engage receive the reward.

How it works

A Click to Load promotion has two parts. You set them up in order in Mobile Experience Builder (MXB):

  • Click to Load event: sets who is eligible, what they receive and when the offer is active.

  • Click to Load component: sets where the claim button appears on the Dashboard and how it looks.

Create the event first. You can't link a component to an event that doesn't exist yet.

The guest journey is: you create the event, the guest sees a claim button in the app, and the guest taps it to load the reward.

Setting up a Click to Load promotion

Step 1: Create the Click to Load event

In Mobile Experience Builder, go to Click to Load Events and create a new event. This sets up the reward but doesn't publish anything to the app. You'll add the component to the Dashboard in Step 4.

Click to Load Events page in Mobile Experience Builder

Step 2: Enter the event details

Complete the following fields:

  • Event name: for your internal reference only. Guests won't see it. Use the language buttons to add the name in other languages.

  • Reward available date and reward expiration date: when the reward becomes available and when it stops being available. Dates and times are in EST.

  • Wallet selection and wallet quantity or amount: the wallet to load and the amount to apply.

  • Attribute cost to: the store that the reward cost is attributed to.

  • Account Filter: the guests who can receive the reward.

Edit Click to Load Event form showing event name and reward dates

Edit Click to Load Event form showing wallet, store and Account Filter

Step 3: Publish the event and wait for guests to load

Select Publish & Update. MXB then adds the eligible guests to the event. This can take a few minutes, and MXB shows the status while it runs.

Click to Load Events list with the Publish and Update button

Status message while eligible guests are being added to the event

When every eligible guest has been added, MXB confirms that the event is ready to add to your Dashboard.

Status message confirming all guests have been loaded into the event

Step 4: Add the component to your Dashboard

Once all guests have been added to the event, go to the Dashboard page and add the Click to Load Reward component. Link it to the event you created in Step 1.

In the component settings, choose the image, description and buttons. These settings control how the component looks on the Dashboard.

Dashboard component list with Click to Load Reward

Click to Load Reward component settings

Step 5: Publish your changes

Publish your changes when you're ready. The component appears straight away, or on the start date if you've set one. It only appears to guests in the Account Filter you assigned.

Before you publish, check the layout in Dashboard Preview. Preview shows all content, even content that would normally be filtered or segmented, and the buttons aren't clickable.

What guests see

Guests see a Click to Load section on the Dashboard with a claim button. When they tap it, the reward loads to their account. Each reward card can show an expiry date. The component only appears to guests in the Account Filter.

Guest view of the Click to Load section on the Dashboard
Did this answer your question?