A Simple Fix to Improve Navigation in Event Maps (Web App Only)

The current Map Manager now supports a wider range of hotspot types, including Topic, Rewards, Challenge, URL, and more. This gives flexibility in how you design the experience.

If you are using the URL hotspot type to direct users to a page, for example a Challenge page, the back navigation will typically return users to the Topic that hosts the challenge.

If your intention is for users to return directly to the Event Map within the project, this is where a simple technique becomes useful.

The Core Idea

When setting up your hotspot URL, append either:

• ?back=true
• #back

This enables the back arrow in the web app to rely on browser history instead of a fixed route.

How It Works

The logic is straightforward.

1. User starts from the Event Map
2. User taps on a hotspot using a URL
3. User is redirected to another page, such as a Challenge
4. The navigation is recorded in the browser history
5. When the user taps the back arrow, they return to the previous page, which is the Event Map

Implementation Example

Instead of: https://yourproject.com/challenge-page

Use: https://yourproject.com/challenge-page?back=true

Important Note

This applies to web app environments only.

The behaviour depends on browser history. Native mobile apps or embedded environments may not behave the same way.

When to Use This

Use this approach when:

• The Event Map is your main navigation hub
• You want users to return directly to the map after viewing a page
• You are linking out using URL hotspots

Avoid this when:

• You want users to return to the Topic structure instead
• Users may land directly on the page from external sources