> 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/faqs/miscellaneous/is-it-possible-to-pre-populate-the-email-address-field-on-the-page-for-joining-the-loyalty-program.md).

# Is it possible to pre-populate the email address field on the page for joining the loyalty program?

Yes, it is possible to pre-populate the email address field on the page for joining the loyalty program using a specific URL format. By constructing a link in the following format:

```
https://oovana.perkville.com/login/?email=jon@gmail.com#join
```

Replace "oovana.perkville.com" with the URL for your actual loyalty program and "<jon@gmail.com>" with the customer's email address. When a customer clicks on this link, they will be directed to the page to join your program with their email pre-populated into the email address field.

**Benefits:**

Pre-populating the email address field reduces the number of steps for customers to join your loyalty program. This streamlined process can improve the conversion rate for joining your program. You can use this feature if you're able to dynamically insert customers' email addresses into the link, such as in a mobile app or in a mass email to your customers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/faqs/miscellaneous/is-it-possible-to-pre-populate-the-email-address-field-on-the-page-for-joining-the-loyalty-program.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
