> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/advanced/allowed-registration-urls.md). # Allowed registration URLs The purpose of this feature is to provide mobile apps with a means to allow unregistered customers to complete their Perkville registration within their mobile app. This ensures that the Perkville cookie resides in the mobile app, allowing the customer to avoid logging in again after registering. Without this capability, customers will likely be directed to their default browser to complete their registration, necessitating a subsequent login within the mobile app to access Perkville. The mobile app may feature a link for the business's loyalty program, enabling customers to view their points, redeem rewards, and register for the program if they haven't already done so. When a customer enters their email ([or if the email is pre-populated by the app](/faqs/miscellaneous/is-it-possible-to-pre-populate-the-email-address-field-on-the-page-for-joining-the-loyalty-program.md)) on the program's registration page, Perkville sends an email prompting them to complete their registration. The "Allowed registration URLs" feature supports the business in including a "register\_at" parameter in the original link to Perkville (within its mobile app) to direct customers back to the mobile app to complete registration, ensuring the Perkville cookie is tied to the app. #### How It Works To facilitate in-app registration, businesses can add an optional "register\_at" query parameter to the loyalty program URL within their app. This allows customers to register for Perkville directly within the application. ```perl https://mybiz.perkville.com/?register_at=myapp%3A%2F%2F ``` When the customer accesses this URL while logged out and begins the registration process, they will receive an email containing a link similar to this: ```perl myapp://?registration_url=https%3A%2F%2Fmybiz.perkville.com%2Fregister%2F123registrationcode%2F%253Fnext%253Dhttps%253A%252F%252Fmybiz.perkville.com%252F ``` When the customer clicks the link provided in the Perkville registration email, your application must decode the "registration\_url" query parameter and open the registration URL within your in-app browser. This allows the customer to complete the registration process in your mobile app. #### Important Considerations * The "register\_at" parameter must be added to your business's list of Allowed registration URLs in the Advanced Settings of Perkville. If the URL is not authorized, the customer will be directed to a standard registration URL. * The registration URL must be either your business's custom domain or a subdomain of Perkville (e.g., `https://rewards.client-custom-domain.com/` or `https://client.perkville.com/`). --- # 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.perkville.com/features/settings/advanced/allowed-registration-urls.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.