Configure Viewer Actions on a Proxi Map

Open the Map Style settings for your Proxi map.

Decide which viewer actions should be available at the map level.

Common options include:

Enable Map stats/info if you want viewers to see map performance details.

Use this option when transparency or engagement metrics are helpful.

Turn on Add a place / placeholder if you want users to contribute locations.

Use this for crowdsource workflows such as:

If you do not want user submissions, leave this feature turned off.

Turn on Share map if you want viewers to distribute the map to others.

Enable Plan a route when users may need to visit multiple locations.

If relevant, allow optimized routing so viewers can visit points in the best order.

Use routing for use cases such as:

Enable Send map to phone to let users move from desktop browsing to mobile use.

Turn on Map comments if you want viewers to discuss places on the map.

Use comments to encourage questions, local tips, or community feedback.

Enable Translation when your audience includes multiple languages.

Confirm that these features support your audience and moderation needs before publishing.

Open the Point Card action settings.

Decide which actions viewers can take on individual points.

Available point-level actions may include:

For each action, determine whether it should appear as a button or another display style.

Enable Get directions if users should navigate to a point.

Choose the default direction mode if your map requires a specific travel method.

Turn on Upvotes if you want users to rate or support locations.

Decide whether to show the upvote count so viewers can see popularity at a glance.

Enable Mark as Visited if users need to track places they have already been to.

Turn on the visited filter at the top if users should be able to sort or filter by visited status.

Use this feature for progress tracking, personal exploration, or gamified map experiences.

Enable Save point so viewers can bookmark locations for later.

Allow Share point if users should send individual locations to others.

Turn on Comment on point if you want discussion tied to specific locations rather than the whole map.

Review the full set of enabled actions to ensure they match your engagement goals.

Only enable actions that support your map’s purpose; too many options can confuse viewers.

If you allow comments, make sure you have a moderation plan in place.

Crowdsource and save/share features may expose user-generated content, so confirm privacy expectations before publishing.

Translation and routing features should be tested to ensure they work correctly for your audience and map structure.

If you change default direction modes or button styles, verify the viewer experience on both desktop and mobile.

Start with the most important actions first, then add secondary features after testing.

Use Map stats and upvote counts when you want quick engagement signals.

Use Add a place only when you need audience contributions; otherwise keep the map cleaner by leaving it off.

Group related actions together in your setup process: map-level actions first, then point-level actions.

Test the map as a viewer after each major change to confirm the actions display and behave as expected.