WordPress conditions
Target visitors by the WordPress page they're on or the topics they've read. You'll find the page, post, category, tag, and favorite options, plus how missing data affects them.
You can target a specific WordPress page or post, or show an offer based on the topics a visitor has been reading.
What it checks
WordPress conditions check pages, posts, tags, categories, and favorites inferred from reading history. They need the WordPress integration to supply content IDs, tags, and categories for the visitor's pageviews.
A path containing /category/ isn't enough to establish a category. These conditions use WordPress data, not a guess from the URL.
When to use it
Use these conditions when you want to target WordPress content by its identity or topics rather than its URL.
For URL paths, domains, page counts, or session age, use Pages and visits conditions. For answers visitors explicitly gave you, use segment membership conditions.
Options
What to check
| To check… | Choose | Available values |
|---|---|---|
| The current page's WordPress page ID | Current page | WordPress pages |
| The current page's WordPress post ID | Current post | WordPress posts |
| Tags attached to the current post | Current post's tags | WordPress tags |
| Categories attached to the current post | Current post's category | WordPress categories |
| Highest-scoring tags in retained reading history | Favorite tag | WordPress tags |
| Highest-scoring categories in retained reading history | Favorite category | WordPress categories |
Pickers show content names and store their IDs. You can select multiple values. If you rename a page, tag, or category, its ID stays the same. Checking part of its title in a URL condition is a different comparison.
Each option starts with include any of and no selected values.
How to compare it
All six options offer these operators:
| Choose | When it matches |
|---|---|
| include any of | At least one actual content ID, tag, or category matches your selection. |
| don't include any of | None of the actual IDs, tags, or categories matches your selection. |
| matches any | At least one actual ID, tag, or category is available for that option. |
| doesn't match any | The actual list for that option is empty. |
Multiple selections are alternatives. Current post's category → include any of with Operations and Planning requires either category, not both. To require both, use two positive conditions in an All group.
matches any and doesn't match any check the actual data list, not your selections. Their answer doesn't depend on a comparison selection, even if the editor leaves the picker visible.
An empty selection fails include any of and passes don't include any of. It doesn't create a test that requires all selected categories.
Current pages, posts, and topics
WordPress distinguishes pages from posts. Current page checks a page ID. Current post checks a post ID. A regular post doesn't become a page match just because it appears on a webpage.
Both conditions use WordPress metadata on the current tracked pageview. If that metadata or the relevant ID is missing, the list is empty.
The tag and category options read the current post's taxonomy term IDs. They don't check all posts displayed in an archive, search listing, or category listing.
A post can have more than one category, even though Current post's category uses the singular. include any of needs only one selected category to match.
Favorites
Favorites come from retained pageviews with WordPress metadata. Each qualifying post view contributes to the scores of its tags and categories. Repeat views contribute again, so this isn't a count of unique posts.
RightMessage weights the retained history instead of counting all views equally or choosing the most recently viewed category. Earlier entries in chronological history receive greater weight than later entries. The latest post doesn't get extra weight.
If several tags or categories tie for the highest score, all of them count as favorites. include any of matches when any selected tag or category is among those favorites.
Examples
If WorkForge (opens in a new tab) used WordPress, it could use Current page → include any of with Pricing to target that WordPress page. For an offer that also needs to appear on non-WordPress pages, a current-path condition may fit better.
Favorite category → include any of with Planning could personalize an offer based on reading history. It wouldn't mean the visitor explicitly chose Planning or that Planning is their only favorite.
Things to know
Missing tags, categories, or post data
A missing tag or category collection counts as empty. That means don't include any of with Operations can match a page with no WordPress post metadata at all.
To require a known post as well as a negative category or tag comparison, add Current post → matches any to the same All group. This requires an actual post ID.
If a rule unexpectedly matches pages without WordPress content, check its negative or presence operator before assuming a category assignment is wrong. Missing integration data isn't a confirmed check of a post's categories.
No reading history
Without qualifying WordPress history, the favorite list is empty. include any of and matches any are false. don't include any of and doesn't match any are true.
Favorites have no duration selector. Changing the operator can't make the condition mean "favorite in the last seven days." A separate time-based condition can add a requirement, but it won't change how RightMessage calculates the favorite.
How long the data lasts
Current-content conditions follow the current pageview's WordPress metadata. Favorites follow the browser's retained pageview history. Neither reads a WordPress account's lifetime browsing history from the server.
These conditions set no fixed expiration for favorite data. Browser storage limits can remove older pageviews. Clearing browser data removes the history available for the calculation. Another browser, device, or origin may have different history.