SleekView for Gmail SMTP for WordPress: send logs as tables
Gmail SMTP for WordPress sends through the Gmail API using OAuth credentials stored in wp_options. SleekView turns local send-log rows into a sortable workspace so support and ops can audit deliveries without leaving WP Admin.
♾️ Lifetime License available
OAuth credentials and send logs as tables
Gmail SMTP for WordPress authenticates against the Gmail API using OAuth credentials stored in wp_options under keys like gmail_smtp_client_id, gmail_smtp_client_secret, and gmail_smtp_token. When the local log is enabled, per-send rows land in wp_gmail_smtp_log with recipient, subject, status, Gmail API response, and source plugin.
The default admin shows a credentials tab and a flat log view. There is no saved-view layer, no per-source filter, no bulk retry. Auditing delivery for a specific recipient or order ID means scrolling through pages of rows. Token-rotation events are hidden in the credentials tab rather than alongside sends, which makes correlating an outage with an expired refresh token harder than it should be.
SleekView reads the local log directly and exposes recipient, status, API response code, source plugin, and the active OAuth token age as first-class columns. Bulk retries route through the plugin's send handler so the OAuth refresh, the rate-limit handling, and registered wp_mail filters all fire correctly.
Workflow
Gmail SMTP log as a workspace
Enable the local log
wp_gmail_smtp_log with recipient, subject, API response, and source.
Map the log table
wp_gmail_smtp_log. Status, API code, and source plugin become first-class columns alongside recipient and subject.
Watch token age
Retry in bulk
wp_mail filters fire.
Sample columns
A typical Gmail SMTP send log
wp_options (gmail_smtp_*) + wp_gmail_smtp_log
| Recipient | Subject | Status | API code | Source | Sent |
|---|---|---|---|---|---|
| alex@studio.co | Quote attached | Sent | 200 | WPForms | Apr 24 |
| ria@design.io | Booking confirmed | Sent | 200 | Amelia | Apr 24 |
| tom@hello.dev | Password reset | Throttled | 429 | core | Apr 23 |
| mia@brew.coop | Newsletter | Auth error | 401 | MailPoet | Apr 22 |
Comparison
Default Gmail SMTP for WordPress admin vs SleekView
Default Gmail SMTP for WordPress admin
- Credentials tab is separate from the log view
- No saved-view layer on the local log
- No grouping by Gmail API code or source plugin
- Token-age and refresh state hidden in the credentials tab
-
Per-source attribution requires SQL on
wp_gmail_smtp_log
SleekView
-
Log workspace read from
wp_gmail_smtp_log - Filter by API code (200, 401, 429) and source plugin
- OAuth token age surfaced as a column for outage correlation
- Bulk retry routes through the plugin's refresh + send handler
- Saved views for throttled and auth-error cohorts
Features
What SleekView gives you for Gmail SMTP for WordPress
Token-aware log
Token age surfaces as a column alongside each send's status. Correlate auth-error spikes with token-refresh events to see when an expired refresh token caused an outage.
Rate-limit cohorts
Filter to 429 (throttled) responses to find which source plugins push send volume over the Gmail per-user limit. Group by source to surface the integration that needs throttling.
Bulk retry with refresh
Select failed rows and trigger the plugin's send handler. The retry handles OAuth refresh and the Gmail API rate-limit backoff automatically; wp_mail filters fire.
Audience
Who uses SleekView for Gmail SMTP for WordPress
Support
Confirm receipt or notification delivery by recipient. The API code column makes the difference between throttled, bounced, and auth-failed sends obvious without opening Gmail.
Developers
Audit which plugins hit the Gmail per-user send limit. Group by source and API code 429 to find the integration that needs a queue or throttle in front of wp_mail.
Site admins
Watch for auth-error (401) clusters as an early sign the OAuth refresh token has expired. The saved view fires a flag well before deliverability drops to zero.
The bigger picture
Why Gmail-API sends need an OAuth-aware workspace
Gmail-API sending is reliable until the refresh token expires, the per-user rate limit is hit, or a sender-mismatch policy blocks the from-address. Each of those failures has a distinct API response (401, 429, 400) that the plugin's log captures but its viewer does not group meaningfully. Operators end up reading line-by-line through pages of rows when a single saved view filtered to 401 would surface an auth-token issue, or a saved view filtered to 429 would point at the integration pushing past the per-user send limit.
SleekView reads the same wp_gmail_smtp_log table, joins the OAuth token-age data, and exposes API code, source plugin, and token age as filterable columns. Support gets a same-window delivery answer. Developers can find the integration that needs throttling.
Site admins can watch the auth-error count for an outage signal before deliverability hits zero. The plugin keeps the OAuth handshake, the rate-limit handling, and the option storage. SleekView gives the resulting log a workspace that scales with the volume of sends and the operational pace of the team.
Questions
Common questions about SleekView for Gmail SMTP for WordPress
Yes for the send-log workspace. With logging off, SleekView still surfaces OAuth credential rows and token-age data from wp_options, but per-send rows require the plugin's log option to be on.
The client ID and secret rows are editable from a saved configuration view, but rotating the refresh token requires the standard OAuth flow in the plugin's credentials tab. SleekView surfaces the rows; the OAuth handshake stays with the plugin.
Yes. The Gmail per-user limit surfaces as 429 responses in the log. Filter to that code to find the source plugin pushing past the limit, and add a queue or throttle in front of wp_mail for that integration.
No. The plugin rotates the log on its configured retention setting. SleekView reads existing rows and respects whatever limit is set; it does not extend retention.
Yes. Saved views export to CSV with the filtered cohort. Useful for sharing a deliverability incident report or for documenting an auth-token expiry timeline.
The log format is identical for both account types because the API surface is the same. The plugin's own credentials configuration determines which is in use; SleekView reads whichever applies.
Deletes and PII redaction route through the plugin's own retention and erasure hooks where available. Redaction status surfaces as a column so audits stay truthful.
Yes. The source field on each log row, when set by the originating plugin, becomes a first-class filter. Per-source cohorts (Amelia, WooCommerce, WPForms, core) become saved views.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Woocommerce Invoice System
- Wpc Buy Now Button
- Woocommerce Product Comparison
- Woocommerce Startrack
- Woocommerce Ccavenue
- Fkcart
- Woocommerce Min Max Quantities
- Printful Integration
- Woocommerce Quaderno
- Woocommerce Shippo
- Woocommerce Vertex Tax
- Razorpay For Woocommerce
- Woocommerce Checkout Fees
- Edd Frontend Submissions
- Authorize Net