Testing your Points & Rewards (P&R) is an important step before launching your experience to the public. This guide will walk you through key system behaviours, and testing offers using the Driftscape mobile app.
TABLE OF CONTENTS
What are Points & Rewards?
Points & Rewards is a feature in Driftscape that allows organizations to offer points at POIs that visitors can collect and redeem for rewards. It's designed to drive engagement, encourage local exploration, and support community initiatives.
While primarily used for live campaigns, testing is essential to ensure that points, rewards, and location rules function as you intended. There are a lot of important steps to follow when setting up your points & rewards, so it’s critical that you test the functionality after implementing them in the CMS. In some cases you may want to temporarily adjust some of the parameters associated with your Points & Rewards in order to make them easier to test.
Looking to set up your points and rewards? See Implementing Points & Rewards for a step-by-step guide.
Get Started: Testing Points & Rewards
Step 1: Publish a Points & Rewards Campaign
Before testing, ensure your Points & Rewards campaign is published to your organization. Test your Points & Rewards implementation before you make your content visible to the public by using Trial Mode.
For help and information on Trial Mode, see: Previewing Your Content
For steps to publish, see: Implementing Points and Rewards
Step 2: Test Non-Location-Based Point Offers
If you’ve published offers that do not require users to be on location:
Open any POI that includes a point offer without location based limitations
Tap Collect Points
Confirm the expected number of points is granted immediately
Step 3: Test Location-Based Point Offers
If you’ve published offers that require users to be on location:
Attempt to collect points from a location-based POI while not on-site. You should receive a message indicating you're not close enough.
Note: points that are collectible only when on location may not function as designed on some browsers on desktop. Points that are collectible only when on location will function as intended when accessed from our mobile apps, and in the web app on a mobile device.
Travel to the POI location and repeat the test, or create a test POI at your location. You should be able to collect the points if you're within the preset distance provided in the CMS. By default on-site rewards have a 100m radius. See Define Collectible Points for more information
Step 4: Test Point Collection Limits
If you’ve set a collection frequency (e.g. once every 2 days) for collectible points, ensure that they’re working as expected.
Collect points from a POI that has collection limits associated with those points.
Attempt to collect again immediately. Confirm that the app prevents the second collection and displays an error message
Return after the set number of calendar days has passed to test that collection is once again available
Note: If this field is left blank in the CMS, the default is one-time collection per user per location. If set to 0, users can collect points repeatedly.
Step 5: Test Reward Redemption
Each POI offering points also includes a Rewards button. Once you have set up your rewards in the CMS, follow these steps to test they are operating correctly.
Tap the Rewards button from any POI with an active points offer.
Any Reward that you do not yet have enough points for, will not show a “Get This Reward” button.
Attempt to claim a reward you do have enough points for. This should succeed and allow you to claim the reward.
Step 6: Test Reward Redemption Parameters
If you've configured reward limitations in the CMS, use the following steps to verify that they behave as expected:
Address Required: If this field is enabled, confirm that you are prompted to enter an address and phone number when redeeming the reward. This is important for any rewards that will be shipped.
Start and End Dates: Try to redeem the reward both before the start date and after the end date. Confirm that the reward is only available between the configured dates.
Collection Frequency: If a frequency limit is set (e.g., every 7 days), redeem the reward once, then attempt to redeem it again immediately. Confirm that the system prevents early repeat redemptions. Return after the set number of days and test again, you should be able to collect the reward provided you have enough points.
Expiry: Redeem a reward that includes an expiry (e.g., valid for 5 days). Confirm that the app displays the expiration date or status appropriately.
Step 7: Confirm Reward Details
Double-check key information from the user’s point of view:
Are point values accurate?
Are reward costs correctly shown?
Do contact emails and reward instructions appear as expected?
If something looks off, return to the CMS and verify:
Point values in the offer setup
Reward threshold values
Custom messaging or email contact fields in the reward setup screen
Known Limitations
Points are tied to your device’s App ID
Deleting and reinstalling the app will reset earned points
Use in-app testing methods (like Trial Mode) to avoid loss of test data
Driftscape for Web is not recommended for location-based testing
Browsers do not support accurate GPS
Clearing cookies resets rewards
Related Articles
If you need help or encounter issues during testing, reach out to your Driftscape representative or email support@driftscape.com.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article