43.1 Public Asset Behavior Overview

AIUNIFY PROS separates the authenticated workspace from public campaign routes. Visitors do not need access to your workspace to use a published or active campaign asset.

Source-confirmed public route types are:

1. /r/{code} — QR Code resolver
2. /s/{code} — Short Link resolver
3. /u/{username} — Bio Page
4. /page/{slug} — Landing Page

43.2 Why Public Routes Matter

QR Codes and Short Links route through PROS before the visitor reaches the final destination. That intermediate PROS route enables supported capabilities such as analytics, password protection, scheduling/expiration checks, dynamic destination behavior, UTM parameters, and routing logic.

43.3 Public QR Code Flow

1. The visitor scans or opens the PROS QR route.
2. PROS finds the QR Code by code and confirms it is routable.
3. If the QR Code is password protected, the password screen is shown.
4. On permitted access, the scan count and last-scanned time are updated.
5. A qr_scan Analytics event is recorded.
6. PROS resolves the content according to the QR type.

43.4 QR Password Protection

When a QR Code has a stored password hash, the public resolver presents the QR password page until the correct password is supplied. An incorrect submitted password produces the protected-page response rather than exposing the destination.

43.5 QR Content Resolution

Different QR types can produce different public behavior:

1. Normal URL destinations redirect externally.
2. Application payloads can choose iOS, Android, or fallback destinations based on the visitor user agent.
3. vCard content can be returned as text/vcard.
4. Event/calendar content can be returned as text/calendar.
5. Text and WiFi payloads can be rendered through the PROS public QR-content page.
6. Multi-Link content is rendered as a public content experience.

43.6 Dynamic QR Advantage

Because the distributed QR image points to the PROS route, supported dynamic QR destinations can be updated while preserving the scan entry point. This is why the interface recommends using dynamic QR behavior when you may need to change a destination without reprinting.

43.7 Public Short Link Flow

1. The visitor opens the PROS Short Link.
2. PROS finds the Short Link and checks whether it is routable.
3. If password protection is enabled, the password screen is shown.
4. On permitted access, click count and last-clicked time are updated.
5. A short_link_click Analytics event is recorded.
6. Applicable redirect rules are evaluated.
7. Configured UTM parameters are appended.
8. The visitor is redirected to the resulting destination.

43.8 Short Link Password Protection

A password-protected Short Link displays a public password form. The destination is not returned through the normal redirect until the submitted password matches the stored hash.

43.9 Short Link Redirect Rules

The backend Short Link resolver supports country/device redirect rules. It checks each saved rule and can send a matching visitor to an alternate URL. If no rule matches, the standard destination is used.

Current UI: The current standard Short Link drawer does not visibly expose redirect-rule editing, so this is a backend-supported behavior rather than a normal subscriber configuration step in the present interface.

43.10 UTM Parameters

The resolver can append saved UTM values for utm_source, utm_medium, utm_campaign, utm_term, and utm_content. This allows distributed Short Links to carry campaign attribution parameters to the destination.

43.11 Public Bio Page

The public Bio route uses the saved username. Only an active Bio Page is intended to be served publicly. A valid public view records a bio_page_view Analytics event.

43.12 Public Landing Page

The public Landing Page route uses the saved slug. Only pages with status published are served as public Landing Pages. A public view records a landing_page_view Analytics event.

43.13 When a Public Asset Does Not Open

A public route can be unavailable when the asset is inactive, outside its scheduled access window, expired, unpublished, deleted, unavailable, or otherwise not routable under the current model rules.

43.14 Testing Public Assets

1. Save or publish the asset.
2. Copy the public URL.
3. Open it in a private/incognito browser window.
4. For QR Codes, scan the actual generated QR from a second device when possible.
5. Test password protection where enabled.
6. Test start/expiration behavior where appropriate.
7. Confirm the final destination or rendered content.
8. Review Analytics after the test event is recorded.

43.15 Do Not Bypass PROS When Tracking Is Needed

If you distribute the underlying destination URL instead of the PROS Short Link or PROS QR route, the visitor can bypass PROS redirect tracking. Use the generated PROS access point when you need the corresponding PROS analytics and management behavior.