Three different links from a single map: Visitor, exhibitor, and security

When you share a single public map link, everyone receives the same content. For visitors, stands and wayfinding are sufficient; for exhibitors, loading docks and warehouse layers are needed; for the security team, emergency exits and assembly points. Opening all of them on the same map either creates information clutter or exposes sensitive layers to everyone.

Multiple public publications solve this problem by generating multiple target audience links from a single map source. The source remains single; filters change per link. When an update occurs, three PDFs are not redistributed; each link stays current with its own view.

How it works?

The organizer publishes multiple anonymous links from the same exhibition map. Different layers, POI types, and shape types are selected for each link. Grid (hall plan) or geo (campus map) mode can be determined per publication. The visitor link remains simple; the logistics link opens technical layers; the SOS link is security-focused.

Example scenarios

• General visitor: Stands, wayfinding, restrooms, food — focused on commercial exploration.
• Exhibitor logistics: Loading docks, warehouse, technical service, electricity — focused on setup and dismantling.
• Security / emergency: Emergency exits, assembly points, first aid — SOS-focused.

These three links are fed from the same drawing. When a stand location changes, three separate files are not updated; the source map is updated, and filters are preserved. Operational gain starts here.

Why send separate PDFs instead?

Preparing three separate PDFs means redistributing three files when an update arrives. The risk of "the wrong plan went out" becomes an operational nightmare on the fair day. Old PDFs circulating on WhatsApp seem more credible than a live map; because people trust the file they downloaded. In multi-publication, the source is single; updates reflect on all links — each link with its own filters.

PDFs still have their place: official archives, contract appendices, certain corporate approval processes. But for on-site guidance, a live link produces fewer errors than a static file. Trade-off: PDF works offline; a live link requires connection. If the connection is weak at the exhibition venue, an offline backup plan should also be considered for critical teams.

Anonymous access and embed

Public links do not require login. A full-screen map opens; you can embed it on your fair website with the embed parameter. It can be directly added to campaign emails, SMS, or press releases. Asking visitors to create an account reduces map usage; anonymous access removes this friction.

Sharing on the organizer's domain keeps links consistent with your brand. Confusion about redirecting to the visitor portal address is reduced. Caution with embeds: It must be clear which publication profile is embedded. Accidentally placing a logistics link on the general site exposes technical layers to everyone.

Master publication remains separate

The in-portal visitor map and full snapshot publication work unchanged. Public links are additional channels; they do not replace the main operational map. This distinction is important: While the operations team uses the full-layered view, filtered views go out to the public. Opening everything to everyone with a single link is weak in terms of both UX and security.

Failed scenario: Every layer is open in a single public link, exhibitor logistics information is visible to visitors, the security team searches for their needs on a cluttered map. Multi-publication cuts this confusion at the design stage.

Practical rules for publication management

1. Name the links: Use clear names like "visitor", "logistics", "sos".
2. Assign ownership: Assign a role responsible for each link's current filter.
3. Pre-publication test: Open each link on a different device and verify the visible layers.
4. Distribution list: Specify in the brief which team will use which link.
5. Deactivate old links: Links from the previous season or with incorrect filters should not remain in circulation.

Without distribution discipline, multiple publications create more confusion than a single link. The tool won't solve issues without ownership.

Measurable metrics

• Open count per link: Which audience used the map
• Embed traffic: Website usage
• Incorrect link complaint: Logistics/SOS link going to the wrong channel
• PDF redistribution count: Whether the live stream reduced the need for PDFs
• Update propagation time: Propagation of source changes to all links

The SOS link not being opened at all should not be considered 'success'; it must be verified at least once during drills and briefings. An unused safety tool cannot be found in a crisis.

Distribution to campaign and press channels

The visitor link should not remain only in the portal menu. The registration confirmation email, the fair morning SMS, the press kit, and the website hero area can carry the same public URL. Distribution diversity reduces reliance on a single channel. The point to note is that the same version goes to every channel: If an old short link or last season's QR code remains in circulation, traffic will flow to the wrong map.

When the logistics link is embedded in an email attachment, access should be kept restricted. If it is accidentally shared in a general newsletter, loading dock and warehouse information will be opened to everyone. Therefore, the distinction between 'public' and 'restricted public' links should be clearly stated in the brief. Anonymous access does not mean every link is suitable for everyone; the filter determines the content, the distribution channel determines the risk.

With QEMENT white-label embed, keeping the visitor link on the corporate website while keeping SOS and logistics links on separate pages or QR sets is a common and clean setup. The single source remains; surfaces are separated.

After the fair ends, public links should also be planned for closure or archiving. An open logistics link can circulate the wrong plan for the next season. Adding 'deactivate public publications' to the season closing checklist is a small but effective discipline. Live source power turns into a risk in forgotten links.

Frequently asked questions

How many public links are enough?

In most fairs, three links (visitor, logistics, security) are sufficient. More links increase ownership and testing burden.

Does a public link require login?

No. Anonymous access is part of the design. Sensitive operational data should already be excluded with a filter.

Why does the portal map remain separate?

The in-portal experience is integrated with session, favorites, and event streams. A public link is an external channel and for quick sharing.

Does a filter on one link break another?

It should not. Filters are specific to the publication profile. The source geometry is common; visible content is separate.

Single source, zero unnecessary copies

You've drawn a map — three links to three different worlds. Visitors search for booths, exhibitors view logistics, the security team focuses on the SOS layer. Single source, controlled filter, reduced PDF copies. This model is a cleaner publishing structure for both UX and operational security.

Explore QEMENT Interactive Map's multi-publishing features or to clarify your target audience link architecture contact us.

Public link content depends on filter configuration; incorrect filter distribution creates operational risk.