Gravity Forms Email Users - WordPress Plugin

Gravity Forms Email Users Guide: How to Send Emails to Form Users Without a Separate Mailing System

Gravity Forms Email Users is useful when your site already has a Gravity Forms form, the entries contain email addresses from attendees, customers, donors, or applicants, and the site owner needs to send them a one-time or segmented message. It is not a replacement for a full email marketing platform. It is a practical way to communicate with people who have already submitted their information through a specific form.

In this guide, we will cover more than just the Forms > Email Users path. We will also look at how to prepare the form, choose the right email field, limit recipients with conditional logic, use merge tags safely, review the message before sending, configure unsubscribe behavior, and understand where the line is between a convenient entry-based mailing workflow and a job better handled by an SMTP service or marketing platform.

This article is intended for a WordPress administrator, site editor, or developer responsible for a registration form, event application, donation form, survey, waiting list, or a similar workflow. After reading it, you will be able to do more than just enable the plugin. You will be able to build a verifiable process: prepare the data, send a test campaign, confirm the result, and quickly find the cause if the email is not delivered or the plugin menu does not appear.

Where This Plugin Fits in the Gravity Forms Workflow

The core idea behind Gravity Forms Email Users is simple: the email is sent not to an abstract subscriber list, but to existing entries from a selected form. The user chooses a form, selects the Email field, writes the subject and message, optionally enables conditional filtering, saves a draft, reviews the generated emails, and only then starts the send.

This matters up front because the plugin does not collect addresses on its own or guess who should receive a message. It works with whatever Gravity Forms already stores. If the form has no Email field, if not every participant filled it in, or if older entries contain address errors, the quality of the mailing will depend directly on that source data.

In standard Gravity Forms notifications, an email is sent at the moment of an event: the form is submitted, payment is completed, an entry is created, or a condition is met. Email Users solves a different problem. It is meant for cases where the event has already happened and you need to return to that group later: send a reminder to seminar attendees, notify ticket buyers about a time change, ask donors to complete a short survey, send a continuation link for an application, or update people on a waiting list.

The plugin's biggest strength is the connection between "form - entries - email". You do not need to export a CSV, compile a list by hand, or build a separate mailing list for a single message. But that same strength defines its limit: if you need automation sequences, behavior-based segments, A/B tests, detailed open analytics, or large recurring campaigns, Email Users alone will not be enough.

What It Uses as Input

The plugin works from the entries of a specific form. Those entries need to contain the data required to identify the recipient's address and personalize the message. In most cases, that means an Email field, first name, last name, selected ticket, application type, interest category, payment status, or another response you plan to use for audience filtering.

If the form was created a long time ago, review several entries manually before the first mailing. Make sure the email field was actually filled in, that it is not optional in workflows where you need a recipient, and that different form paths do not leave the address blank. For multi-page forms, it is especially important to confirm that users reach the page containing the Email field before the entry is saved.

What the Administrator Controls

In the Email Users interface, the administrator controls the form selection, the email field selection, the subject, the content, sender fields, BCC and Reply To, as well as filter conditions. Gravity Wiz documentation specifically notes support for merge tags in the subject, message, From, Reply To, and BCC fields. That lets you insert entry data into the email, but it also requires care: an incorrect merge tag does not automatically turn into good personalization.

The administrator also controls when the message is sent. The plugin lets you save a draft and review the generated emails before launch. In practice, that protects against two common mistakes: sending the message to the wrong audience and sending a message where personal data was merged in differently than expected.

What the Recipient Sees

The recipient sees a normal email generated by WordPress through the site's mail system. If merge tags are used in the message, the recipient will see their entry data merged into the email. If an unsubscribe link is added using the plugin's special merge tags, the recipient will be able to opt out of future Email Users messages according to the configured behavior.

There is no separate Email Users portal for the recipient. As a result, the quality of the outcome depends on three things: accurate entry data, clear message content, and reliable delivery through domain email, SMTP, or another mail transport.

When Gravity Forms Email Users Is a Good Fit and When Another Tool Is Better

The plugin works well on sites where Gravity Forms is already the center of the lead collection process. That might be an education project, an event site, a nonprofit organization, a consulting business, a club, a local service, a webinar registration workflow, preliminary applications, or a contact form that needs a follow-up.

A typical use case looks like this: people complete the form, the entries contain an email address and useful segmentation fields, and the administrator needs to send one message to all or part of that group. In that situation, Email Users saves time and reduces the risk of manual error. You are not copying addresses from Entries into an email client, storing an unnecessary CSV on your computer, or creating a temporary list in a third-party service.

The plugin is especially well suited to one-time and irregular communication:

• A reminder to everyone registered for a selected event.
• A message only to people who selected a specific option in the form.
• A follow-up after a consultation, survey, donation campaign, or registration.
• A link to a second form where some data can already be prefilled through a shared workflow with Gravity Forms Easy Passthrough.
• A short notice about a change in schedule, status, meeting location, or next step.

On the other hand, Email Users should not be treated as a full-featured bulk email marketing service. The official documentation explicitly describes it as a lightweight solution and recommends looking at a more robust email service if you need to send thousands of messages. That is not just a legal disclaimer. High volume increases the risk of limits imposed by your host, SMTP provider, and recipients' mail systems.

Practical rule: if you are sending to dozens or a few hundred addresses tied to a specific form, Email Users can be convenient. If you are building recurring mailings to thousands of subscribers with list-based unsubscribes, segmentation, reporting, and automated sequences, you are better off using Mailchimp, MailPoet, a CRM, or a dedicated transactional email service.

Who This Plugin May Not Be Right For

Email Users may not be the best choice if recipients need to be selected manually from individual entries. Gravity Wiz documentation notes that selecting individual entries directly is not the plugin's primary mode; for that use case, the developer recommends the Send Manual Notifications snippet and a Gravity Forms bulk action. So if you need to check five specific entries in the Entries list and send them a manually chosen notification, compare that workflow with Email Users before you adopt it.

The plugin also does not solve complex subscription policy requirements. It provides unsubscribe merge tags and hooks for customizing unsubscribe behavior, but it does not turn your site into a complete subscription center with topics, frequency controls, double opt-in, and behavior reporting. For legally sensitive marketing communications, you should separately verify consent rules, form wording, data storage, and the requirements of your jurisdiction.

Finally, the plugin does not fix mail delivery by itself. If WordPress email delivery is unreliable on your hosting, Email Users will run into the same problems as regular Gravity Forms notifications. Reliability is usually improved through Gravity SMTP, Post SMTP, WP Mail SMTP, Mailgun, Postmark, SendGrid, or a similar mail transport, not by pressing Send again.

What to Check Before Installation and Before the First Mailing

Before installing the plugin, separate technical readiness from editorial readiness. On the technical side, you need WordPress, Gravity Forms, Gravity Perks/Spellbook, and the form itself with saved entries. On the editorial side, you need a legitimate reason to contact people, a valid basis for that message, and copy that does not feel like a random mass email.

Start with the form. Open the editor and make sure the Email field exists as a dedicated Gravity Forms field, not as arbitrary text in a Single Line Text field. The official Gravity Forms documentation describes the Email field as a specialized field with email format validation and an address confirmation option. That matters for Email Users: using a real email field is the safer and cleaner way to select recipient addresses.

Then check the entries. A few test entries will show what values were actually saved. If older submissions collected addresses inconsistently, do not try to solve that with a mailing. Clean up the data first, review whether the field is required, enable email confirmation where users often make mistakes, and only then plan the send.

Site Email and Sender Domain

Gravity Forms and Email Users use the WordPress mail layer. Gravity Forms documentation on notification issues explains that Gravity Forms passes the message to wp_mail(), and from there delivery depends on WordPress, the mail server, and your domain configuration. That means that before your first real mailing, you should send a normal Gravity Forms notification for a test entry and confirm that it arrives.

Pay special attention to the From Email field. For both the form and future mailings, it is safer to use an address on your site's domain rather than a free personal address. If the sender appears to be Gmail or Yahoo but the message is actually sent from your site server, mail systems are more likely to treat it as suspicious. Gravity Forms troubleshooting documentation lists this as a standard item to verify.

Permissions and the Administrator Role

Email Users adds its own capability: gravityperks_gwemailusers. A standard admin role should receive it automatically, but Gravity Wiz documentation warns about one nuance: a role management or membership plugin may interfere with automatic assignment. If the menu item does not appear, that does not necessarily mean the installation failed. The role may simply need that capability added manually.

Do not give Email Users access to every site editor without review. The plugin makes it possible to send emails to people listed in form entries. That is an administrative action with real risk for domain reputation and data privacy. Access should be limited to people responsible for communication who understand which audience is being selected.

Consent, Context, and Privacy

From a technical standpoint, the plugin can send a message to addresses collected through the form. But not every technically possible email is appropriate. If the form was a support form, the user may have expected a reply about their request, not regular marketing messages. If the form was event registration, an operational update makes sense, while an unrelated offer requires separate evaluation.

A good practice is to make the form explicit about what messages a person may receive after submission. For older existing forms, do not retroactively expand the meaning of prior consent. If there is any uncertainty, keep the message operational, concise, and tied to the user's original action, and move marketing sequences into a tool that supports subscription management.

Installation Through Gravity Perks and Initial Verification

Gravity Forms Email Users is part of Gravity Perks. According to current Gravity Wiz documentation, installing and managing Perks is handled through Spellbook, the WordPress plugin and platform used for licensing, updates, and selecting individual perks. That means that after purchasing or enabling Gravity Perks, you will usually work through the Spellbook interface rather than uploading a separate ZIP like a random standalone plugin.

The overall process is straightforward: install and activate Gravity Forms, install Spellbook, connect your Gravity Perks license, open Spellbook > Perks, find Email Users, and activate it. After activation, check the WordPress menu: under Forms, you should see an Email Users item or a corresponding action in the form interface.

Do not start with real recipients right away. Create or choose a test form that includes an Email field, a Name field, and several entries using your test addresses. That lets you see how the plugin inserts merge tags, how the preview looks, and how WordPress sends the message without risking contact with a real audience.

Quick Check After Activation

1. Open Spellbook > Perks and confirm that Email Users is active.
2. Go to Forms > Email Users and make sure the page loads without errors.
3. Select a test form that already has saved entries.
4. Confirm that the correct email field appears in the list instead of an empty selector.
5. Write a short test email and click Save Draft & Review Emails.
6. Open the preview for one or two entries and check the data merge.
7. Send the message only to test addresses, then check the inbox, spam folder, and SMTP logs if available.

If the interface looks different at any step, do not assume the plugin is "broken." Gravity Wiz updates its products regularly, and both the WordPress admin UI and Gravity Forms also evolve. Focus on the functional checkpoints instead: is the perk activated, does it see the form, does it detect the Email field, does it generate a review, and does the message go out through the mail system?

What to Do If the Menu Does Not Appear

First, verify that Gravity Forms, Spellbook, and Email Users are all active. Then check the role of the current user. If the site uses a role editor, membership plugin, or a more complex permissions system, add the gravityperks_gwemailusers capability to the role that should manage mailings. Gravity Wiz documentation identifies this exact scenario as a known limitation.

If the capability is present but the menu still does not appear, temporarily log in as an unrestricted administrator. If the menu appears under that account, the cause is almost certainly permissions. If it does not appear anywhere, check whether the plugin is actually active, whether there is a conflict with another extension, and whether the site error log shows any PHP errors.

Email Setup Map: Form, Email Field, Subject, Message, and Service Fields

After installation, the most important screen is not the plugin list but the email composition page. This is where the connection between the selected form and the future recipients is defined. A mistake here can lead to sending to the wrong people, sending without personalization, or sending a message filled with technical strings instead of clear text.

Start by selecting the form. If the site has many forms with similar names, rename them in Gravity Forms so an administrator can easily tell which one is event registration, which is support, which is a donation form, and which is a test copy. Email Users shows the forms available on your site, and the person in the admin area should not have to guess.

Selecting the Email Field

Select the Email field that contains the recipient's address. In more complex forms, there may be several: the applicant's email, a parent's email, an accounting contact, or a contact person's email. You cannot assume the first available field is the correct one. Open a couple of entries and confirm whose address is stored in that field.

If the form uses Email Confirmation, the user entered the address twice. That helps reduce mistakes in submissions, but it does not guarantee deliverability. An address can be valid in format and still reject mail. For high-stakes mailings, it is useful to send a standard confirmation right after submission in advance and track how many messages bounce or fail in SMTP logs.

From, Reply To, and BCC

Email Users lets you use merge tags not only in the message but also in email fields. But for From Email, you should not substitute the user's address from the entry. In practice, it is much safer to keep the sender on the site's domain, such as This email address is being protected from spambots. You need JavaScript enabled to view it. or This email address is being protected from spambots. You need JavaScript enabled to view it., and use the user's address in Reply To only where that is truly needed. That aligns better with Gravity Forms deliverability guidance.

Use BCC carefully. It is not a good way to archive an entire mailing to an administrator's personal inbox if many emails are being sent. It is better to send a test, use SMTP logs, or rely on your mail service logs. Bulk BCC can create unnecessary load and make troubleshooting harder.

Subject and Message

The email subject should be short and clearly tied to the recipient's original action. Good examples include "Update on Your Registration," "Materials After the Webinar," "Link to a Short Survey," or "Meeting Time Change." A poor choice is a vague promotional subject line that gives the recipient no clue why they received the email.

The message can be formatted using the rich text editor. That is useful for links, short lists, and emphasis, but do not turn the email into a heavy page full of images. Email Users is intended for personal follow-up, not for a highly designed newsletter. If you need a visual template, responsive content blocks, click reporting, and campaign management, it is better to connect a mailing platform.

Always use the review stage before sending. The preview shows the actual message for a specific entry with merge tags already resolved. Open not just one but several entries from different segments. That is how you catch empty fields, conditions that selected the wrong audience, or wording that becomes awkward because of the user's data.

Filtering Recipients with Conditional Logic

One of Email Users' signature features is recipient filtering based on form entry data. In the official documentation, this is described as conditional logic: you can send a message to people who bought a specific product, answered a survey question a certain way, or fall into the required age group. In a real project, that turns the form into a simple but useful segmentation database.

Imagine an offline seminar registration form. It includes a field called "Participation Format" with values such as "in person" and "online," a "City" field, and a "Certificate Needed" field. After the event, you need to send different messages: a map and materials list to in-person attendees, a recording link to online attendees, and an additional form link to people who need a certificate. You could send one generic message, but then people would receive instructions that do not apply to them. Conditional logic lets you target the audience more precisely.

Segment Setup Workflow

A practical workflow looks like this:

1. Select the form that contains the accumulated entries.
2. Select the recipient's Email field.
3. Enable conditional logic for the mailing.
4. Define one or more conditions based on form fields.
5. Save the draft and open the review.
6. Confirm that the number and composition of emails match the intended segment.

The key point is verifying the result before sending. If the condition is based on a field with similar options, such as "VIP," "VIP + recording," and "VIP guest," it is easy to choose the wrong operator. In that case, it is better to review the matching entries in Gravity Forms Entries first and confirm that the saved values are actually what you expect.

When Not to Overcomplicate the Condition

Conditional logic is useful, but it is not a good idea to turn one email into a complicated web of exceptions. If you are trying to build a condition with five or six branches, multiple statuses, and text-based matches, the audience may need cleanup before the mailing. In some cases, it is safer to create a separate form for a specific campaign, add a hidden category field, or export entries for analysis than to send based on a fragile rule.

For repeated mailings, document the rule: which form, which email field, which conditions, who checked the preview, and how many recipients were expected. That is not pointless bureaucracy. It protects you from the situation where another administrator repeats the send a month later and has no idea why the audience changed.

How to Avoid Duplicates

Gravity Wiz documentation notes an important behavior: if the same email appears in multiple form entries, that person may receive one message for each submission by default. For registrations to multiple events, that may be fine. For a general account update, it can be annoying.

There is an official hook, gpeu_send_to_duplicates, that lets you change this behavior and avoid repeat emails to the same address. This is already a technical customization, so use it only when you are certain the message should be unique per email address rather than per entry.

add_filter( 'gpeu_send_to_duplicates', '__return_false' );

This change is based on an official Gravity Wiz hook. It is best added through Code Snippets, a small site-specific plugin, or another safe mechanism that will not disappear when the theme is updated. After enabling it, test a form with two entries using the same address: the review should show only one recipient. Rolling back is simple - disable the snippet and review the preview again.

Merge Tags, Unsubscribe, and Safe Personalization

Merge tags make Email Users far more useful than a basic message sent to a list of addresses. You can address the person by name, insert the selected event option, include a link to the next form, reference an application number, or use another saved response. But personalization is only safe when you understand which fields are reliably populated and how they appear in real entries.

Start simple. In your first test email, use the recipient's name, one link, and one meaningful value from the entry. Do not add ten tags at once. That makes it easier to spot empty data, values that are too long, or user-provided text that does not belong in the email subject.

Where Merge Tags Are Especially Useful

• In the greeting, if the form includes a Name field and users filled it in consistently.
• In the subject line, if you need to identify a specific event, application, or selected option.
• In a link to a follow-up form, if an Easy Passthrough token is being used.
• In Reply To, if the administrator needs replies to go to the address stored in the entry while keeping From Email on the site domain.
• In BCC only for narrow technical use cases, not as a way to manually copy every outgoing message.

If a field can contain user-entered text, use it carefully. For example, an answer to an open-ended question is usually better placed in the message body as a reference line rather than in the subject. The subject should stay clean, short, and independent of unpredictable long input.

Unsubscribe in Email Users Messages

Email Users documentation describes two special unsubscribe merge tags: {gpeu_unsubscribe_url} and {gpeu_unsubscribe_link}. The first outputs the URL, and the second outputs a ready-made HTML link. For messages that go beyond a purely operational response, unsubscribe should be part of normal communication rather than a hidden formality.

The text around the unsubscribe link should be clear: "If you no longer want to receive updates like this related to this form, use the unsubscribe link." Do not promise behavior that is not actually configured. Whether unsubscribe applies to all Email Users messages or only to messages from a particular form depends on the implementation and possible hook-based customization, so your site policy should reflect the actual behavior.

Gravity Wiz provides hooks for customizing unsubscribe URL arguments, link text, and the confirmation message. Those are useful for developers who need to send users to a custom page after unsubscribing or change the unsubscribe scope. In a standard setup, do not start with code. Insert the default link first, test it with a sample entry, and make sure the outcome matches your policy.

Draft, Review, and Send: Control Before You Reach a Real Audience

The Save Draft & Review Emails stage is one of the plugin's main safety mechanisms. It is not there just so you can "see whether the message looks nice." At this point, you verify three things: the recipients were selected correctly, the merge tags resolved properly, and the content fits the context of the form.

Do not skip the review even for a small audience. A mistake in a message sent to ten people can be just as damaging as one sent to a thousand if it contains personal data, the wrong link, or a promise meant for a different group.

How to Review the Preview Like a Human

Open several emails from different parts of the list. If the mailing is segmented, check entries that should be included and entries that should not. Compare the preview with the original entries. If the email contains a link, copy it from the preview and open it in a private browser window or as a test user.

You should never consider the email ready until the action link has been verified. If the user is supposed to go to a follow-up form, download a file, confirm attendance, or update information, that transition is the primary outcome of the email. A polished subject line and the correct first name will not save the workflow if the link points to the wrong page or the form does not accept the data.

Saving a Draft

Draft Emails are helpful when the message is being prepared by more than one person. For example, an administrator may assemble the audience, an editor may write the text, and an event manager may approve the final details. A draft lets you return to the message later without starting over. But a draft is not a substitute for the final review: new entries may have appeared or form data may have changed between drafting and sending.

If the audience needs to stay fixed, do not wait too long to send after the review. If a significant amount of time passes between review and send, repeat the verification. That is especially important for active forms where new entries continue to arrive.

A Small Pre-Send Checklist

How to Prepare an Email So It Feels Like a Continuation of the Form

Email Users gives you a technical way to quickly send a message based on entries, but a good outcome depends on how closely the email is connected to the original form. The recipient should immediately understand why you are writing to them. If the person registered for an event, start with that event. If they submitted a donation form, talk about the project they supported. If they requested a consultation, do not turn the follow-up into a generic promotional blast.

Strong Email Users copy is usually short, specific, and verifiable. It contains a reason for the message, personal context, one main action, and a clear link. If there are more than three different actions in the message, users will start choosing at random or do nothing at all. For one-off entry-based mailings, one clear message works better than trying to cram an entire newsletter into it.

Prepare a Mini Template Before You Open the Interface

Before opening Forms > Email Users, it is useful to sketch the message in a separate document. That reduces the risk of clicking the wrong button by accident and helps the team align on the purpose of the email. The mini template can be simple: subject, opening paragraph, body copy, action link, unsubscribe or service note. After the text is approved, move it into the plugin's rich text editor and check the merge tags in the preview.

For recurring workflows, keep a few internal templates: event reminder, survey follow-up, donation update, waiting list update, correction notice. That does not mean every email should sound identical. The template defines the structure, not the finished copy. Each time, update the event details, the link, the recipient condition, and the test entry used for verification.

Email Subject

The subject should explain the connection to the form without sounding pushy. For example, in a workshop registration workflow, "Information About Your Registration" or "Materials After the Session" is enough. Do not overload the subject with the site name, plugin name, or technical terminology. If you insert a merge tag into the subject, make sure the value is short and does not contain long user-entered text.

Opening Paragraph

The first paragraph should answer the question, "Why did I get this email?" A good formula is: "You submitted form X, so we are sending Y." There is no need to sound apologetic, and there is no need for a promotional intro. The person should understand the situation within five seconds and decide whether to keep reading.

Main Action

One primary link matters most in Email Users. It may point to a follow-up form, a materials page, instructions, a schedule, or an information update form. The link should be visible, but it does not need to be styled like an aggressive button when the message is sent from a simple rich text editor. Check the URL in the preview, because that is where merge tags become real values.

What Data Should Not Go Into the Email

Not every entry field belongs in an email. The form may contain internal comments, service statuses, technical IDs, IP addresses, payment notes, or responses the user does not expect to see in a message. Even if a merge tag is available, ask yourself: "Will the recipient understand why this is here?" If not, keep it for internal admin use only.

Handle sensitive data carefully. Email is not a secure storage medium. If the form collects medical, financial, legal, or other sensitive information, do not include that information in a bulk email. It is better to provide a link to a secure account area, an information update form, or a support contact where the person can confirm the action themselves.

Privacy check: open the preview as if you were the recipient and ask yourself whether every merged value is appropriate to display in a standard inbox. If something looks unnecessary or sensitive, remove it from the message.

How to Write for Segments

If recipients are selected through conditional logic, the wording should reflect that condition. There is no point in filtering people by "online attendance" and then writing the message as if it were relevant to everyone. Name the specific context: "You selected the online format," "You indicated that you need a certificate," or "You submitted for the second group." That tells the recipient the message is not random.

At the same time, do not expose unnecessary internal segmentation logic. A line like "You matched segment city = New York and status = paid" sounds technical and inappropriate. Translate the condition into human language: "We are sending this information to participants in the New York group." Keep the internal rule in team notes or your pre-send checklist.

Verifying the Result After Sending

Many administrators treat the Send Emails button as the end of the process. For a working mailing workflow, that is too early. After sending, you still need to confirm that the messages were sent, that test recipients received them, that the links work, and that the follow-up action actually happens. Otherwise, you will only discover the problem from user complaints.

Break post-send verification into three levels: technical delivery, user action, and the resulting data state inside Gravity Forms. Technical delivery tells you whether the site handed the messages off to the SMTP provider. User action shows whether test recipients clicked the link and reached the correct page. Data state shows whether new entries were created if the email led to a follow-up form.

What to Check in the First Few Minutes

Immediately after sending, check your own test addresses across different mail services. One address on a company domain and one address on a mainstream mailbox provider often reveal different outcomes. If the message arrives in a corporate inbox but lands in spam in a personal mailbox, the problem may be related to domain reputation, DNS, or message content.

If your SMTP plugin keeps email logs, open the most recent send. Look not only for errors, but also at the message count, send time, provider status, and retries. If some messages failed, do not blindly rerun the entire campaign. First determine which addresses failed and whether the issue was temporary, caused by a rate limit, authentication, or content rejection.

How to Tell Whether the Workflow Worked

For a message that only shares information, delivery and the absence of complaints may be enough. For an email that links to a follow-up form, you need a more concrete check: a test user opens the link, sees prefilled fields, submits the form, and the administrator sees a new entry. If Easy Passthrough is involved, make sure the data came from the original entry rather than from an earlier browser session.

For an event update, verify that the materials page opens without requiring login if the email is meant for all participants. For restricted materials, verify the opposite: that a random visitor does not gain access by accident. Email Users is responsible for sending the email, but the actual outcome often lives on a different page of the site, and that page needs to be tested too.

What to Document After a Successful Send

The minimum internal record should include the send date, the form, the email field, the recipient condition, the subject line, the action link, the number of previews and recipients, the test addresses, the SMTP provider, and notes on any issues. That makes the process repeatable and helps you answer quickly if someone asks why a specific person did or did not receive the message.

If these mailings are repeated, create a simple matrix: which type of email, which form, who approves the text, who checks the preview, who launches the send, and where the result is verified. Email Users remains a lightweight tool, but the workflow around it becomes mature. That process is what separates careful communication from a random mass email.

Practical Workflow: Post-Event Follow-Up with a Prefilled Form

Let us look at a workflow that clearly demonstrates the value of Gravity Forms Email Users. There is a registration form for a webinar or live seminar. Attendees submit their name and email. After the event, the organizer wants to send them an email with a link to a short survey. To avoid making people enter their name and address again, the follow-up form receives data from the original entry through Gravity Forms Easy Passthrough.

This workflow is supported by Gravity Wiz documentation and tutorials: Email Users sends the follow-up message, and Easy Passthrough adds a token to the link so the second form can pull data from the first entry. This is not a required integration for every site, but it is a good example of how Email Users can be more than just a "mass mailing tool" and instead become part of a broader action chain.

Goal

Collect honest feedback after the event without making the participant re-enter data the site already knows. The email should go only to people registered for the relevant event, and the link should open the survey form with the name and email fields already prefilled.

Preparation

The site should have Gravity Forms, Gravity Forms Email Users, and, if automatic data transfer into the second form is required, Gravity Forms Easy Passthrough enabled. The original registration form should include an Email field and the fields you want to pass through. The second form should contain the matching destination fields where those values will be inserted.

Start by configuring the Easy Passthrough feed on the survey form: select the original registration form and map the fields. Then verify that the token can be used in the link. Easy Passthrough documentation shows the query parameter format ep_token={Easy Passthrough Token}. In the Email Users message, that merge tag should be replaced with a unique token for the specific entry.

Sending Steps

1. Open Forms > Email Users.
2. Select the event registration form.
3. Choose the participant's Email field.
4. If the message should go only to one group, enable conditional logic, for example by event name or participation format.
5. Write a subject line that clearly ties the email to the event.
6. Add a short message and a link to the survey page with the parameter ep_token={Easy Passthrough Token}.
7. Insert an unsubscribe link if the message goes beyond a strictly operational notice.
8. Click Save Draft & Review Emails and open several previews.
9. Test the link from the preview using a sample entry.
10. Send the email after verifying the audience and delivery setup.

Result Verification

The workflow is successful if the test recipient receives the email, the link opens the correct follow-up form, the name and email fields are already filled in, and submitting the survey creates a new entry in the target form. If the fields are not prefilled, look for the cause in the Easy Passthrough setup, the token in the URL, field matching, or caching on the form page.

If the email does not arrive, do not immediately change the Email Users conditions. First verify whether the review was created, whether recipients exist, whether standard Gravity Forms notifications are being delivered, what errors appear in the SMTP logs, and whether the message landed in spam. That sequence separates an audience selection problem from a delivery problem much faster.

A Real-World Campaign Nuance

A follow-up message often feels like something you should send to "everyone who attended." But the form may include test entries, canceled registrations, participants who did not consent to further contact, or people who already completed the survey. For a clean process, add a field to the source form or entries that lets you exclude extra recipients. If no such field exists, build a clear condition before sending or use a separate reviewed form for the final audience.

Delivery, Limits, and Performance: Where the Plugin's Responsibility Ends

Email delivery in WordPress often fails not because the form or add-on is wrong. Gravity Forms hands the message to WordPress, WordPress sends it through wp_mail() or an SMTP plugin, and then the sender server, the domain's DNS records, and the recipient's mail system take over. Email Users sits at the beginning of that chain and cannot guarantee inbox delivery on its own.

That is why production mailings should use SMTP or a transactional email service from the start. Gravity Forms documentation points to Gravity SMTP and dedicated add-ons for Mailgun, Postmark, and SendGrid, along with the broader recommendation to use a dedicated email delivery service. WordPress.org plugins like Post SMTP and WP Mail SMTP solve a similar problem at the site level: they replace unreliable host-based delivery with a more controlled mail flow that includes logs and provider integrations.

Your first Email Users test should always go through the same mail setup you will use for the real send. If you tested with a local mail catcher and then send the actual campaign through a new SMTP configuration, the result is not truly verified. Test the exact From Email, domain, SMTP account, and audience you plan to use.

Email Count Limit

Email Users includes an official hook, gpeu_limit, which defines the maximum number of emails or entries allowed before sending is blocked. The documentation lists the default as 999. This is a safety mechanism related to delivery reliability and the risk of server or browser errors when processing too many entries.

Do not treat that limit as a recommendation to always send nearly a thousand messages at once. The real safe volume depends on your mail transport, hosting environment, provider limits, message size, and the quality of your address list. On weak hosting, even a few hundred messages can be problematic if they are sent through standard PHP mail. With a properly configured transactional provider, the limit may be higher, but it still needs to align with the provider's rules.

Concurrent Connections

Gravity Wiz's snippet library includes an example for gpeu_connection_threshold. It changes the number of simultaneous sending connections; the documented default is 5, and the sample increases it to 10. This is not a "speed boost that everyone should enable." Increasing it may make sending faster, but it also puts additional load on the server.

If the site runs on standard shared hosting, do not increase the threshold without a clear reason. If you are seeing timeouts with relatively small audiences, first check SMTP, logs, message size, plugin conflicts, and server limits. Increasing concurrency only makes sense after testing on staging or during a controlled window when you are prepared to roll the snippet back.

When It Is Better to Split the Send

If the audience is large or the conditions are complex, send by segments. For example, first "online attendees," then "in-person attendees," then "certificate pending." That makes it easier to verify the content, track errors, and avoid a sudden sending spike from a single domain. If your SMTP provider imposes a rate limit, segmentation also helps you avoid hitting it all at once.

For recurring sequences, delayed emails, and repeated reminders, it is better to look at Gravity Forms Notification Scheduler. That tool solves a different problem: sending a notification later, on a date, on a repeat schedule, or relative to a Date field. Email Users is more convenient when a person makes the decision manually and sends a message to a set of accumulated entries.

Common Email Users Problems and How to Diagnose Them

Email Users issues are easiest to troubleshoot when you stop thinking in terms of the generic message "it doesn't work" and instead identify the point of failure. Start by determining where the chain breaks: the menu is missing, the form cannot be selected, there are no recipients, the preview is wrong, the email is not sent, the email was sent but not delivered, or the recipient got multiple copies.

The Email Users Item Does Not Appear in the Forms Menu

Symptom: the plugin is activated, but the administrator or editor does not see the Email Users page. A possible cause is an inactive Perk, a Spellbook issue, or a missing gravityperks_gwemailusers capability for the user's role.

Check that Gravity Forms, Spellbook, and Email Users are all active. Then log in as the main administrator. If the menu appears, the problem is role-related. In your role management plugin, add the gravityperks_gwemailusers capability to the required role. If the menu does not appear even for the administrator, disable suspicious plugins on staging and check the server logs for errors.

The Required Form or Email Field Is Missing

Symptom: the interface opens, but the required form is not suitable for sending or the email field list is empty. In most cases, the form does not contain a real Email field, entries have not been created yet, or the administrator selected a similar-looking test form by mistake.

Open the form editor and make sure the email is stored in a field of type Email. Then open Entries and inspect actual submissions. If older data was collected in a text field, Email Users may not offer the expected selection. The safest fix is to update the form so future submissions use a proper Email field, and use older entries only after manual review.

Conditional Logic Selected the Wrong Recipients

Symptom: the number of emails in the review does not match expectations, or the preview shows entries from the wrong group. A likely cause is that the condition uses the wrong field, the saved entry values differ from the labels shown in the form, or the administrator mixed up similar options.

Compare the condition against the filters in Entries. If the rule depends on a text value, verify the exact spelling. For choice fields, make sure the value stored in the entry matches the value used in the condition. If the audience is sensitive, do not send until you have manually spot-checked several entries.

Merge Tags Did Not Resolve or Resolved as Empty

Symptom: the preview shows blank spots or raw technical tags instead of data. The usual cause is an incorrect tag, an empty field in the entry, or an attempt to use a field that does not exist in the selected form.

Use the merge tag picker in the interface rather than typing tags from memory. Check several entries, because one test entry may be complete while real entries are not. If the field is optional, write the message so that an empty value does not break the meaning. For example, instead of "Your selected package: X," use more neutral wording where the package is mentioned only when the data is reliably present.

The Email Is Marked as Sent but Never Arrives

Symptom: Email Users completes the send, but the recipient does not see the message. This is often a WordPress delivery problem rather than an Email Users problem. Gravity Forms troubleshooting recommends checking standard notifications, From Email, spaces and typos in addresses, routing, SMTP authentication, logs, and SPF/DKIM/DMARC DNS records.

First send a normal Gravity Forms notification to a test entry. If that message also fails, connect SMTP or a transactional provider and inspect the logs. If a normal notification arrives but Email Users does not, check the recipient count, message size, BCC, links, content, and any provider-side restrictions.

One Person Received Several Identical Emails

Symptom: one email address appears in multiple entries and receives several copies. That matches the documented default behavior: sending is based on entries, not on unique people. For event forms, this can be correct if one person registered multiple attendees. For a general announcement, it may be unnecessary.

The solution is to decide in advance what the mailing unit is: the entry or the unique email address. If you need a unique email address, use the official gpeu_send_to_duplicates hook and test it on staging. If multiple entries for the same address represent different purchases or registrations, do not disable duplicates without understanding the business logic.

The Preview Is Heavy or Sending Is Slow

Symptom: the review loads slowly, especially with a large number of entries and personalized messages. Gravity Wiz provides the gpeu_show_message_preview hook, which can disable message preview for large volumes to improve performance, as well as gpeu_limit and gpeu_connection_threshold to help control processing.

Do not start troubleshooting by increasing the limits. First reduce the audience size, simplify heavy HTML, check SMTP, and send a segment. If the problem repeats at higher volume, treat it as an infrastructure issue: sending service, rate limits, campaign segmentation, and possibly a move to a dedicated email platform.

Safe Extensions Through Official Hooks

Email Users includes a set of documented hooks, but that does not mean every site should start writing code immediately. Developer-level extensions are useful when the standard interface is already understood, the workflow is repeated, and the risk is clear. For this guide, one safe idea is enough: control duplicates or performance through official filters without modifying the plugin code.

All snippets should be stored outside a theme that may be updated or replaced. Use Code Snippets, a small site-specific plugin, or a deployment workflow if the site is maintained by a developer. Do not edit Gravity Forms, Gravity Perks, theme, or WordPress core files. After each snippet, test on staging or on a dedicated test form.

When to Use gpeu_send_to_duplicates

This hook fits a business rule like: "One address gets one email, even if it appears in multiple entries for the selected form." An example would be a general announcement to a participant base where repeat submissions should not generate repeat messages.

It is not appropriate when one email address legitimately represents multiple real participants. For example, a parent registers two children for different groups and should receive separate instructions for each entry. In that case, disabling duplicates could hide important information.

When Not to Increase Concurrent Connections

Increasing gpeu_connection_threshold can be tempting because it may speed up sending. But the official snippet explicitly warns about additional load. For most sites on standard hosting, it is more useful to make the flow reliable rather than faster: SMTP, a clean From Email, small segments, verified DNS records, and a simple message without heavy attachments.

If a developer does change the threshold, record the original value, the change date, the test form used, and the result. Rolling back should be as easy as disabling the snippet. Do not leave performance tweaks undocumented, because a few months later no one will remember why a mass send suddenly started putting pressure on the server.

Combined Workflows with Other Gravity Forms Solutions

Email Users is especially effective when it completes or extends an existing Gravity Forms workflow. It does not have to work alone. But combined workflows should have a clear separation of responsibility: one tool collects data, another passes data through, a third schedules the send, and a fourth handles delivery.

Email Users + Easy Passthrough

The combination of Email Users and Easy Passthrough is ideal for follow-up forms. Email Users sends the message to people listed in entries. Easy Passthrough injects data into the next form through a token. The boundary of responsibility is clear: Email Users handles audience selection and email sending, while Easy Passthrough handles data transfer between forms.

The risk of conflict is usually not between the Perks themselves, but rather around follow-up form page caching, incorrect field mapping, or a missing token. The verification step is to open the link from the preview and confirm that the fields are populated as expected.

Email Users + an SMTP Plugin

In this setup, Email Users is responsible for generating the messages, while the SMTP plugin or transactional provider is responsible for delivery. For production sites, this is almost a required pairing if emails need to reliably reach recipients. Use SMTP logs for verification: they will tell you whether WordPress handed the message off to the provider and what error, if any, the server returned.

Do not confuse a recipient selection issue with a delivery issue. If Email Users shows a correct preview but the SMTP logs report an authentication error, there is no point adjusting conditional logic. You need to fix the SMTP credentials, port, encryption, sender domain, or provider configuration.

Email Users + Notification Scheduler

Notification Scheduler is the right fit when the message should be sent automatically based on timing, delay, or a Date field value. Email Users is the better fit when a person manually selects the audience and sends a message based on accumulated entries. These tools are not mutually exclusive, but they should not be used for the exact same job at the same time.

If an event has a fixed sequence of reminders leading up to a date, Notification Scheduler is more convenient. If the organizer wants to send a one-time message after the event only to people who attended or only to those who selected a specific option, Email Users is more practical.

When Gravity Forms Email Users Is Worth Using on Your Site

Gravity Forms Email Users is a strong choice when you already use Gravity Forms, form entries represent a clear audience, the email needs to be sent manually and for a specific purpose, and you are not trying to build a long marketing automation sequence. The plugin is especially useful where communication is tied to a specific submission: registration, application, donation, ticket, survey, waiting list, or follow-up form.

Before rollout, verify four things: the form contains the correct Email field, the entries are clean enough to use, the administrator role has the gravityperks_gwemailusers capability, and WordPress sends mail through a reliable SMTP or transactional provider. Then set up a test send and verify the preview, links, unsubscribe behavior, and delivery logs.

If you need a fast one-time communication channel for people who have already submitted a form, you can get the Gravity Forms Email Users file and test it on a site copy or a test form. If your needs are closer to recurring newsletter campaigns, large audiences, automated sequences, and analytics, use Email Users only as a supporting tool and build the main mailing workflow on a specialized platform instead.

The best result comes not from the Send button, but from a verifiable process: a clear form, accurate entries, a carefully defined segment, a short useful message, preview before launch, and transparent delivery troubleshooting. In that setup, Email Users handles exactly the job it is meant to handle without trying to be something it is not.