GamiPress Conditional Emails - WordPress Plugin

How to Configure GamiPress Conditional Emails for Smarter Achievement Emails

GamiPress Conditional Emails is not meant for general email campaigns, and it is not a replacement for your email service. Its job is more specific: send an email the moment something important happens in GamiPress - when a points balance is reached, an achievement is unlocked, an entire achievement type is completed, or a rank is earned. In this guide, we will break down how to turn those events into clean, purposeful emails, how to avoid overwhelming users with repeat notifications, and how to verify that the email was actually sent.

This guide is written for WordPress site owners, instructional designers at online schools, community administrators, store managers running a loyalty program, and developers maintaining GamiPress on a live project. We will move from preparation and installation to configuring templates, conditions, send limits, test emails, a real-world use case, and troubleshooting. We will not repeat the general product pitch - that is already covered earlier on the page.

The core idea is simple: the email should be a result of a specific gamification event, not a random greeting. That is why every example below follows the same chain: the user completes an action, GamiPress records points, an achievement, or a rank, Conditional Emails selects the matching condition, inserts the tags, and sends the message through the WordPress mail system.

What Problem Conditional Emails Solves in a Rewards System

In a standard gamification setup, email is often treated as a side effect: the user earns a reward, the site sends a notification, and that is the end of it. Conditional Emails makes this layer controllable. The administrator decides which event should trigger the email, what text the user will see, which dynamic data should appear in the subject and body, how many times the email can be sent in total, and how many times it can be sent to a single user.

The official documentation describes a dedicated GamiPress > Conditional Emails screen where conditional emails are stored, along with an edit screen where the Email Configuration, Condition Configuration, and Details blocks are configured. This matters because the product does not create a visual block on the site or add a public form. It works inside the admin area and through the WordPress email channel.

The practical value becomes clear on projects where rewards should not go unnoticed. A student finishes all assignments in a section, a community member reaches the required points balance, a customer moves up to a new loyalty tier, or a contributor earns a badge for activity. In each case, the email can explain what happened, what to do next, and where to view the result on the site.

A good conditional email does more than congratulate. It connects the event to a next step: move on to the next lesson, open the bonuses page, check the profile, use the points that were earned, view the new rank, or return to the account dashboard. That is why configuration should start not with the email copy, but with a simple question: what user behavior do you want to support after the event?

How Conditional Emails Differs from Standard GamiPress Email Settings

GamiPress includes general email settings under GamiPress > Settings > Emails: the template, logo, sender name, sender address, and footer text. Those settings affect the overall look and sender identity of GamiPress emails. Conditional Emails operates one level higher in the scenario logic: it decides when to send a specific email and what conditional content to insert.

If you need to change the base template for all emails, it makes more sense to start with the general email settings. If you need to send a separate email only when a specific points balance or rank is reached, you need Conditional Emails. If you need different templates for different reward types, GamiPress Emails By Type is worth reviewing as well. If you need to send emails to administrators, GamiPress Admin Emails or the free Conditional Emails Recipients add-on may be a better fit, if it matches your use case.

Where the Product Is Especially Useful

Conditional emails work especially well when the reward itself does not clearly explain the next step. A user may see a badge in their profile but not realize they unlocked a new module, gained access to a discount, or moved closer to the next level. The email closes that gap: it turns an internal GamiPress event into a clear user action.

• In an online school, the email can suggest moving to the next course block after the user earns an achievement.
• In a community, the email can congratulate the user on a new rank and explain what it represents.
• In a points-based store, the email can remind the user about their accumulated balance and direct them to the bonuses page.
• In a content project, the email can highlight a sequence of actions such as comments, posts, completed tasks, or participation in discussions.

Conditional emails should not be used as a mass mailing tool for your entire user base. The product is strongest when it reacts to targeted GamiPress events tied to a user's personal progress.

Who the Plugin Is For and When It May Be Unnecessary

GamiPress Conditional Emails is useful for anyone who already has a clear points, achievements, or ranks system in place with GamiPress. If the site does not have meaningful rewards configured, the product will have nothing to react to. That is why it makes more sense to treat it not as the first step in gamification, but as a communication layer on top of rules that are already working.

Good-Fit Projects

The best candidates are sites where user progress matters and should be acknowledged. That can include learning platforms, private communities, loyalty clubs, challenge-based sites, contributor directories, gamified stores, internal portals, and projects built on BuddyPress, BuddyBoss, LearnDash, LifterLMS, WooCommerce, or other GamiPress integrations. Conditional Emails itself does not replace those integrations, but it can send emails based on events GamiPress is already receiving.

The plugin also works well for editors who do not want to write code for every email. The official documentation confirms fields for subject, content, conditions, status, date, total send limit, and per-user send limit. That is enough to cover a large number of practical scenarios without modifying the theme or plugin.

When a Different Approach Makes More Sense

This product may be unnecessary if you need to build long marketing sequences, segment subscribers by many outside attributes, track opens and clicks, send regular digests, or manage newsletter consent the way a full email platform does. For those tasks, it is better to use a mailing service, CRM, or automation tool, and leave Conditional Emails for GamiPress events.

It also will not solve poor email deliverability. If WordPress is not sending email, messages land in spam, or the sender address does not match the domain, you need to fix that first with a proper SMTP plugin or email service. Conditional Emails builds the message and triggers sending through WordPress, but domain reputation, SPF, DKIM, DMARC, and hosting limits are still your responsibility.

What to Check Before Installation and Activation

Before installing conditional emails, make sure the core GamiPress system is working predictably. An email will only be correct if the event itself is being triggered correctly. If points are awarded inconsistently, an achievement is given to the wrong user, or a rank is updated manually without a clear rule, the email will only add to the confusion.

Core Dependencies

First, confirm that the main GamiPress plugin is installed and active. The WordPress.org page for GamiPress describes three key entities: points, achievements, and ranks, along with built-in blocks, shortcodes, widgets, logs, and email settings. Conditional Emails is built on top of those entities, so without them the scenario has no foundation.

If the add-on was obtained as a premium extension, install it the standard WordPress plugin way: through Plugins > Add New > Upload Plugin or by uploading the archive to wp-content/plugins/ and then activating it in the admin area. There is no need to describe or work around license activation here; for this guide, what matters is configuring the features and checking the result after the administrator already has the file.

Checking the Email Infrastructure

For any WordPress email, sender settings are critical. In GamiPress, the Settings > Emails tab includes the global template, logo, From Name, From Address, and Footer Text. Before creating conditional emails, verify that the sender address belongs to your site domain or is properly configured in your SMTP service. Otherwise, the user may never see the email even if Conditional Emails triggers correctly.

The practical minimum before launch:

• Send a regular WordPress test email or an email from another plugin to make sure mail is leaving the site at all.
• Check that the sender mailbox does not look like a temporary hosting address.
• Make sure there is no plugin on the site that blocks or overrides email sending without your knowledge.
• Prepare a test user with a real email address you can access.
• Create a test achievement, points type, or rank so you do not debug email behavior on a live audience.

The most common early mistake is polishing the email copy before checking the event itself and deliverability. First prove that the GamiPress event fires, then test the email.

Permissions and Editorial Responsibility

A conditional email can include personal data, profile links, points details, and personalized tags. For that reason, access to these settings should be limited to administrators or responsible editors. If multiple managers work on the site, agree on a naming convention, for example starting the email name with the event type and audience. That makes it easier to avoid duplicates and quickly locate the email that did not behave as expected.

Installation and the First Check in the Admin Area

After activating the add-on, a conditional emails section should appear in the GamiPress menu. The documentation describes the path as GamiPress > Conditional Emails. On this screen, you can see the list of created emails with their name, status, and date. If the section does not appear, first verify that both the main GamiPress plugin and the add-on are active on the Plugins page.

A Safe First Launch

Your first email should be created for a test scenario, not for a live reward with real users attached to it. That way, you can see how the subject, content, tags, and limits behave without risking dozens of emails going out to real people.

1. Open GamiPress > Conditional Emails.
2. Create a new conditional email or open a draft if one has already been prepared.
3. In the Email Configuration block, fill in the email subject and content.
4. In the Condition Configuration block, choose a condition that is easy for a test user to reproduce.
5. In the Details block, leave the status inactive until the content and condition have been checked.
6. Save the changes with Save Changes.
7. Use the test email action if it is available on the save screen.

The documentation highlights an important detail: the test email is sent to the current administrator account's email address, and you need to save your changes before testing so the message includes the latest version of the settings. It is a small detail, but it saves a lot of time during troubleshooting.

What You Should Have After Installation

The correct result at this stage is not sending an email to all users, but having a controlled draft in place. You should understand where the email list lives, where the subject is edited, where the condition is selected, where limits are set, and where the test email is sent. Once those points are clear, you can move on to full configuration.

Configuring the Email: Subject, Content, Tags, and the Global Template

The Email Configuration block controls what the user will see. It includes the subject and content. The key is not to turn the email into a decorative congratulations message with no practical value. Within a few seconds, the user should understand what happened, why they received the email, and what to do next.

How to Write the Email Subject

The subject should be short, specific, and clearly tied to the reward. If you use a tag in the subject, make sure that tag is supported for the selected event. The official available tags documentation confirms that tags work in both the subject and email content, but the available tag set depends on GamiPress types and their slugs. That means a generic subject with any arbitrary tag may not resolve the way you expect.

Good subject line options:

• You earned a new badge on the site.
• Your points balance has reached the required level.
• The next rank in the participation program is now unlocked.
• All tasks in this section are complete - check your next step.

Weak subject lines usually suffer from one of three problems: they are too vague, too promotional, or they do not explain the event. Avoid writing just "Congratulations!" if the user has many different activities on the site. Give them a clear reference point instead.

Email Content and GamiPress Tags

In the email body, use a short structure: greeting, event, what it means for the user, next step, and a link to the relevant page. If you add dynamic tags, leave some plain text around them so the message still makes sense even if a value fails to populate. For example, do not build an email out of tags alone.

The Conditional Emails documentation states that email content executes shortcodes, and tags can be used as shortcode attribute values. The documentation example shows an achievement tag paired with user_id:

[gamipress_achievement id="{quest_id}" user_id="{user_id}"]

Use that mechanism carefully. If the email should stay lightweight and render well across different mail clients, do not overload it with complex markup. A shortcode in an email makes sense when it genuinely helps display a reward or link, but detailed progress information is usually better left on the profile page or inside the user account area.

A Starter Email Mini-Template

For a first scenario, you can use a simple structure without overpromising:

Hello!

You completed the condition on the site and earned a new reward.

Check your profile to see your current progress and the next available step:
https://example.com/profile/

If you received this email by mistake, just reply to this message and contact the site administrator.

After testing, replace the generic lines with the actual tags and links for your site. Do not include sensitive data in the email if it can be shown more safely after the user logs in to their account.

Overall Style Through GamiPress Emails Settings

If the email looks off, check not only the specific Conditional Email but also the general GamiPress Emails Settings. That is where the email template, logo, sender name, sender address, and footer are defined. This is the shared layer for GamiPress emails, so a problem with the logo, gray background, sender address, or template may have nothing to do with the conditional email itself.

A practical setup order: first clean up the global GamiPress email template, then create one conditional email, then send a test, and only then enable real conditions. That makes it much easier to tell whether the problem is in the base email template or in the specific condition.

Send Conditions: Points, Achievements, Achievement Types, and Ranks

The most important part of the product is Condition Configuration. It defines the event the conditional email will react to. The documentation lists these conditions: Reach a points balance, Unlock a specific achievement, Unlock any achievement of type, Unlock all achievements of type, and Reach a specific rank. Once a condition is selected, extra fields may appear, such as the amount and points type for a balance-based condition.

These conditions are not interchangeable. Some are best for targeted congratulations, some for program milestones, and others for major progress checkpoints. Choosing the wrong one leads to emails firing too often, too late, or not at all.

Using a Points Balance as the Trigger

Reach a points balance is useful when you need to react to accumulation. For example, a user earns 500 bonus points, reaches the threshold for access to a gated section, or gets close to redeeming points for a reward. It is important to specify the points type if your site uses more than one. In GamiPress, you can create different points types such as Credits, Gems, or Coins, and the tag documentation notes that tags are based on the slug of the corresponding type.

For balance-based conditions, the per-user limit is especially important. If the user can cross the threshold multiple times because points are deducted and re-awarded, an email without a restriction may be sent again and again. In most threshold scenarios, it is safer to set Maximum Sends Per User to 1 if the email should only be sent once.

A Specific Achievement

Unlock a specific achievement is the right fit when the email is about one exact reward: a course completed, a certificate unlocked, a sequence of actions finished, or an important badge earned. This is the clearest scenario for the user because the email is tied to one event. The message can also be more specific: what the achievement is, why it matters, and what the next step should be.

This condition is also easy to test: create a test achievement, manually award it to a test user or perform the action that unlocks it, and then check the email. If the email does not arrive, it is much easier to inspect one reward than an entire achievement type.

Any Achievement or All Achievements of a Type

Unlock any achievement of type and Unlock all achievements of type are designed for broader scenarios. The first reacts to any achievement inside a type, while the second reacts to completing the full set of achievements in that type. For example, an achievement type like "Module Tasks" may include several achievements, and an email after all of them are completed makes sense as a final message.

The key here is not to confuse user excitement with noise. If an email is sent for any achievement in a type, and that type contains dozens of small rewards, the user may end up receiving too many emails. In cases like that, it may be better to use an on-site notification through Conditional Notifications or send a single summary email after all achievements in the type are completed.

A Rank as a Strong Milestone

Reach a specific rank works well for major transitions: a new member level, a new club status, or advancement in a learning program. An email tied to a rank usually feels more significant than an email about a small action, so it can be a bit longer and explain the benefits of the new level. But do not promise features your GamiPress setup or site does not actually provide. If the rank is symbolic, say so plainly: the new status reflects progress, but it does not necessarily unlock access.

Limits, Status, and Date: How to Avoid Sending Extra Emails

The Details block may look technical, but it is exactly what protects you from unwanted sends. It includes the email status, creation date, maximum total sends, and maximum sends per user. The documentation highlights two important rules: only active conditional emails are sent, and the first email will be sent after the selected date.

Email Status

An active status means the email can participate in sending. An inactive status is useful for drafts, tests, and temporary shutdowns. Do not delete a working email immediately if you need to stop sending. First switch it to inactive, verify that new events no longer trigger it, and only then decide whether the rule should be deleted.

For editorial discipline, it helps to add a scenario marker in the email name: "Points 500 - profile", "Expert rank - post-upgrade email", or "All module achievements - next lesson". That is not a required product feature, just a safe organizational habit.

Date as the Start Boundary

The date field matters if you are creating a conditional email on a site that already has existing users and accumulated rewards. The documentation says the first email will be sent after the selected date. The practical takeaway is simple: do not use an old date unless you clearly understand how your site handles events that were already completed in the past. For a new scenario, it is safer to set a current launch date and test it with a dedicated user.

Maximum Sends and Maximum Sends Per User

Maximum Sends limits the total number of times the email can be sent. Maximum Sends Per User limits how many times it can be sent to the same person. In the documentation, a value of 0 means there is no maximum. That is convenient for repeatable events, but risky for emails that are meant to mark a milestone.

Practical values:

• For an email about a first achievement, use a per-user limit of 1.
• For an email about a new rank, use a per-user limit of 1 if the rank cannot be reset and earned again.
• For an email about a points threshold, use a limit of 1 if the message should mark the first time the threshold is reached.
• For a pre-launch test email, you can temporarily limit the total sends so you do not send more messages than planned.

If you are unsure, start with a stricter limit and loosen it only after the logic has been tested. You cannot take back an unnecessary email once it reaches a user, but you can usually allow repeat sends later if needed.

Practical Scenario: Email After Reaching a Points Threshold

Let us look at a working scenario: the site uses GamiPress for an activity program. The user earns points for completing lessons, leaving comments, or participating in assignments. Once they reach the required balance, the administrator wants to send an email explaining the next step. This is not a marketing sequence, but a personal progress notification triggered by a real event.

Goal

You need to send a single email to a user who reaches a selected threshold for a specific points type for the first time. The email should congratulate them, explain what the threshold means, and link to the profile or bonuses page. Crossing the same threshold again should not start a stream of repeat emails.

Preparation

Before configuring anything, verify three things. First, the points type already exists and is being awarded correctly. Second, you have a test user with a known email address. Third, the general GamiPress email settings are filled out and WordPress test sending works. If even one of those pieces is missing, Conditional Emails will be difficult to debug.

Configuration Steps

1. Open GamiPress > Conditional Emails and create a new email.
2. In the email name, specify the internal scenario, for example "Activity Points - First Threshold".
3. In Email Configuration, write a subject tied to the points threshold.
4. In the email content, explain that the user has reached the required balance and add a link to the page where they can see the result.
5. In Condition Configuration, select Reach a points balance.
6. Enter the required points type and amount if those fields appear after selecting the condition.
7. In Details, keep the current launch date and set Maximum Sends Per User to 1.
8. Save the changes with Save Changes.
9. Send a test email to the current administrator to verify the copy and tag substitutions.
10. Switch the email to active only after the test succeeds.

Checking the Result

After enabling the rule, trigger the event with a test user. If you are adjusting the balance manually, make sure the method you use actually triggers the intended GamiPress logic. Then check the user's inbox, spam folder, SMTP plugin log if one is installed, and the GamiPress logs if the site uses an activity log.

Expected result: the user receives one email, there are no unresolved tags in it, the link goes to the correct page, and crossing the same threshold again does not send a second email if the per-user limit is set to 1.

A Nuance with Re-Awarded Points

If points can be deducted and then awarded again, the user may reach the threshold more than once. That can be useful in some gamified systems, but it is a poor fit for a one-time congratulations message. That is why threshold emails almost always need a per-user limit. If you intentionally want a repeatable email, state that clearly in the scenario design and make sure it does not come across as spam.

Practical Use Ideas for Different Types of Sites

The product's value is easier to understand through real working situations than through a feature list. Below are ideas based on confirmed Conditional Emails conditions and common GamiPress scenarios. You can adapt them to your site, but do not promise bonuses or access unless they are actually configured by separate rules in your project.

Online School: an Email After Completing a Set of Achievements

If each lesson or assignment grants an achievement of the same type, Unlock all achievements of type can be used as a module completion email. There is no need to recap the entire course in the message. It is better to say the block is complete, link to the next module, and remind the user where to check their progress.

Check: the test student should receive the email only after completing the full set of achievements, not after the first task. If the email arrives too early, either the wrong condition type was selected or the achievements are grouped into types differently than expected.

Community: a New Rank as a Reason to Explain Status

For a forum, club, or private community, Reach a specific rank helps explain what a new status means. The email can point the user to relevant pages, remind them of participation rules, and show where the rank appears in the profile. If the rank does not unlock new permissions, do not claim that it does. It is better to describe it honestly as a marker of activity.

Store or Loyalty Program: a Points Threshold Without Aggressive Emailing

If GamiPress awards points for purchases or site activity, an email tied to a points threshold can direct the user to the bonuses page. But it is important not to turn every point award into an email. For a store, a better approach is to send messages only for major milestones: the first meaningful threshold, a new level, or an achievement connected to the loyalty program.

Content Project: a Gentle Return to the Next Action

On a site built around assignments, articles, or challenges, an email triggered by a specific achievement can guide the user toward the next task. For example, after the first published comment, the email can explain where to view the profile and which actions lead to the next reward. This works only if the path is truly configured in GamiPress and does not read like an empty motivational phrase.

Checking the Result After Launch

Once a conditional email is enabled, it is important to verify not just delivery, but the entire user path. A successful send means nothing if the email leads to a restricted page, contains an empty tag, or arrives after the wrong event.

The Verification Chain

Use a simple verification chain: event, GamiPress record, email condition, WordPress send, user receipt, link click. If something breaks, inspect the chain from left to right. Do not start by rewriting the email copy if the GamiPress event itself never fired.

• Event: The test user completed the action that should award points, an achievement, or a rank.
• GamiPress: The profile, log, or admin area shows that the reward was actually granted.
• Conditional Emails: The conditional email is active, the date does not block the launch, and the limits have not been exhausted.
• WordPress email: The SMTP plugin or mail log shows a send attempt.
• Inbox: The email arrived, did not land in spam, the subject is clear, and the tags were resolved.
• Result: The link takes the user to the place where they can see the next step or their progress.

How to Check Tags

Tags depend on GamiPress types and slugs. The documentation says that tags related to types are added automatically and are based on the slug of the corresponding type, for example for a points type or achievement type. That is why, after changing a slug, an achievement type, or the structure of your rewards, you should always send a fresh test email.

If the email still contains a string like {example_tag}, that is a sign the tag is not supported in that context, was entered incorrectly, or does not belong to the selected condition. Do not hide that problem with polished copy. It is better to remove the tag, use a different confirmed tag, or move the detailed information to the profile page.

When to Enable It for a Live Audience

Enable the email for real users only after three successful checks: the administrator received the test email, the test user triggered the event and received the email, and a repeat event did not break the send limits. If the audience is large, launch one scenario at a time. That makes it much easier to find the cause if support starts receiving complaints.

Limitations and Safe Improvements Without Editing Core Files

Public sources did not provide confirmation of dedicated public hooks specifically for GamiPress Conditional Emails that would be safe to include in this guide as PHP snippets. That is why the article does not contain invented code. But there are still several improvements you can make without modifying the WordPress core, GamiPress, or the add-on itself.

Improve Deliverability Through the Standard Mail Layer

Use an SMTP plugin or email service that routes WordPress mail through a verified domain. This is not a Conditional Emails-specific feature, but it is critical to the outcome. After setup, send one test email from GamiPress and another from the SMTP plugin to confirm both channels go through the same sender.

Keep Emails Short and Easy to Validate

Do not turn the email into a full account page. It is enough to explain the event and include a safe link to the page where the user can see the details after signing in. That lowers the risk of broken tags and helps avoid exposing unnecessary information in the mail client.

Use Internal Email Names as Technical Documentation

The conditional email name is visible to the administrator, so it can double as short documentation: "Rank - Expert - one-time", "Points - 500 - profile", or "All module achievements - next lesson". That helps with maintenance and reduces the risk of duplicate rules.

Retest Emails After Changes to the GamiPress Structure

If the points type slug, achievement type, achievement set, or rank logic changes, retest every email that relies on the related tags and conditions. The tag documentation directly ties some tags to type slugs, so structural changes can affect substitutions.

When GamiPress Conditional Emails Is the Right Choice

GamiPress Conditional Emails is worth using when your site already has a clear points, achievements, or ranks system and users need timely explanations of their progress. The product is especially strong for one-time milestones: a new rank, a first meaningful points balance, a specific achievement, or completion of an achievement set. In those scenarios, the email helps the user understand the value of the reward instead of missing it.

Before launch, check the basic GamiPress email settings, WordPress mail delivery, the structure of your points and achievement types, send limits, and the test scenario. If everything works with a test user, you can download the latest version of GamiPress Conditional Emails and roll it out on the live site one rule at a time.

If you need a full email marketing system, an external CRM, complex automation chains, or emails to administrators, do not try to stretch this add-on beyond its purpose. In those cases, a neighboring solution is the better choice, and Conditional Emails should be reserved for what it does best - conditional emails triggered by GamiPress events.