> ## Documentation Index
> Fetch the complete documentation index at: https://docs.politicalcomms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Gmail Verified Sender Program

> What Google's Verified Sender Program does, who is eligible, what we check before you submit, and the Campaign Verify steps.

## What it is

Google's Verified Sender Program gives a 527 committee reliable delivery to
personal Gmail inboxes once its sending domain is verified through Campaign
Verify and its 14-day spam rate stays under 0.3%. That is Google's own
framing: consistent inbox placement at Gmail, not a visible badge on the mail
itself. Being in the program is never required to send. It improves Gmail
delivery for registered committees, and it does not change anything else
about your sending.

## Who is eligible

Your committee needs a **Verified** Campaign Verify identity request, an
active sending domain, and a sender identity on that domain. The program
works at the root domain, so every subdomain of a verified root benefits,
which is why one identity being verified can cover its siblings on the same
domain.

## What we check before you submit

Submitting burns one of Campaign Verify's three attempts on the request, so
the platform runs nine checks first and only shows the submit action once the
blocking ones pass.

| Check                    | What it confirms                                                                          | Blocking |
| ------------------------ | ----------------------------------------------------------------------------------------- | -------- |
| Campaign Verify verified | Your CV identity request is in **Verified** status                                        | Yes      |
| Domain active            | The sending domain is active on the platform                                              | Yes      |
| Authentication           | SPF and DKIM are signed by the sending domain                                             | Yes      |
| Postmaster verified      | The root domain is verified in Google Postmaster Tools                                    | Yes      |
| Website match            | The sending domain's root matches or redirects to the website on your CV identity request | Yes      |
| Registrar expiry         | The domain's registration does not expire before your CV request does                     | Yes      |
| Root unique on platform  | No other organization is submitting the same root                                         | No       |
| One address per request  | Your CV request does not already carry a submitted address this cycle                     | No       |
| Sending history          | The identity has a recent record of sending to Gmail                                      | No       |

A failed non-blocking check shows as a warning you can acknowledge; a failed
blocking check keeps the submit action hidden until it is fixed.

## The exact address

Campaign Verify verifies the **root domain** and then passes the **full
address you submit**, subdomain included, on to Google. The root has to match
or redirect to the committee website on file with your Campaign Verify
identity request. The platform shows you the exact address to enter,
including the subdomain, so there is nothing to retype or guess.

## Steps in the Campaign Verify portal

<Info>
  Steps written from Campaign Verify's published guidance and confirmed against
  the live portal after September 8, 2026.
</Info>

<Steps>
  <Step title="Sign in">
    Sign in to Campaign Verify at app.campaignverify.org with the account
    that holds your committee's identity verification.
  </Step>

  <Step title="Open the verified request">
    Open the verification request whose status is Verified. Only a current,
    verified identity request can carry a sender email address.
  </Step>

  <Step title="Find Verified Email Senders">
    Find the Verified Email Senders section of that request.
  </Step>

  <Step title="Enter the exact address">
    Enter the sender address exactly as shown on the sender page in
    Political Comms, including the subdomain. Campaign Verify verifies the root domain and passes the full
    address to Gmail.
  </Step>

  <Step title="Submit">
    Submit. Campaign Verify checks the domain in under a minute and shows
    the result in the portal.
  </Step>

  <Step title="Mark it submitted">
    Return to the sender page and mark the address as submitted so we can
    watch for Gmail's confirmation.
  </Step>
</Steps>

A few things to keep in mind before you submit:

* You get three submission attempts per verification request, and one
  address change after approval. Check the address before you submit.
* Approved addresses reach Gmail overnight. Gmail activates the program
  within one to two business days, and we confirm it from Google Postmaster
  Tools.
* The address expires with your Campaign Verify identity verification. A new
  identity verification and a new address submission renew it.
* Being verified is never required to send email. It improves Gmail delivery
  for registered committees; it does not change anything else.

## After you submit

Campaign Verify forwards approved addresses to Google on a nightly feed.
Google activates the program within one to two business days of that feed,
and we confirm activation from Google Postmaster Tools rather than guessing
from the submission alone.

| Status              | Meaning                                                                                                            |
| ------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Not eligible**    | One or more blocking checks are failing. Fix them to move forward.                                                 |
| **Eligible**        | Blocking checks pass, but the platform has not finished its own verification pass yet.                             |
| **Ready to submit** | All blocking checks pass. Submitting in Campaign Verify is the next step.                                          |
| **Submitted**       | The address is in Campaign Verify's queue, waiting for Google's confirmation.                                      |
| **Verified**        | Google confirmed the program is active for this address's root domain.                                             |
| **Suspended**       | Google paused the program for 7 days after a spam-rate breach. It re-enrolls automatically once the rate recovers. |
| **Rejected**        | Campaign Verify or Google rejected the submission. Check the note for why.                                         |
| **Expired**         | The underlying Campaign Verify identity verification lapsed. Renew it and resubmit.                                |

## Where the status shows

* The sender identity page, in its Gmail Verified Sender Program section.
* The senders list, as a badge on the identity's row.
* The sender picker when building a campaign.
* **Admin > Domains**, as a chip on the domain's email row.
* Your Campaign Verify page, listing the addresses submitted or verified
  under that identity request.
* Over the API, as `gmail_verified_sender` on `/v1/email/senders` objects.

## Expiry and renewal

The address expires when the Campaign Verify identity verification behind it
expires. Verifications filed before November 15, 2026 expire January 31,
2027, in line with Campaign Verify's cycle-end rule. We send a reminder 30
days before that date so a renewal, and a resubmission of the address, can
happen before the program lapses.

## Suspension

Google suspends the program for a domain for 7 days if its 14-day spam rate
breaches the 0.3% threshold, then re-enrolls it automatically once the rate
recovers. We alert your organization when the reported spam rate reaches
0.2%, ahead of Google's threshold, so there is room to act on list quality
before a suspension happens. See
[Google Postmaster Tools](/help/email/google-postmaster-tools#spam-rate-alerts).