How to Set Up and Manage Data in Proxi

Log in to Proxi and start from the dashboard, which serves as the central hub for all activity.

Understand the core structure of the platform:

Use the built-in data/help bubble near the word data if you need a refresher on how these parts connect.

Go to Listings to add every business, restaurant, trail, vendor, venue, or organization you want to manage.

Add data using one of these methods:

Treat Listings as the single source of truth so updates can flow to all connected experiences.

Use Bulk Edit to update multiple listings in spreadsheet view.

Click Fields to add, reorder, or modify listing fields.

Include the data your team needs, such as:

Open an individual listing to:

Go to Collections and create a new collection for a specific theme or use case.

Group listings by purpose, such as:

Add listings to the collection by selecting Add Listing.

Choose existing listings from your master database, or create a new listing if needed.

Use Bulk Edit and Fields in Collections to manage collection-specific data efficiently.

Add or edit collection fields to capture the information needed for that grouping.

Common collection fields may include:

Turn on the Submissions form if you want the public or partners to contribute listings.

Design the form to replace tools like Google Forms or Typeform.

Add logic, page breaks, and section headings as needed.

Click Share to publish the form and distribute it using a link or embed code.

Decide whether submissions require approval before they appear in the collection.

Go to the asset area and click Create New Map.

Name the map clearly.

Select Use Places I Already Have and choose the collection that should power the map.

If you need to add places later, add them directly in the experience; updates will flow back to the collection and then to Listings.

Work through the map settings top to bottom on the left-hand side to configure the experience.

Test settings as you go to confirm the map behaves as expected.

Create a Directory when you need a list or grid view of places from a collection.

Embed a map and directory together on the same page if needed.

Create a Calendar for community events and configure:

Create a Bulletin Board for kiosk-style or TV slideshow content.

Allow businesses to submit slides such as events or advertisements.

Share bulletin boards using an embed or link.

Create a Guide to provide a curated list of places that functions like a mobile app.

Allow users to:

Create a Passport for gamified check-in experiences.

Create a Scavenger Hunt for clue-based check-ins.

Create a Best Of voting experience.

Use the Revenue section to create sponsorship opportunities.

Define what sponsors receive and set payment cadence options such as:

Charge for participation where appropriate, such as:

Note that ticketing is planned for future release, so check current platform capabilities before promising that feature.

Use Insights to review reporting for individual experiences and overall platform activity.

Request specific data exports or custom reporting if needed.

Use the help button in the bottom-right corner to contact support during business hours.

Email [email protected] for additional assistance. Reach out for best-practice guidance, troubleshooting, or help designing your setup.

Do not treat collections as separate master databases; Listings should remain the source of data.

Check whether submissions require approval before enabling public contribution to a collection.

Test settings carefully in each experience, since many options are available and some may be hidden deeper in the interface.

Confirm current feature availability before planning around future releases such as ticketing.

Ensure sponsor and public-facing information is accurate before inviting organizations to manage their own pages.

Use bulk import and bulk edit whenever possible to reduce manual entry.

Encourage businesses and vendors to claim and maintain their own listings to keep data current.

Reuse one collection across multiple experiences to avoid duplicate data entry.

Build and maintain forms directly in Proxi instead of using separate tools when possible.

Work top to bottom through settings in each experience/map to avoid missing configuration options.

Use the same collection to power a map, directory, and other assets so updates automatically sync everywhere.