Do You Need Your Main Email for the 2026 Call of Duty: Mobile Test Server?

The fastest answer: for the current Call of Duty: Mobile Public Test Build, choose Guest when creating the test identity; you do not need to enter your main game account email just to follow the announced test flow. That guidance applies to this build only. Check the latest official notice if the app asks for a different sign-in or verification step.

This guide is for players preparing to install the 2026 Public Test Build and keep test activity separate from their live game identity.
It also helps players choosing between a main email, a temporary inbox, and Guest access.
If test-data deletion or account recovery is the concern, the key distinction is whether the account has anything worth keeping.

Last updated October 25, 2026. The current test details were checked against the Public Test Build announcement and Activision’s account profile guidance.

Before installation: confirm this is the test build

A Public Test Build is a separate testing context from the regular game. Its entry instructions, eligibility, and test data should not be assumed to match the live version. Treat the test announcement as the source for the current build rather than relying on an old installation guide, a community comment, or a remembered sign-in process.

The current announcement lists Android and iOS as supported platforms. That is a two-platform scope for the build described there, not a guarantee that every future test will open on both. The same notice describes the closing date as the most likely expected date. “Most likely” matters: it is an estimate, not a confirmed promise that access will end at a precise time. Check the announcement again before downloading or planning around a particular test window.

Before installing, verify three things on the official notice:

• Whether the build is still open for participation.
• Which platform instructions apply to the device being used.
• Whether the sign-in instructions have changed since the announcement.

Do not use a test-build link from an unofficial post simply because it looks familiar. A test entrance, a qualification requirement, and a live-game login are separate things. Confirm the current official route first, then follow only the steps listed for that build.

This distinction also prevents a common mistake: seeing the regular game account prompt and assuming the test requires the same credentials. The available announcement instead tells players creating an account for this test to choose Guest. That is the basis for the recommendation here; it does not establish a universal login rule for other builds.

At first launch: create a test identity with Guest

When the current test flow asks for an account during initial setup, select Guest as directed in the announcement. Do not enter the email attached to the live Call of Duty: Mobile account just because the test is a Call of Duty: Mobile product. The instruction is specific to the current announcement and its described process.

Guest access is a way to keep the first test-session decision separate from the permanent account. It is not a promise that the test identity will be anonymous, recoverable, or transferable. It also does not confirm that every feature will be available without additional steps. If the app presents a new email field, account-linking prompt, or verification requirement that is not covered by the notice, stop and check the newest official instructions before submitting long-term credentials.

For the current flow, the practical sequence is:

• Open the official announcement and make sure it still describes the active build.
• Install only through the platform entrance specified there.
• At account creation, select Guest as instructed.
• If the screen differs from the announcement, pause rather than guessing which account to use.
• Do not connect a live account unless a current official instruction clearly requires it and the consequences are understood.

The current announcement is the authority for this build’s Guest instruction. A past test, a separate regional release, or another game’s process is not a substitute. This is especially important if the player has not used a test build before: the safest choice is to follow the live directions on the official notice, not to reuse credentials based on habit.

During testing: keep privacy separate from recovery

An independent test identity can reduce confusion between test actions and activity on a live account. It may also help keep an interest-specific identity distinct from the email used for everyday gaming. But email separation alone does not make a player anonymous. Display names, linked social accounts, device activity, and information shared in a community can still connect activity.

The Call of Duty: Mobile test server email decision is therefore not simply “main address or temporary address.” First ask whether the current workflow requires an email at all. If Guest is the stated route and the player only needs to participate in the test, adding a main-account email can be unnecessary. If an official step later requires an address, assess what that address will be used for and whether it must remain reachable.

A temporary inbox and a long-term recovery email serve different jobs:

• Guest identity: Best aligned with the current announcement’s instruction for creating a test account. It avoids entering the main game account email at that initial step, but it does not create a recovery guarantee.
• Temporary inbox: Can separate a short-lived registration from a personal inbox when a signup genuinely requires an email. It is a poor choice for an account that needs future recovery or lasting access.
• Long-term email: Appropriate for a live account that holds progress, purchases, or other durable value, because the owner can continue receiving recovery messages. It may reveal more of the player’s usual email identity to that service, so use it where ongoing account control is the priority.

These are editorial fit ratings for the use cases, not official Activision ratings: Guest is the strongest fit for the current test setup; a temporary inbox is a conditional fit only for a disposable test signup that explicitly needs an address; a long-term address is the strongest fit for a permanent account requiring recovery. None of those choices creates a guarantee about test eligibility, successful delivery, or data migration.

If a new screen asks to verify or link an address, do not assume that the test process has silently changed in a harmless way. Check the current notice and the service’s official account guidance. Activision explains account-profile management in its official profile guide. If a permanent account later becomes inaccessible, use the official account recovery process, not an address that was chosen only for a short test session.

For an account that will remain in use, keep its recovery route durable. Activision’s account recovery guidance is the relevant reference for regaining access, while its two-factor authentication instructions cover an additional account-protection option. A temporary address does not replace either a valid recovery path or careful handling of sign-in requests.

A message claiming that the test requires the live account password should not be treated as proof of a new rule. Verify any changed login requirement against the current official announcement before entering credentials.

Before submitting an email: use this player checklist

Use this checklist at the exact point an email field appears. It separates the short-term test need from the long-term recovery needs that are easy to overlook during setup.

• [ ] Does the current official instruction explicitly require an email at this step? If not, follow the Guest route stated for the current build rather than adding the live account email out of habit.
• [ ] Is the address needed only for a short-lived test registration, or must it receive future notices and recovery messages? Choose based on the expected job, not on the general idea of “keeping accounts separate.”
• [ ] Does the account hold live-game progress, purchases, or another asset the player expects to keep? If yes, use a long-term address that remains accessible for recovery.
• [ ] Does the test instruction promise that Guest progress can be migrated or restored? The current announcement does not provide that promise; do not infer one from a successful test session.
• [ ] Has the app introduced a sign-in, verification, or linking step not described in the current notice? Pause and check the official page before providing permanent credentials.
• [ ] Is a temporary inbox being considered only to avoid marketing mail? If so, first confirm that an email is required and that no future account recovery depends on it.

The checklist produces a simple rule. For the test flow described in the current notice, use Guest. For a permanent game account, use an email that can still be accessed when recovery is needed. A temporary inbox can be a fit for a short registration that has no long-term account value, but it should not become the only recovery address for a live account.

Players comparing longer-term options can use this guide to choosing an email address for different account relationships. For a permanent account specifically, the guide to safer signup email choices helps distinguish privacy separation from keeping a usable recovery route.

At the end of testing: assume the test identity will not last

The current announcement says that player data collected during the test will be deleted. It does not promise that test progress will transfer to the live game, that a Guest identity will remain recoverable, or that test access will continue after the stated window. Treat the test as temporary unless a later official notice clearly says otherwise.

That matters most when a test session starts to feel like a normal game account. A player may spend time exploring, unlocking test content, or changing settings, but those actions should not be mistaken for permanent progress. Do not attach a live account or switch to a long-term email solely because the test identity has become familiar. First confirm whether the current official process says that linking is supported and what it does.

For the regular game, recovery matters more than short-term separation. An account with retained progress or purchases should have an address the owner can access later. The Activision email verification information is relevant when managing an account email, while the recovery guide should be consulted if access is already lost. Keep test participation and live-account recovery as separate decisions.

This approach avoids two opposite errors. The first is submitting the main email to a test that currently directs players to Guest. The second is using an ephemeral address for a permanent account and then discovering that the address cannot support future recovery. The right choice depends on what the account is expected to preserve, not on a blanket preference for either privacy or convenience.

Frequently asked questions

Does the Call of Duty: Mobile test server require the main account?

According to the current Public Test Build announcement, select Guest when creating an account for the test. That means you do not need to submit the email for your live game account just to follow this test flow. Check the latest official notice before launching, though: later builds can change their entry or verification steps.

Can you enter the Call of Duty: Mobile Public Test Build as a Guest?

The current announcement says to choose Guest when you create an account for the test. Treat that as guidance for this specific Public Test Build, not a promise that every future test or platform will use the same process. If the app shows a different sign-in or verification requirement, pause and compare it with the latest official instructions before entering long-term account credentials.

Do test-server progress and live-game data carry over?

Do not count on test progress, a Guest identity, purchases, or recovery access carrying into the live game. The current announcement says player data collected during testing will be deleted. It does not promise that test progress will migrate or that a Guest identity can be recovered as a permanent account, so keep long-term assets on an account with an accessible recovery address.

Should you use a temporary or long-term email for a game test?

First check whether the official test flow actually asks for an email. If it directs you to Guest and you only need to participate, avoid adding your main game account email unnecessarily. A temporary inbox can suit a short-lived signup that does not need future recovery, but a live account with progress, purchases, or ongoing access needs a long-term email you can keep using.

For this build, the low-risk move is to follow the current Guest instruction and keep the live account’s recovery address out of the test flow unless an updated official step requires it. If a separate short-term signup does require an email, Forwardtmp can provide an immediately usable temporary inbox without registration, keeping the main address out of a one-off registration and away from its follow-up mail. For any live account with progress, purchases, or recovery needs, keep a long-term address instead.

Frequently asked questions