Connecting Google Postmaster to EasySender
This guide explains how to connect your Google Postmaster account to EasySender to start monitoring your domain’s reputation and email performance data directly within EasySender.
Step 1: Add Your Domain to Google Postmaster
- Go to Google Postmaster Tools.
- Click on the red + sign to add your domain
- Enter your domain name and proceed.
Step 2: Add the TXT Record in Your DNS
- Google will display a unique TXT record for domain verification.
- Copy that record and log in to your DNS provider.
- Add a TXT record under your domain’s root (
@
) or specified subdomain and click on Save
Step 3: Verify the Domain in Google Postmaster
- After DNS propagation (can take a few minutes), go back to Google Postmaster.
- Click “Verify” next to your domain.
- Once verified, the domain will be added and marked as "Verified."
Step 4: Initiate Connection from EasySender
- Log in to your EasySender account.
- Go to Post-Send > Google Postmaster.
- Click “Connect”.
Step 5: Authenticate and Authorize the Connection
- A pop-up will ask you to authenticate with your Google account that owns the Postmaster domain.
- Authorize EasySender to access Google Postmaster data.
Step 7: Connect your domain(s)
- A popup window will appear to choose all your connected domain(s) on Google Postmaster
- Choose the ones that you want to integrate with EasySender
- Click on Connect
Step 6: Monitor Data in EasySender
- Once connected, domain-level metrics such as Spam Rate, IP Reputation, Domain Reputation, and Feedback Loop data will be available under the Dashboard Overview.
- Data is updated automatically from Google Postmaster.
Note:
- All data is pulled directly from Google Postmaster. EasySender does not generate or inject any data on its own.
- If there’s no data shown in Google Postmaster, then EasySender will not display anything either. Google controls what data is available per domain and IP.
- This integration currently uses Google Postmaster API v1. Version 2 is not supported yet, as Google hasn't enabled third-party API access for v2.