> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/redirect.md).
# Redirects
Redirects create a short, managed URL for an enrolment form. They add context, such as a store, seller, language, or campaign source, without duplicating the form.
This approach keeps distribution links consistent and makes performance measurable across locations and campaigns.
Real-world examples
* A retail Brand prints one QR code per store. Each code adds the correct `storeId`.
* A clienteling team uses a seller code to attribute enrolments to each associate.
* A campaign QR code sets `neo.src` to separate event scans from email traffic.
### Plan the redirect
Define the enrolment form and the context carried by the link before creating a redirect. A redirect should serve one clear distribution use case.
For each redirect, confirm these details:
* **Destination:** the enrolment form layout that opens.
* **Label:** a clear operational name, such as `Paris-Rivoli-summer-2026`.
* **Parameters:** the context added when the link is opened.
Use `storeId` when the journey must identify a store. The value must match the identifier in [Stores](/guides-enrolment/enrolment/enrolment-form/stores.md).
Common supporting parameters are:
* `associateId` for seller attribution.
* `neo.lg` for the display language.
* `neo.src` for the distribution source.
### Create a redirect
Create redirects manually when the distribution context is unique or requires review before publishing.
{% stepper %}
{% step %}
#### Open Redirects
In the administration console, open **Forms → Redirects**. Select **Add New**.
Open the Redirects section from the Forms menu.
{% endstep %}
{% step %}
#### Select the destination
In **Layout**, select the enrolment form layout that should open. In **Label**, enter a name that identifies the location or campaign.
{% endstep %}
{% step %}
#### Add the context
Select **Add Parameter** and add the required key and value. For store routing, use `storeId` and the matching store-data identifier.
Add `associatId`, `neo.lg`, or `neo.src` only when the journey needs seller attribution, a language override, or source tracking.
{% endstep %}
{% step %}
#### Save and verify
Save the redirect. Open its generated link once and confirm that the expected form and context load.
{% endstep %}
{% endstepper %}
### Import redirects in bulk
Bulk import supports large store networks and repeated campaign patterns. It reduces manual work and keeps redirect naming consistent.
Prepare an Excel file with these columns:
* `Layout`
* `Label`
* `StoreId`
Return to **Forms → Redirects** and import the file. Review a sample of imported redirects before distributing their QR codes.
### Validate and distribute
Validation prevents incorrect store attribution and broken enrolment journeys. Test each redirect with a known form configuration before printing or publishing it.
#### Preview the QR code
Select the three-dot menu beside a redirect, then select **View**. Confirm that the preview includes the correct parameters and opens the intended form.
#### Download QR codes
Select **Download** to export QR codes as a ZIP file. The export contains `.png` and `.svg` versions for digital and print use.
#### Monitor redirect activity
Select **View statistics** from the three-dot menu. Choose a date range to review scan volume, compare stores, and assess campaign performance.
#### Delete a redirect
Delete a redirect when its enrolment journey, store, or campaign is no longer active, for example when a physical store closes.
{% stepper %}
{% step %}
**Open Redirects**
In the administration console, open **Forms → Redirects**.
{% endstep %}
{% step %}
**Delete the redirect**
Select the three-dot menu beside the redirect, then select **Delete**. Confirm the deletion.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Deleting a redirect invalidates its generated QR code and link. Update or remove any printed or distributed QR codes pointing to a deleted redirect to avoid broken enrolment journeys.
{% endhint %}
### FAQ
When should a redirect be used?
Use a redirect when an enrolment form needs distribution-specific context. Store QR codes, seller links, language-specific links, and tracked campaign links are common uses.
Can several redirects use the same enrolment form?
Yes. Each redirect can open the same form while adding different parameters. This supports one shared form across several stores or campaigns.
How should store QR codes be validated?
Scan a sample of generated QR codes before printing. Confirm that each link opens the correct form and carries the expected `storeId`.
Which QR-code format should be used?
Use `.svg` for print materials because it scales without quality loss. Use `.png` for digital channels that require a raster image.
Can a redirect be disabled temporarily?
No. Redirects cannot be disabled. Delete the redirect when it is no longer needed, then update or remove any QR codes and links that point to it.
Can a deleted redirect ID be reused?
No. Redirect IDs are generated automatically and cannot be selected. Once deleted, a redirect ID cannot be reused.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/redirect.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.