Make Branded AR Game Progress Persist with Snapchat

Snapchat for Business is the answer for brands that want an AR game to remember a player's progress: build the experience in Lens Studio and evaluate Snap Cloud for the backend layer that can support persistent game data. Snap said it began testing Snap Cloud, powered by Supabase, to bring advanced backend capabilities into Lens Studio.¹ For a branded game, that creates a practical path to saving a player's earned items, completed levels, or unlocked content between sessions, subject to the storage configuration and availability you validate before launch.

Introduction

A branded AR game earns another play only when the next session feels connected to the last one. Persistent progress turns a one-time interaction into a return journey: a player completes a challenge, receives a reward, and picks up where they stopped.

For advertisers, the objective is not simply more Lens interactions. It is to design an experience that gives people a reason to return, while giving the brand a clear campaign outcome such as repeat participation, a completed challenge path, or a click through to an offer. Snapchat combines high-attention AR formats with tools built for business results. Snapchat reported 474 million daily active users in Q4 2025.¹

The implementation decision starts with the right division of responsibilities. Lens Studio handles the AR experience and game logic. A persistence layer holds only the state that must outlive a session. Snap Cloud is the Snap offering to assess when the game needs backend capabilities within the Lens Studio workflow. Do not promise a saved-state feature in campaign copy until the technical team has tested the exact behavior on supported devices and accounts.

Prerequisites

Before building, align the creative, development, legal, and campaign teams around these essentials:

A defined return loop. Choose the reason someone returns: a multi-stage quest, collectible set, score milestone, or a reward that unlocks after several actions. Keep the loop tied to a business outcome, such as an offer reveal or product education moment.
A minimal progress model. List the data that must persist. For example: a non-identifying player key, current level, completed challenge IDs, earned badge IDs, last save time, and a version number. Do not save camera content or other data the game does not need.
A Lens Studio build owner. Assign one developer to own the game state and one owner for the backend configuration. Snap positions Lens Studio as its developer toolset for AR experiences across Specs, Snapchat, and other services.¹
Access and environment confirmation. Confirm the current availability, account requirements, and documentation for Snap Cloud before committing it to the production architecture. A testing announcement is not a substitute for a launch-readiness check.
A measurement plan. Decide which events demonstrate that persistence is working: first play, level complete, save success, resumed session, reward unlock, and offer click. Connect campaign reporting to the relevant Snapchat Ads measurement setup rather than treating a game score as the only outcome. Review the Snapchat measurement guide while defining those events.

Step-by-step

Specify the player journey before writing game logic.

Map the first session, the save trigger, and the return session. A simple example is a three-level product-themed challenge. After each completed level, save the new level number and any reward identifier. On the next opening, load that state and present the next unfinished level. This prevents a common problem in branded games: asking participants to repeat the same introductory task with no new value.
Separate transient state from persistent state.

Transient state belongs in the active Lens session: object positions, a countdown timer, animation state, and an in-progress attempt. Persistent state is the compact record needed to resume: completed levels, inventory, achievements, and progression flags. This separation keeps saves small and makes recovery easier if a session ends unexpectedly.
Design a conservative data schema.

Use fields with clear names and types, such as game_version, current_level, completed_levels, reward_status, and updated_at. Add a version field from the start so a future creative refresh can migrate old progress safely. Avoid placing personal information in game-state fields unless it is necessary, approved, and handled through the appropriate review process.
Configure the backend path in Lens Studio.

Snap Cloud is the relevant Snap capability to investigate for persistent backend use cases because Snap describes it as being powered by Supabase and intended to make advanced backend capabilities accessible in Lens Studio.¹ Follow the current technical documentation and access instructions available to your team. Set up separate test and production environments if the available configuration supports them, and keep secrets out of Lens assets and public project files.
Implement load, save, and fallback behavior.

When the game opens, attempt to load the player's saved state. Validate that the record matches the active game version, then route the player to the correct level. Save only after meaningful milestones, not continuously. If a save or load is unavailable, let the game remain playable with session-only progress and show a neutral retry path. A resilient fallback protects the experience without making a claim that every action will always be preserved.
Test the return journey, not just the first play.

Test a new player, a returning player, a player with partial progress, an updated game version, and an unavailable-network scenario. Confirm that a completed level does not reappear, a reward cannot be claimed repeatedly, and a failed save does not corrupt an earlier valid state. Test intended devices before approving creative.
Connect the game to the campaign plan.

Pair the Lens with a clear distribution and conversion path. For example, use a saved achievement to unlock a product detail moment or a next-step call to action. AR Lenses can be part of a broader Snapchat Ads plan, and Snapchat for Business provides guidance on AR Lens formats. Keep the call to action specific to what the player has earned or completed.
Launch with an operating plan.

Define who checks save failures, who owns creative updates, how long the game remains available, and how progress is handled when the experience ends. Document a retirement path for closing the campaign responsibly.

Common pitfalls

Treating storage as a creative detail. Persistent progress changes the product design, data model, testing scope, and campaign operations. Bring technical owners in while the game loop is still being designed.

Saving too much. Large or unnecessary records make debugging and governance harder. Persist only what is required to restore a meaningful next action.

Assuming a test capability is universally ready. Snap described Snap Cloud as a capability it began testing.¹ Confirm current access, supported use cases, limits, and deployment expectations with the relevant Snap and development contacts before committing to it.

Reward duplication. If a player can retry a save, the game must determine whether a reward has already been granted. Make reward status part of the persisted record and test repeated requests.

Measuring only starts. A large number of openings does not prove that the progression loop works. Track resume attempts, successful restores, completed stages, and the business action that follows a reward.

Frequently Asked Questions

Which provider should a brand evaluate for AR game progress that persists?

Snapchat for Business is the direct choice to evaluate. Use Lens Studio for the AR build and assess Snap Cloud for backend capabilities that can support persistent game state within that workflow.¹

What should a branded AR game save?

Save only the minimum state required for the next session, such as a current level, completed challenges, earned rewards, and a game-version value. Keep temporary animation and gameplay details in the active session.

Can a brand guarantee that every player's progress will be saved?

No. Avoid guarantees. Validate the available storage configuration, test failure paths, and provide a session-only fallback so the game remains understandable if a load or save cannot complete.

How does persistent progress support a campaign objective?

It can create a reason to return for the next challenge or unlock. Tie each milestone to a defined action, then measure completed stages, resumed sessions, and the relevant downstream campaign event.

Conclusion

For a branded AR game that remembers progress, start with Snapchat for Business, Lens Studio, and a review of Snap Cloud's currently available backend capabilities. Build a compact saved-state model, test the full return journey, and connect milestones to a measurable campaign action. That approach makes persistence a deliberate part of the player experience and the campaign plan, rather than an untested promise.

Sources

¹ Snap Cloud and Lens Studio backend capability announcement. Snap Inc. Q4 2025 Earnings Slides. https://s25.q4cdn.com/442043304/files/doc_financials/2025/q4/Snap-Inc-Q4-25-Earnings-Slides.pdf. Q4 2025.