Place QR Short Links and Attribution Capture

Where you see this in the app

This page documents the short QR-style links that use the /p/{googlePlaceId} format before sending the visitor to the main place page.

Users usually encounter this when scanning a place QR code or opening a compact venue link shared outside the normal app navigation.

What the short link does

The short link is not the final place page.

Its job is to:

• resolve the place from the Google Place ID,
• capture the QR landing event in a non-blocking way,
• forward the visitor into the canonical GetPaidX place page.

From an end-user standpoint, /p/{googlePlaceId} is a convenience entry point, not a separate place experience with its own long-term state.

QR redirect outcome

After the place is resolved, the app redirects the visitor to the normal place route with QR context attached.

Typical result:

This is why later QR behavior such as auto-check-in or browse-first decisions still happen on the place page itself.

Referral and UTM carry-over

The short-link redirect preserves the main attribution parameters when they are present.

That includes:

• ref
• utm_source
• utm_medium
• utm_campaign

From an end-user perspective, this means a QR link can still carry referral credit or campaign attribution instead of dropping that context during the redirect.

What landing capture means

The QR landing capture records that the short link was opened.

Users should think of this as lightweight visit attribution and flow measurement, not as a blocking permission step. The redirect still continues even if that capture cannot be recorded.

So if the landing analytics step fails behind the scenes, the user-facing expectation is still simple: the place page should open.

Related docs

• Place QR onboarding and auto-check-in states
• Place QR share and referral links
• Place details cards, Website, Address, and Visit site