> 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/end-customer-faqs/freeing-up-your-gmail-address-if-you-accidentally-created-a-duplicate-account.md).

# Freeing up your Gmail address if you accidentally created a duplicate account

Sometimes customers lose access to an old email address and register with Perkville using a new Gmail address. While this lets you log in, it creates a new account that isn’t connected to your original data at the business—so you won’t earn points or see your point history.

To fix this, you'll need to temporarily free up your Gmail address from the new account so it can be added to your original account. Follow the steps below:

***

#### Step 1: Add a modified version of your Gmail to the new account

Gmail ignores anything after a `+` in the first part of your email (before `@gmail.com`), but Perkville treats it as a different address. This allows you to use a variation of your Gmail to change the email on your new (incorrect) Perkville account.

For example:

* Your Gmail: `myemail@gmail.com`
* Temporary version: `myemail+1@gmail.com`

To update your account:

1. Log in to the new Perkville account (the one not showing your points).
2. Go to **Settings > Email Settings**.
3. Add `myemail+1@gmail.com` as a new email address using your actual Gmail, not <myemail+1@gmail.com>.
4. Check your Gmail inbox for a confirmation email and click the link to confirm.

***

#### Step 2: Make the modified Gmail your primary email

1. Return to **Settings > Email Settings**.
2. Click **Make Primary** next to the new email that you added similar to `myemail+1@gmail.com`.

***

#### Step 3: Remove your real Gmail address from the new account

1. Still in **Email Settings**, find your real Gmail address (e.g., `myemail@gmail.com`).
2. Click to delete it from the new duplicate account.

Now your real Gmail address is no longer tied to the incorrect Perkville account.

***

#### Step 4: Ask the Business to update your original account

Contact the business where you earn points and ask them to:

* [Add your Gmail address](broken://pages/4uaA26BxBhvS1ma93pQh) (`myemail@gmail.com`) to your original Perkville account—the one that has your point history.

Once they’ve done that, you can log in to Perkville with your Gmail address and access your correct account.

**Note:** In some cases, the business may not be able to add your Gmail address to your original account— if you're connected to more than one business that uses Perkville or if you're a staff member at a participating business.


---

# 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/end-customer-faqs/freeing-up-your-gmail-address-if-you-accidentally-created-a-duplicate-account.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.
