by Redigit
1 (1 reviews)
Emerge Campaigns
Self-hosted email campaigns for WordPress. Authored in the block editor, sent through your own mailbox, tracked in your own database.
Compatible with WP 7
v1.0.0
Current Version v1.0.0
Updated 1 week ago
Last Update on 05 Jul, 2026
Refreshed 13 hours ago
Last Refreshed on
Rank
#52,677
—
No change
Active Installs
1+
—
No change
KW Avg Position
123
-2 better
Downloads
183
+3 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(1 reviews)
Next Milestone 10
0+
10+
51,881
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#52,677
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
1 reviews
Overall
20%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| segments | 123 | — | Tag | 3 days ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.0
- Last Updated
- Jul 05, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7
- PHP Version
- 8.1 or higher
- Author
- Redigit
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 1
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,742
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#989
Contact Form 7
10M+ installs
#3
WP Mail SMTP by WPForms - The Most Popular SMTP and Email Log Plugin
4M+ installs
#12
MC4WP: Mailchimp for WordPress
1M+ installs
#34
Frequently Asked Questions
Common questions about Emerge Campaigns
Emerge Campaigns dispatches every send via WordPress's wp_mail() function — the same function any other WordPress plugin uses to send email. Whatever transport your site is already configured for (host SMTP, a transactional-email plugin, or PHP's default mail) handles the actual delivery. Deliverability depends on that configuration.
A daily background sync pulls from whichever sources you enable in Settings: WordPress users, comment authors, WooCommerce customers, Easy Digital Downloads customers, Jetpack contact form submissions, Jetpack Subscriptions, MailPoet subscribers, Newsletter Plugin subscribers, Contact Form 7 submissions (via Flamingo), and Gravity Forms entries. You can also add contacts manually from the Contacts screen, and accept self-signups via the Emerge Subscribe form (shortcode, block, or widget).
A static segment is a manually-curated list — pick the contacts you want, save the segment, those contacts are members until you remove them. A dynamic segment is a rule definition (e.g. "source = woocommerce AND subscribed_at >= 2026-01-01") evaluated at send time, so membership stays current as new contacts arrive.
A Broadcast is a one-time send — compose it, pick an audience, and send now or schedule it for later. A Newsletter is a recurring series: you choose a daily / weekly / monthly cadence and a time of day, and a background sweep spawns each issue automatically. Newsletters have their own menu and a read-only Issues log showing every issue that's gone out. Both are built on the same engine; they're just separated so the one-off and ongoing workflows stay uncluttered.
Yes — that's what the Newsletter surface is for. Set a daily, weekly, or monthly cadence with a send time; a background sweep job spawns the next issue as a fresh child campaign at each interval. The parent stays editable, so changes to the template or segment propagate forward. By default a new issue is only spawned when the rendered content has actually changed since the last one (an opt-out "send only if content changed" checkbox) — ideal for newsletters that pull dynamic content like recent posts. You can pause or stop the series at any time.
If the companion Emerge Mail plugin is delivering your mail, it reports bounces and complaints back to Emerge Campaigns. A hard bounce or spam complaint suppresses the contact — it's dropped from the mailable audience and hidden from the default Contacts view — while a soft bounce is marked but kept mailable. On a hard bounce you can optionally (off by default) delete a linked WordPress user, reassigning their content, and reassign the bounced address's anonymous comments to a fallback user. Without Emerge Mail, this is simply inactive.
Yes. Templates render through the same the_content filter pipeline as front-end posts, so Query Loop and any other block that works in posts works in emails. This is especially useful for newsletter templates that pull in recent posts dynamically.
Three ways, all interchangeable: drop the [emerge_campaigns_subscribe] shortcode anywhere on a post or page; add the "Emerge Subscribe" block in the block editor; or add the "Emerge Subscribe" widget to a sidebar or block-based widget area. All three render the same form, accept the same options (heading, description, button label, optional first/last name fields, optional consent line), and submit to the same endpoint. Submissions land in the Contacts table with source emerge_subscribe.
Yes. With JavaScript enabled, submissions go through a small vanilla-JS module that posts to a REST endpoint and renders the result inline with no page reload. With JavaScript disabled or blocked, the same form falls back to a classic POST + redirect that surfaces the same result inline on the next render. Same nonce, same validation, only the transport differs.
Every send has a unique token. The token is used to build a per-recipient unsubscribe URL placed in both the email body ({{unsubscribe_url}}) and the List-Unsubscribe header. Mail clients that support RFC 8058 (Gmail, Apple Mail) show a native one-click unsubscribe button that POSTs to the URL without a browser round-trip.