How to Use Email Log Search (Message Trace) in Google Workspace

The short answer
Email Log Search is Google Workspace’s message trace. In the Admin console go to Menu > Reporting > Email Log Search, pick a date range within the last 30 days, and search by sender, recipient, subject, IP or Message ID. Expand a result to see each delivery step. Mail older than 30 days needs the recipient plus the Message ID.
Use Email Log Search (message trace) in Google Admin to see if a message was delivered, bounced or quarantined. Menu path, 30-day limit, Message-ID lookup.
On this page
- 01Is there a message trace in Google Workspace?
- 02Before you start
- 03How to run a message trace (Email Log Search) in Google Admin
- 04Email Log Search delivery statuses explained
- 05Post-delivery statuses and spam reasons
- 06Can you use Email Log Search for emails older than 30 days?
- 07Where Google Workspace email logs live
- 08Can you access Email Log Search through an API?
- 09What to do when Email Log Search does not find the message
- 10Where AI Emaily fits
Email Log Search (ELS) is the Google Workspace Admin console tool that shows what happened to a message sent to or from your domain: delivered, bounced, dropped, quarantined or marked as spam, and what the recipient did with it afterwards. Open it at Menu > Reporting > Email Log Search, choose a date range up to 30 days back, enter the sender, recipient or Message ID, and expand a row to read each delivery step.
The facts below come from Google’s Workspace Admin Help pages “Find messages with Email Log Search” and “Email Log Search delivery status definitions”, checked in October 2026. Google renames console labels from time to time, so if a menu item reads slightly differently in your console, those two pages are the reference.
Is there a message trace in Google Workspace?#
Yes. Microsoft 365 calls it message trace; Google calls the same job Email Log Search. If you are coming from the Exchange admin center, the mental model carries over: you search by sender, recipient, date and message ID, and you get a per-message record of how the mail moved through Google’s servers. The differences are in the details. Email Log Search covers Gmail traffic for your domain, including mail sent to Google Groups, and it adds post-delivery information (opened, read, labelled, marked as spam) that a classic message trace does not show.
What it does not do: Email Log Search cannot show message content. Google’s help page says so directly and points to other tools for that, including Google Vault and content compliance rules.
- Where: Admin console > Menu > Reporting > Email Log Search (direct link: admin.google.com/ac/emaillogsearch).
- Who: an admin with the Gmail Settings administrator privilege. Super admins have it.
- How far back: custom searches cover the last 30 days. For older mail, choose Older than 30 days and enter the recipient’s full address plus the Message ID.
- Fastest lookup: the Message ID. When you search by Message ID, Google ignores the date range you picked.
- Output: a status for every delivery step, a post-delivery status in the recipient’s mailbox, and optional export to Google Sheets or CSV.
Before you start#
You need the Gmail Settings administrator privilege. Super admins have it; for anyone else, a super admin can create a custom admin role that includes it, rather than handing out full super admin rights just for log lookups. Google’s page also notes that Email Log Search is not available to resellers who manage a customer’s Workspace subscription on the customer’s behalf.
Google lists Email Log Search as available on Business, Enterprise, Education, Frontline and Nonprofits editions, as well as legacy G Suite Basic and Business. The 30-day window is the same rule across them; it is not something a higher edition lifts.
Gather what you know first. The sender’s address, the recipient’s address and roughly when it was sent are usually enough. Better still, get the Message ID from the sender. In Gmail, they open the message, choose More (the three-dot menu) > Show original, and copy the Message-ID line. In classic Outlook for Windows it sits under File > Properties > Internet headers; in new Outlook and Outlook on the web, open the message’s More actions menu and view the message details or source. For more on reading headers, see how to check email headers.
Get the Message ID before you open the tool
How to run a message trace (Email Log Search) in Google Admin#
These steps follow Google’s current help page. Date is the only required field; everything else narrows the result.
- 1
Open Email Log Search
Sign in at admin.google.com with an account that has the Gmail Settings administrator privilege. Go to Menu > Reporting > Email Log Search, or open admin.google.com/ac/emaillogsearch directly. If you land in a normal Gmail inbox, you are signed in as a regular user; switch accounts.
- 2
Try a predefined search, or open Custom search
The Predefined search tab has ready-made searches: all messages from today, all messages since yesterday (the past 48 hours), all messages in the last 7 days, and messages sent from or received by your domain since yesterday. For a specific message, use the Custom search tab.
- 3
Pick a date range and enter your criteria
Choose Today, Since yesterday, Last 7 days, Specify range (any range within the past 30 days) or Older than 30 days. Then fill in what you know: Sender (full, partial or Return-Path address), Recipient, Sender IP, Recipient IP, Subject or Message ID. Partial addresses need at least three characters, wildcards are not supported, and quotes force an exact match. Subject matching is not case-sensitive.
- 4
Run the search
Google says results come back within about 1 minute to 1 hour, depending on how many messages match. One search returns up to 1,000 messages. If you hit that ceiling, search with the recipient as the only criterion, or use the Message ID with a specific recipient.
- 5
Expand a message and read the delivery steps
Each message shows a log entry for every delivery step, each with its own status, and a post-delivery section for each recipient covering labels, where the message sits in the mailbox, whether it was marked as spam, and whether it was deleted after delivery. Use the export option to save results to Google Sheets or a CSV file for a ticket or an incident record.
Email Log Search delivery statuses explained#
Email Log Search reports a status for each step a message passed through, so one message usually carries several statuses: received, inserted into the Gmail delivery pipeline, then delivered (or not). Google’s help page notes a message typically has about five to seven log entries per recipient. The final step is the one that tells you the outcome. The table covers the delivery statuses you will meet most often, in Google’s own wording, paraphrased.
| Delivery status | What Google says it means | What to check next |
|---|---|---|
| Delivered / Delivered to Gmail inbox | The message reached the recipient’s Gmail mailbox or a third-party SMTP server. The recipient may since have archived, labelled or deleted it. | Read the post-delivery status. If the user still cannot find it, look at filters, labels, forwarding and the Spam folder. |
| Delivered to an SMTP server | Google handed the message to an outside mail server at the listed address, with the encryption used. | Google’s part is done. Ask the receiving side’s admin to trace it on their system. |
| Bounced | Delivery failed because of a problem with the email account, such as a blocked IP, sending or receiving limits, or a policy rule. | Check the step detail for the reason, then review routing and content compliance rules and the account’s limits. |
| Dropped | Not delivered because the sending server has a bad reputation, or because a Gmail catch-all or routing rule affected it. | Review your routing and catch-all settings; for inbound mail, the sender needs to fix their server reputation. |
| Rejected | Automatic outbound spam filtering marked the message as spam. This applies to mail your users send out. | Look at what the user sent and in what volume. An account sending spam-like mail may be compromised. |
| Marked spam | Gmail classified the inbound message as spam. A spam classification reason is shown alongside it. | Read the reason (for example a DMARC failure or a suspicious link). If it is wanted mail, see the sender-side fixes or an allowlist. |
| Bypassed spam | The message was flagged as spam but delivered normally because of a spam filter setting. | Confirm the setting that let it through is intentional. |
| Quarantined / Released from quarantine / Rejected from quarantine | A setting held the message for admin review; an admin then released it for delivery or deleted it. | Review held mail in Admin Quarantine and check which setting sent it there. |
| In progress | The message is still passing through Google’s servers. | Wait and search again later. |
| Delivered to group for distribution to members / Forwarded by group / Sent to group members | The message reached a Google Group address and was expanded to members. | Search each member as the recipient to see their individual delivery. |
Post-delivery statuses and spam reasons#
After delivery, Email Log Search reports what happened in the recipient’s mailbox. Google lists these post-delivery statuses: Label (any labels other than Inbox), Marked important, Marked unimportant, Opened and read, Opened and marked unread, Unopened and unread, Unopened and marked read, Seen (displayed in the user’s Gmail view), Unseen, Spam (the recipient manually marked it as spam) and Starred. There is also an Opened delivery-log entry recorded each time the message is opened, with the date, IP address, session ID and client type.
These settle most “I never got it” disputes. Unopened and unread means it arrived and nobody looked. Spam here means the recipient reported it themselves, which is different from the Marked spam delivery status, where Gmail’s filter made the call.
When a message has the Marked spam delivery status, Email Log Search adds a spam classification. Google’s reasons include: the message failed DMARC authentication, the sender is listed in public realtime blocklists, the sender has poor reputation, the message contains suspicious links or attachments, the recipient has marked similar messages as spam before, and the message was classified based on an administrator-configured spam setting. For a DMARC failure on mail from your own domain, start with checking SPF, DKIM and DMARC results in headers. If internal mail is landing in spam, see why Google Workspace internal email goes to spam.

Can you use Email Log Search for emails older than 30 days?#
Only in a narrow way. Custom searches cover the last 30 days. For anything older, choose Older than 30 days and enter both the recipient’s complete email address and the Message ID. Google lists three limits for those searches: you cannot search with a Google Group address, the recipient address and Message ID are both required, and Email Log Search returns post-delivery status only, not the delivery steps.
Google Vault does not extend Email Log Search. Vault retains, holds and searches message content under your retention rules; it does not keep delivery logs. If you need to show that a message existed and what it said, Vault is the tool. If you need to show how it was routed, you have 30 days. For the difference, see what Vault retains versus what Email Log Search shows.
Export the trace while it still exists
Where Google Workspace email logs live#
Email Log Search is one of four places Workspace keeps email records, and each answers a different question.
| Tool | Where in the Admin console | What it answers |
|---|---|---|
| Email Log Search | Reporting > Email Log Search | How was this message routed, and was it delivered? Last 30 days, no content. |
| Gmail log events (audit and investigation) | Reporting > Audit and investigation > Gmail log events | What did users and admins do with mail: sends, views, link clicks, attachment downloads, spam classification, quarantine. Needs the Audit & Investigation privilege. |
| Security investigation tool | Security > Security center > Investigation tool, data source Gmail log events | The same Gmail log events, in Google’s security investigation workflow. Needs the Security center privilege and Enterprise Standard and Plus, Education Standard and Plus, Frontline Standard and Plus, Enterprise Essentials Plus and Cloud Identity Premium. |
| Google Vault | vault.google.com | What did the message say, and is it under retention or legal hold? Content, not delivery logs. |
Can you access Email Log Search through an API?#
Google’s Email Log Search help page describes exporting results to Google Sheets or CSV. It does not document an API for Email Log Search itself. There are two programmatic routes to Gmail log data instead.
First, Gmail log events are available in the Admin SDK Reports API. Google announced this on its Workspace Updates blog in September 2025, for licenses that are eligible for audit logs. These are the activity events from the audit and investigation tool, not the hop-by-hop delivery steps Email Log Search shows.
Second, Gmail logs can be exported to BigQuery on Enterprise Standard and Plus, Education Standard and Plus, Frontline Standard and Plus, and Enterprise Essentials Plus. You set up a BigQuery project and then turn on the export in the Admin console; Google’s “About reporting logs and BigQuery” page walks through it. Set it up before an incident rather than during one, and check that page for what data the export holds from the day you enable it.
What to do when Email Log Search does not find the message#
Most failed searches come down to the window, the address, or a group.
| Symptom | Likely cause | What to do |
|---|---|---|
| No results | Range too narrow, an alias or alternate address, or the message is older than 30 days. | Widen the range to the full 30 days. Try the primary address and any aliases. For older mail, use Older than 30 days with the recipient and Message ID. |
| Searching a group address returns nothing useful | Group searches need the Message ID, and they do not show delivery to individual members. | Search with the Message ID, then search each member as the recipient. |
| Delivered, but the recipient cannot find it | A filter, label, forwarding rule or the user’s own action moved it. | Read the post-delivery status (label, location, deleted). Then check filters and [hidden forwarding rules](/blog/gmail-hidden-forwarding-rule-check). |
| Bounced or Dropped with a policy reason | A routing, catch-all or content compliance rule acted on the message. | Note the rule in the step detail, then review it under Apps > Google Workspace > Gmail > Compliance or Routing. See [content compliance rules](/blog/google-workspace-content-compliance-rules) and [routing rules](/blog/google-workspace-email-routing-rules). |
| Quarantined, and the user never saw it | A setting held it for admin review. | Release it from Admin Quarantine if it is legitimate, and adjust the setting that caught it. |
| Too many results, or the search is slow | Broad criteria; one search caps at 1,000 messages. | Search by recipient alone, or by Message ID plus a specific recipient. |
Where AI Emaily fits#
Email Log Search answers what happened to a message after someone asks. It does not tell the sender that a thread has gone quiet. That is a different job, and it is the one we built AI Emaily for: an AI-native email client that connects Google Workspace, Gmail, Outlook and IMAP mailboxes and tracks threads still waiting on a reply, so the follow-up goes out before it turns into a “did you get my email?” ticket. It does not replace Admin console logs or Vault. AI Emaily has a 7-day free trial on its Pro and Autopilot plans; current prices are on the pricing page.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Google Workspace Admin Help — Find messages with Email Log Search
- Google Workspace Admin Help — Email Log Search delivery status definitions
- Google Workspace Admin Help — Gmail log events
- Google Workspace Admin Help — About reporting logs and BigQuery
- Google Workspace Updates — Updates to Gmail log events (September 2025)

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.