Increase XenForo engagement with stock hooks, not another add-on

Engagement is not a reaction count. A member who hearts every announcement and never posts again is a spectator. The number that matters is a second session in seven days, then a second post that is not “thanks.” XenForo 2.3 already ships the hooks that create those two events: a first screen that shows what moved, a watch that pings when it moves again, a thread type that asks for an answer instead of a vibe, a notice that asks for one action, and a ladder that changes what the username looks like after they actually participated.

People buy engagement add-ons because those hooks are off, unexplained, or pointing at the wrong rooms. This is the stock stack — not the 30-day onboarding calendar, not a magazine homepage, not ranks-as-a-product. Trophies here are a light loop. This is the ACP work the calendar points at.

What you are actually trying to raise

Three different jobs answer to the word “engagement.” Mix them and you will install the wrong thing.

Job	The member does	Stock hook	Fake win
Return	Opens the site again without a campaign email	What’s New, watched forums/threads, activity summary / alerts	A notice that says “we missed you”
Reply	Leaves a post someone else can answer	Question / poll / suggestion types, staff threads a stranger can enter, watches on the rooms that move	A contest that produces one-line entries
Recognition	Sees that the reply counted	Reactions, reaction score, trophies, title ladder, a promotion that adds a banner	A 40-rung rank plugin nobody believes

Measure the first two. Recognition is fuel, not the destination. If first posts are fine and second sessions are not, the problem is the first screen and watches — not the registration form. The onboarding article already said that. Here you fix the machinery.

Do not start by adding a points shop. A shop rewards people who already post. Dead boards have an empty hallway, a forum list that looks the same every morning, and a welcome thread staff stopped answering in 2023.

The first screen is the return visit

A member who has to hunt for “what changed since Tuesday” will not hunt twice. XenForo gives you three honest first screens. Pick one. The rest of this article assumes you picked.

Forum list. Default. Good when the node tree is short and every category still moves. Bad when the tree is a junk drawer: the eye lands on Archive / Off-topic / Staff, not on the two rooms that had replies today.

New posts as the Forums default page. Returning members live here. The list is “what moved,” not “here is every container we ever created.” Pair it with a What’s new tab you do not hide. The portal article already warned you: widgets assigned to Forum list positions vanish from the first screen when you flip this option. Move them, or you will think the board died.

A decided portal. Index page route at Setup → Options → Basic board information, a page node or a dressed forum list, one curated strip, one “what moved” feed. That is a first-screen job. It is not engagement by itself. An empty Featured widget and a Members online block that says “2 users” is anti-engagement.

Guests and new Registered accounts need a different first sentence than your regulars. Regulars want unread. New people want “start here” and one thread they can answer without lore. If those two jobs share one screen, give regulars What’s New and give new people a notice or a pinned thread — do not make both of them scan 40 nodes.

Open three sessions after you change the first screen: guest, a brand-new Registered account, and your admin. If the three stories disagree, you are not done. The usual bug is a Featured hole (you featured a private-node thread) or a New posts list that is all staff chatter the guest cannot open.

Watches are the actual ping

A watch is a promise: “tell me when this moves.” Alerts, emails, and (if you enabled them) push notifications are how XenForo keeps that promise. Engagement add-ons that invent a second notification system on top of watches are solving a copy problem with PHP.

Stock behaviour that actually matters:

• Members can watch a thread (new replies) or a forum (new threads). Forum watches are how regulars stay in a room without opening every title.
• Default watch settings live on the account. If your welcome mail never mentions watches, you trained people to refresh the forum list like it is 2006.
• Email only works if mail leaves the server. Fix SPF/DKIM before you write more drip copy. The onboarding article already said this; it is still the number-one silent failure.
• Do not auto-watch every new member onto every forum. That is how you get “unsubscribe from this site” on day two. Auto-watch the one room they joined for — the game they play, the product they own — and say so in the welcome thread.

Staff should watch the rooms they claim to moderate. An unanswered first post teaches the next first poster that the room is a museum. A moderator template (“Welcome, we moved this to X, here is a related thread”) is better than a like and silence.

Watches amplify movement. If nothing moves, they amplify silence. Create the movement in the next section, then ask people to watch it.

Thread types that ask for a reply

Since 2.2, a forum is not only a bag of discussions. XenForo ships discussion, poll, article, question, and suggestion types. Each type changes what “participating” means. Use the type that matches the job. A mixed-type forum that allows everything is how a support question drowns under a 40-reply argument.

The official manual is explicit about the containers:

Type	What the first post is	What a reply is	Where it may live
Discussion	A conversation starter	More conversation, last-post order	Discussion forum or mixed-type
Poll	A multiple-choice question plus a thread	Votes on the poll, plus optional chatter	Same as discussion
Question	The question, pinned at the top of every page	Answers. One can be the solution	Question forum or mixed-type
Article	A long artefact (higher character and embed limits)	Comments. Later pages show a compressed article	Article forum or mixed-type
Suggestion	An idea with up/down votes	Debate under a vote score sort	Suggestion forum only

That last row is a hard limit. Suggestion threads may only be posted in dedicated suggestion forums. The listing sorts by vote score, not last reply. Filters exist for popular, new, your suggestions, your votes. Do not try to sneak a suggestion into a mixed discussion forum. The node editor will not let you, and even if an add-on did, you would break the sort that makes the type work.

Questions — the highest-leverage type most boards ignore

A question thread stays unsolved until the author (if permitted) or a moderator picks a solution. The solution then rides at the top of every page with the question. Users with vote permission can rank answers. A dedicated question forum adds filters: Unsolved, Your questions, Your answers. Solved threads get an icon in the list.

That is a reason to come back that a discussion does not have. “Did anyone answer me?” is a hook. “Is this still unsolved?” is a staff queue.

Use a question forum for support, lore questions, “which setting do I flip,” anything with a correct-enough answer. Do not convert the main hangout into questions. People who wanted to ramble will resent the solution chrome, and you will mark “I agree” as the answer because it has the most votes.

Staff should close the loop. An unsolved queue that is 200 threads deep tells the next asker that asking is pointless. If you cannot staff solutions, do not enable the type.

Polls — one decision, not a decoration

A poll is a discussion thread with a multiple-choice question attached. It works when the choice is real: next event day, which map, which rule to drop. It fails when staff post a weekly “how is your Monday” poll. That is a banner, not a decision. Members learn to ignore the chrome.

Cap the options. Announce what you will do with the result. Then do it. An unanswered official poll is worse than no poll.

Suggestions — a backlog, not a popularity contest you will ignore

Suggestion forums sort by vote. That is useful when you will actually ship or reject the top of the list. It is poison when staff never reply and the same three regulars downvote everything new.

If you open a suggestion forum, publish a monthly “what we will / will not do” thread. Unanswered official threads train people to ignore staff. The onboarding article said that about feedback; it is louder here because the vote number looks like a promise.

Articles — comments, not conversation

Articles are how you publish. They are a weak engagement engine on their own. Replies are comments under a long first post. Use them for patch notes and guides, then link them from a discussion or question where people can argue. Do not expect a magazine listing to produce the second post.

Do not convert a busy discussion forum into an article forum because you liked the masonry preview. Staff will keep hitting Discussion in a mixed forum, and you will feature a 40-reply argument because it had a pretty image. The portal article already walked the cover-image and Preview vs Expanded choice. Do that work there.

Moving threads

The manual has a dedicated caution: when you move a thread between forums, special behaviours have to survive at the destination. A question moved into a discussion-only forum, or a suggestion yanked out of its dedicated forum, is how you lose the solution chrome or the vote sort. Read the thread-type tools page before you “just move it.” Prefer prefixes and a split over a type change you cannot reverse cleanly.

Notices that ask for one action

Communication > Notices broadcasts a title and HTML message. You may use {name} for the viewer’s username, show their avatar or a custom image, pick a display style (or your own CSS class), and hide the notice below a screen-width breakpoint.

Four types. The type is the priority, not the decoration:

• Block — under the main nav, stays until dismissed. For the one thing you need them to do this week.
• Scrolling — several notices cycle horizontally. Only scrolls if more than one scrolling notice is visible. Easy to turn into a junk ticker.
• Floating — bottom-right, less intrusive. Can auto-dismiss after it fades. One-shot, non-critical.
• Fixed — full width, stuck to the bottom, covers content. Treat it as an emergency bar.

Dismissable notices can be closed. Users can review dismissed notices in their account. If every visit starts with three Block notices they already dismissed last month, you taught banner blindness.

Criteria are the point. Notices share XenForo’s criteria system with trophies and promotions: user criteria (guest, group, messages, avatar, registration age) and page / time criteria (where they are, how they arrived). Official examples: show only to guests (User is a guest); show to people who arrived from a search engine. The developer manual’s trophy walkthrough uses the same criteria UI to target “likes on a single message ≥ 5.” You can do the same for a notice that says “you just got your fifth like — watch this forum so you see the next reply.”

Good notices, 2026 edition:

• Guest, first screen: one sentence, one button. “This board is for X. Register to post in Y.”
• New Registered, message count 0: “Introduce yourself in this thread” plus a watch hint.
• Registered, no avatar, after day three: one Floating notice. Not a Block. Avatar nag is not a crisis.
• Search-engine landing on a deep thread: “There are 12 forums. Start here.”

Bad notices: a scrolling stack of Discord, donate, merch, and “follow us.” A Fixed bar for a sale that lasted six weeks. A Block that only staff see because the criterion is “user is in Administrative.”

One live Block notice per audience. If you cannot name the audience and the single action, do not save the notice.

Reactions are a cheap loop. Score is a criterion.

Content > Reactions is the manager. Each reaction has a title, text colour, graphic, display order, and a reaction score: positive, neutral, negative, or a custom number. Like is +1. Ten likes and nothing else is a score of 10.

The manual’s warning is the one boards ignore. Sad and angry ship as neutral. An angry reaction on a post about a server outage is empathy, not a penalty. Negative scores get used as a pile-on. If you add a “disagree” or “trash” reaction, leave the score at 0 unless you have a written moderation rule for score bombing.

Reaction score is a public counter. Admins can view and edit it under the user’s User details → Counters, next to message count and trophy points. That same score is a promotion criterion: the official permissions manual’s example is “add users to a Helpful members group when their reaction score exceeds 100.” That is a ladder. It is not a whitelist. The whitelist article already told you not to point a human gate at a score threshold.

What reactions do for engagement:

• They let lurkers participate without writing a sentence. That is real, and it is small. Do not confuse it with a reply.
• They give the author a reason to open the site again. A first like on a first post is worth more than a trophy named “Newbie.”
• They feed promotions and trophies. That is the only reason to care about the score as an admin.

What they do not do: replace a staff reply. A like on a support question that stays unsolved is a shrug. Prefer the question type and a solution.

Keep the default set small. Six reactions people understand beat a custom pack of 30 emotes that look like a Discord server and mean nothing in the score.

Trophies and the title ladder are light on purpose

Trophies are under Users, in the same customisation toolkit as fields and the title ladder. You set points and criteria. When the profile matches, the trophy is awarded and the points land on the public profile. Top trophy-point earners show in notable members.

Official limits you should design around:

• Once awarded, a trophy is not revoked if the user later fails the criteria. Do not use trophies for states that come and go (birthday, “has an avatar this week”). Use a promotion for states.
• Deleting a trophy removes its points from everyone who had it.
• You can disable trophies at the bottom of the trophy list if you do not want the system at all.
• Awards are not instant on every post. Force a pass at Tools > Cron entries → Update user trophies (the arrows-circle control) when you are testing, or after you add a trophy you want applied retroactively.

Criteria are the same system notices and promotions use. Documented examples: user has / has no avatar; posted at least X messages (the data is the number); registered more than a year; reaction score over 100; received at least 5 likes on a single post (like_count). Page criteria exist too (“user is creating a thread right now,” “selected navigation tab is Members”) — those belong on notices, not on trophies. A trophy for “is on the Members tab” is nonsense.

A useful default set is short:

1. Posted 1 message (they spoke).
2. Posted 10 messages (they came back).
3. Reaction score 10 (someone else noticed).
4. Has an avatar (they look like a person).
5. Registered 1 year (they stayed).

Name them in the language of the community, not “Level 1 / Level 2.” Do not invent 25 trophies on day one. Regulars will ignore the list. New people will think they failed a game they did not know they were playing.

User title ladder is the text under the name. Officially you may base it on messages, likes, or trophy points. The displayed title is the highest ladder row whose threshold is still below the user’s value: 0 / 50 / 100 messages and an 80-post user get the 50 title. Put a row at 0 so nobody is blank.

The ladder loses to two overrides, in this order:

1. A custom title typed on the user’s profile in the ACP. That wins over everything.
2. A user title override on a secondary group, resolved by Display styling priority when they are in several groups. The same priority also picks username CSS and banners (Setup > Options > User options > User banners).

If staff have a custom title and new members have a ladder that says “Larva / Pupa / Imago,” you built two cultures. Keep the ladder boring (Member / Regular / Veteran) or turn it off and let group banners do the talking. Do not fight a promotion’s banner with a ladder title that says the opposite.

A later article in this series will go deep on ranks, achievements, and full gamification. Do not install that stack until the five trophies above are awarding and people still come back without them.

Promotions are a participation ladder

Groups & Permissions > User group promotions. Official purpose: automatically add members to groups to change title, username styling, or permissions. Official examples: A/B segmentation, a birthday badge, a “contributed a lot” banner, username styling that marks new users.

That last one is the engagement use most boards skip. A New member secondary group with a banner, given to everyone under 10 messages or under 14 days, then taken away when they cross the line, is a signal to staff: answer this person. It is also a signal to the person: you are in week one on purpose.

How the job actually runs (manual, not folklore):

• The User group promotions cron runs every hour. Manual run: Tools > Cron entries > User group promotions.
• No criteria means the promotion is never awarded automatically.
• Only recently active members are processed. Lurkers who have not logged in will not be promoted or demoted until they come back. To stamp a group on the whole userbase, use batch update, not a promotion.
• If they stop matching, they are removed from the group — unless an administrator added that group on the profile, or another still-matching promotion also grants it.
• Disabling a promotion stops new awards. It does not demote people already in.
• Deleting or disabling will not undo group membership. To unwind: delete a purpose-built group, batch-remove membership, or change the criteria so nobody matches (the manual’s example is “registered before January 1990”) and wait for active users to be processed.
• Manage promoted users can apply or prohibit a promotion per person. Manual apply lasts even if they fail the criteria. Manual demote (delete icon → Promotion disabled) makes them ineligible until you undo it.

Never put Never on the Registered group to “lock” a privilege you then grant via promotion. Never on Registered is an absolute override; the extra group cannot punch through. Baseline on Registered, Yes on the promoted group. The permissions guide is the longer version of that sentence.

Do not use a promotion as a whitelist. Message count and reaction score are global. There is no stock criterion for “staff set the Approved prefix.” That is a human, or an add-on. Two different doors. The whitelist article is the human door.

A clean 2026 ladder:

Group	Criteria (all must match)	What it changes
New member	Registered less than 14 days or fewer than 10 messages	Banner only. Same permissions as Registered.
Regular	25+ messages, has avatar, reaction score ≥ 5	Slightly higher attach limits, a quiet banner.
Veteran	Registered 1 year and 200+ messages	Banner. Maybe a custom title override.

Registered stays primary for everyone. Promotions add secondary groups. If you also run a human Whitelisted group, do not reuse Regular as that group. A “100 reactions” promotion will add people you never interviewed.

Discovery: featured, stickies, prefixes, widgets

People cannot reply to threads they cannot find. Stock discovery, in the order you should spend time:

What’s new. Keep the tab. Do not rename it to something cute. Returning members already know the words.

Featured content (2.3). Staff with the featuring permission use thread tools. The public list is the featured/ route; the same queue feeds the widget. Order is featured date, not last post. 2.3 will not expire features for you — a calendar reminder will (2.4 is adding automatic unfeature; do not wait for it). Feature things guests can open. Feature one item that teaches a new member how the place works. Do not feature the private staff room.

Stickies. One or two per forum. A sticky is a landmine after the third one. A 2019 “read this first” that staff never update is anti-engagement: it sits above the thread that moved today. Review stickies when you review featured. If it is not acted on this month, unstick it and link it from the forum description.

Prefixes. Filters people actually use. They are not tags and they are not a group flip. Three to seven per forum, named the way members search (Solved, Looking for group, Recruiting), staff-only prefixes for states members should not set. The server listing article is the worked example. A prefix set of 20 colours is decoration.

Widgets. Appearance > Widgets. Stock keys the official add-on walkthrough actually names: new_posts, members_online, new_profile_posts, forum_statistics, share_page. Default sidebar position: forum_list_sidebar. Three widgets is a homepage. Twelve is a second application. New posts with a limit of five to eight beats a statistics block that says you have 1.2 million posts and 40 online. Hide members_online if the number will embarrass you.

Profile posts (new_profile_posts) are optional. On most boards they are a ghost town with spam. If your community does not already live on profiles, do not put that widget on the first screen. You will advertise emptiness.

HTML widgets are for one paragraph, not a second site. The portal article covers layout. Here the rule is: every widget must either show something that moved or tell a new person where to post. If it does neither, delete it.

What stock XenForo will not do

Be honest with the next add-on pitch.

Stock will not:

• Award points you can spend in a shop, or show a progress bar toward the next trophy
• Auto-watch a member onto a forum based on a custom field they ticked at registration (without a small add-on or listener)
• Expire a featured thread on a date (in 2.3)
• Turn a prefix change into a group change
• Give you Discourse-style trust levels as a single object (you can fake a thin version with promotions; it is not the same machine)
• Run events, raffles, or “post of the month” contests
• Replace staff replies

If the gap is “we need a shop,” wait for the later article on points and credits. If the gap is “nobody comes back,” a shop will not fix it. If the gap is layout — a ticker, a mosaic, a dedicated portal/ route — that is the portal article’s add-on test, not this one.

This domain used to sell themes and widgets that promised a livelier first screen. A ticker of old threads is not engagement. A stats widget that celebrates post count is not engagement. The stock New posts widget plus a watch on the two rooms that matter will beat both.

A 90-day engagement checklist

Paste this into the staff forum. Tick it in public so you cannot pretend you did it.

Week 1 — first screen and mail

1. Guest, new Registered, and admin see three sessions that tell a coherent story.
2. What’s new is in the public navigation. Forums default page is New posts or the tree is short enough that the forum list is the news.
3. SPF/DKIM pass. A test watch email arrives in under five minutes.
4. Welcome thread explains watches in two sentences. Staff are watching that thread.

Week 2 — types and notices

5. One question forum (or mixed-type with questions allowed) for things that have answers. Filters Unsolved / Your questions work for a dummy account.
6. Zero or one suggestion forum. If it exists, a dated staff reply exists on the top three ideas.
7. One Block notice per audience, with criteria. No scrolling stack. Avatar nag is Floating, not Block.
8. Stickies: at most two per active forum. Everything else unstuck.

Week 3 — recognition

9. Reactions: small set. Sad / angry stay neutral unless you have a written rule.
10. Five trophies, not twenty-five. Run Update user trophies once after you save them. Confirm they appear on a test account.
11. Title ladder: a 0-row, based on messages or trophy points, not both in your head. No custom titles on random regulars.
12. Promotions: New member banner that drops off, plus at most one Regular ladder. Hourly cron enabled. Registered has no Never that the ladder needs to punch through.

Weeks 4–12 — movement

13. One recurring staff thread a stranger can answer without lore. Weekly is enough.
14. Featured queue reviewed every Monday. Private threads unfeatured. One feature that teaches the place.
15. Staff reply budget written down. If you cannot answer new posters this month, do not run a campaign that creates more of them.
16. Numbers you actually look at: registrations, first posts, second sessions in seven days, posts by accounts younger than 30 days, unsolved question count. Not “total posts.”

If first posts are fine and second sessions are not, go back to the first screen and watches. If second sessions are fine and second posts are not, the thread types are wrong or staff are liking instead of answering. If both are fine and people still say the board is dead, you are measuring the wrong rooms — archive and off-topic do not count.

FAQ

Should I set New posts as the homepage for everyone?
Returning members yes. Brand-new members need a “start here” in addition, not instead. A notice with “message count is 0” plus a pinned welcome is enough. Do not build a second homepage for that sentence.

Can I promote people who posted in a specific forum?
Not with stock criteria. Message count is global. Use a question forum and staff eyes, or an add-on that adds a criterion. Do not fake it with “25 messages anywhere.”

Why did a lurker not get the Veteran banner?
Promotions process recently active users. They have to log in. Then wait for the hourly job, or run User group promotions by hand.

I disabled a promotion and people still have the group.
Expected. Disable stops new awards. Unwind with batch update, a criteria change that matches nobody, or by deleting a purpose-built group.

Can I take a trophy back?
Not automatically. Officially, trophies are not revoked when criteria fail. Delete the trophy if you want the points gone from everyone. Use a promotion for reversible states.

Should guests see reaction scores and trophy points?
Yes, if the numbers are real. A notable-members list of staff alts is a tell. Hide the Members tab before you hide the counters.

Do profile posts help?
Only if people already use them. Putting new_profile_posts on an empty first screen advertises that they do not.

Is a points-and-shop add-on the next step?
Only after this checklist is boring. A shop on a quiet board is a catalogue nobody walks through.

Will this overlap the 30-day onboarding plan?
At the edges, on purpose. That article is a calendar. This one is the ACP objects it points at. Do both.

Do this afternoon

1. Write the one sentence: what should a member who was here on Tuesday see first on Friday. If you cannot write it, you are not ready to buy an add-on.
2. Put What’s new where a returning member expects it. If the tree is a junk drawer, flip Forums default page to New posts or fix the nodes first.
3. Communication > Notices > Add notice: one Block, criterion “User is a guest” or “message count is 0,” one link. Delete the rest of the live notices or set them Floating.
4. Create or clean one question forum. Post one real question. Answer it. Mark the solution. Confirm Unsolved / Solved looks right on a dummy account.
5. Content > Reactions: confirm sad and angry are neutral. Remove any custom reaction you cannot explain in five words.
6. Users trophies: five rows, then Tools > Cron entries → Update user trophies.
7. Groups & Permissions > User group promotions: New member banner, short window, Registered still primary. Run the promotions cron once. Check a dummy account with Analyze permissions.

A board that answers the first post, shows what moved, and watches the rooms that matter will out-engage a board with a shop, a ticker, and a rank plugin. Ship the hooks today. Buy the game when people are already playing.