Skip to main content
Gmail and Google Workspace mailboxes are kept out of warm-up. The reason the product gives, on every warm-up screen, is Google’s Terms of Service. One screen enforces it by leaving those mailboxes out of the picker; everywhere else the rule is carried by a notice rather than by a block.
Where
Email Accountsrow menuWarm up
Your role needs
Read access to Warm-up read-warm-ups. Admin, Member and Viewer have it by default.
To create
create-warm-ups on top of the permission above.
Warm-up has no sidebar entry. You reach it from an email account’s row menu, from the bulk warm-up action, or by URL. If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.

How it behaves

The notice is on the warm-up screens before you touch anything

Open the page that creates a warm-up and this sits above the form, on load, whatever mailbox you later pick:
Gmail/Google Workspace Notice Due to Google’s Terms of Service, Gmail and Google Workspace accounts are not available for warm-up campaigns. You must use a different email provider for warm-up.
Learn More (1) opens this article in a new tab. The same notice sits at the top of the warm-up list (everywhere except its empty state) and at the top of the smaller Create Warm-up panel you get when you start a warm-up from one email account’s row. In that panel it appears for any mailbox, not only a Google one. The only mailboxes that skip it are the ones on PipeLime managed infrastructure, which are warmed for you as part of being provisioned.

Only the create page actually leaves Google mailboxes out

On the create page, the Sender list only offers mailboxes that can warm up. A Gmail or Google Workspace mailbox is not greyed out or disabled there. It is not in the list, so there is nothing to select. That filter runs on that one picker and nowhere else. The Bulk warm-up flow narrows its list by whether a mailbox already has a warm-up, not by who runs the mailbox. The per-account panel opens on a mailbox you have already chosen from the Email Accounts table, so it has nothing to filter. And the request that creates a warm-up checks your permission and your figures, not the mailbox’s provider.
Outside the create page’s Sender list, nothing stops you starting a warm-up on a Google mailbox. The notice is the whole guard. The policy it states is the reason not to.

The check reads the server address, not the email address

A mailbox counts as Google when its outgoing server address contains gmail, which is what the Gmail preset fills in when you connect a Google account. A mailbox that Google delivers for, but that you connected under some other server address, is not recognised and is not filtered out.

Learn More changes on a partner-branded workspace

On a partner-branded workspace the button never opens a PipeLime page. It opens the partner’s own help center instead, and when the partner has not configured one (or has configured a PipeLime link), the button does not appear at all.

A Google mailbox still sends, and Smart Daily Limit reads No Warmup

None of this stops a Gmail or Google Workspace mailbox from sending campaign email. A new one goes through the same quarantine as any mailbox, counted from the day it was connected, and quarantine is settled before anything looks at the mailbox’s warm-up link, so a brand-new account reads In Quarantine first, and only afterwards reaches the warm-up question. Once past quarantine, a mailbox with no warm-up account behind it gives Smart Daily Limit nothing to read. The panel shows No Warmup, no calculated number is produced, and the daily limit stays whatever you set by hand.

Limits

Email warm-up

What the deliverability percentages measure, and how to start or resume a warm-up.

Smart Daily Limit

How your daily sending number is calculated, and every state the panel can show.

Connect a Gmail or Google Workspace account

Send from a Google mailbox using an app password instead.

PipeLime managed infrastructure

Mailboxes that arrive already warmed, so the policy above does not apply to them.