myne Support

Pre-filling form fields from rich links

Published

Joshua

Pre-filling lets you pass customer details through a link so they don't have to type them in manually. This is useful for personalised campaigns, receipt follow-ups, and reducing friction in your signup flow.

Connection pages, standalone forms, and website embeds all support pre-filling via query string parameters on the URL.

How pre-filling works

When a customer clicks your link, myne reads the query parameters (?param=value) and automatically fills matching fields on the form. Fields that are already filled—or that come from a stronger identity source (like a recognition link)—won't be overwritten.

Identity priority on hosted forms: URL parameters → browser cache → signed-in user.

Building your base URL

Connection page:

https://app.myne.network/connect/{locationUuid}?pid={connectionPageId}

Standalone form:

https://app.myne.network/connect/{locationUuid}?form={formId}

Website embed: Add parameters to your host page URL (same pattern applies).

Copy your page link from Connection Flows in myne, or build it manually if you know the location UUID and page/form ID.

Adding customer fields

Append each field with & and the query parameter name. URL-encode special characters:

  • Spaces → %20

  • @ symbol → %40

  • + symbol → %2B

Example with name and email:

https://app.myne.network/connect/{locationUuid}?pid=42&first_name=Sam&email=sam%40example.com

Example with phone (URL-encoded):

https://app.myne.network/connect/{locationUuid}?pid=42&first_name=Sam&phone=%2B61412345678

Supported standard customer fields

Query parameter

Prefills

first_name

First name

last_name

Last name

email

Email address

phone

Phone number (URL-encode the + prefix)

postal_code

Postcode

birth_date

Date of birth

marketing_opt_in

Marketing opt-in — use true, 1, or yes

guid

Receipt or transaction code (order ID)

ig_key

Instagram connection key

Custom and catalogue fields

Custom fields on your form: Use the field's storage key (same name as in Brand → Forms) as the query parameter. Find the storage key in your form settings.

Example: if your form has a custom field called "favourite_venue" with storage key favourite_venue:

?favourite_venue=123

Select and catalogue fields (business, location, product, etc.):

  • By ID (preferred): ?referred_by=72365

  • By name: ?referred_by=Acme%20Cafe (space encoded as %20)

  • Multi-select (comma-separated): ?tags=12,34,56

Building and sharing links step-by-step

  1. Start with your connection page link: …/connect/{locationUuid}?pid=42

  2. Add only fields that appear on your form (don't add fields that don't exist).

  3. URL-encode special characters (spaces, @, +, etc.).

  4. Share via email, SMS, QR code, or paste into campaigns.

  5. Optional: Use Liquid to personalise at scale — see example below.

Using Liquid for bulk personalisation

In automations, email templates, or integrations, you can use Liquid placeholders to personalise links dynamically:

{{ connection_page_url }}&email={{ customer.email }}&first_name={{ customer.first_name }}&phone={{ customer.phone }}

This way, each link sent to a customer includes their own details without manual work.

Quick examples

Name and email only:

https://app.myne.network/connect/{locationUuid}?pid=42&first_name=Sam&email=sam%40example.com

Full profile with marketing opt-in:

https://app.myne.network/connect/{locationUuid}?pid=42&first_name=Sam&last_name=Lee&email=sam%40example.com&phone=%2B61412345678&postal_code=2000&marketing_opt_in=true

Receipt or docket follow-up:

https://app.myne.network/connect/{locationUuid}?pid=42&guid=ORDER-12345&email=sam%40example.com

With a referred-by field (by ID):

https://app.myne.network/connect/{locationUuid}?pid=42&first_name=Sam&email=sam%40example.com&referred_by=72365

Important behaviour to know

Prefill doesn't overwrite identity

If a customer has already typed something into a field, pre-fill won't replace it. This protects customer data and respects manual corrections.

Bad select IDs or names don't block signup

If you use a select field parameter with an ID or name that doesn't exist, the field will stay empty but the form will still submit. The unknown parameter is logged on the Submission activity for debugging.

Unknown parameters are recorded

Parameters that don't match any form field are ignored for prefill but are still recorded in submission query_params. This is useful for tracking UTM codes, campaign tags, or custom metadata without cluttering the form:

?pid=42&utm_source=email&utm_campaign=spring_promo&first_name=Sam

The UTM codes will be recorded even though they don't fill form fields.

Lock prefilled fields (optional)

If you want a prefilled value to be submitted but hidden from the customer (useful for partner attribution), enable Lock on that form field in myne. The customer won't see or edit it, but it will be submitted with the form.

Common use cases

  • Email campaigns: Personalise signup links with customer name and email so they only confirm opt-in.

  • Receipt follow-ups: Include the order code (?guid=) so customers can immediately see their purchase history.

  • QR codes: Encode a pre-filled link in a QR code for in-venue or printed materials.

  • SMS invites: Send a short URL with name and phone pre-filled to reduce typing.

  • Partner integrations: Prefill a referrer ID or business link so credit is assigned correctly.

  • Marketplace or affiliate links: Pass a campaign tag to track where signups came from.