Actions are the conditions a participant must complete to enter the giveaway and/or receive a marker.
There are 8 actions in total: participation button, post reaction, channel subscription, repost, comment, keyword hunt, game task and inviting a friend.
Not every condition works on every platform: a reaction only counts on VKontakte, repost works in Telegram and VKontakte, and the other six actions work everywhere.
Which action works where#
The activity builder hides the conditions your channel's platform cannot verify. Here is the full summary.
| Action | Telegram | VKontakte | MAX | Why |
|---|---|---|---|---|
| Participation button | Yes | Yes | Yes | Platform-independent: participation is recorded when the app is opened |
| Reaction | No | Yes | No | Telegram: reactions to a channel post are anonymous, the Bot API never says who left them. VKontakte: any like counts, a specific emoji cannot be required. MAX: the API has no reaction events at all |
| Channel subscription | Yes | Yes | Yes | In MAX the check only works if our bot is an administrator of the channel |
| Repost | Yes | Yes | No | MAX has no repost verification: the platform does not report who shared the post |
| Comment | Yes | Yes | Yes | Telegram: the channel needs a linked discussion group, and the channel bot must be its administrator. VKontakte: comments must be enabled for community posts. MAX: the channel must have comments enabled and our bot must be a channel administrator; a comment left on behalf of the channel itself does not count |
| Keyword hunt | Yes | Yes | Yes | The word is typed right in the mini app, no social network involved |
| Game task | Yes | Yes | Yes | The game result is verified inside the app |
| Invite a friend | Yes | Yes | Yes | Platform-independent, but a friend is confirmed by their subscription - so the "Subscribe to channel" action is required alongside |
There is no manual verification by the organizer in Re:Activity: if a condition is verified at all, it is verified automatically. A condition the platform cannot verify simply is not offered to you.
Action Types#
Participation Button#
The participant must tap the button in the activity post to launch the Re:Activity app, which registers their participation in the giveaway.
This action requires no additional parameters and is completed automatically when the app is opened.
Reaction#
The participant must leave a reaction (emoji) under the activity post.
Parameter: a comma-separated list of allowed emoji (for example: 👍,❤️,🔥). If the list is empty, any reaction is accepted.
Where it works: on VKontakte only (see the summary table). A like on a community post is counted. VKontakte does not report the reaction type, so the emoji list is not checked there - any like will do. Removing a like does not revoke an already completed condition.
For Telegram and MAX channels the builder will not offer this condition - pick the participation button, a comment or a subscription instead.
Channel Subscription#
The participant must be subscribed to one or more specified channels.
Parameter: a list of your connected channels. Select one or more - the participant must subscribe to all of the specified channels.
Verification is performed through the platform's API when the entry is submitted and again during summarizing. If the participant unsubscribes before the results are drawn, the completion mark is revoked.
MAX: the subscription is checked automatically, but only if our bot is an administrator of the channel. Without administrator rights the platform does not return the member list, and the condition stays unverified.
Repost#
The participant must repost the activity's publication.
For Telegram, three methods are available:
| Method | Description |
|---|---|
| Forward to bot | The participant forwards the post to our bot in a direct message - the bot records the repost |
| Referral link | The participant shares a link unique to them - the platform counts clicks |
| Story mention | The participant publishes a story mentioning the bot |
For VKontakte:
- Require open profile - the participant's wall must be public for verification
- Minimum duration - how many days the repost must remain on the page (7 days by default)
For MAX the condition is not available: the platform does not report who shared the post, so there is nothing to verify the repost against.
Comment#
The participant leaves a comment under the activity post.
Parameter: a keyword phrase - if set, the comment must contain it. Case, punctuation and emoji are ignored: "Want it!!! 🔥" counts as "want it". If no phrase is set, any comment qualifies.
This is the same code-word mechanic as in the Keyword Hunt action: the only difference is where the participant types the word - in the post comments or inside the app. See Code-word scenarios for ways to use it.
Prerequisites. In Telegram the channel must have a linked discussion group, and the channel bot must be an administrator of that group: comments arrive from it. If the group is missing, the activity builder does not allow adding a comment action or a comment retry. If the group exists but the bot is not an administrator, the builder shows a warning and participant comments are not counted. In VKontakte comments must be enabled for community posts. In MAX the channel must have comments enabled and our bot must be a channel administrator - otherwise the platform sends us no comments at all.
A comment left on behalf of the channel does not count. If you write a comment as the channel (not as a regular participant), the messenger does not tell us who exactly left it, so there is nobody to credit. This most often shows up in MAX when an owner tests their own activity: the comment is visible, but the condition stays unmet. Comment under your own name and it will be counted.
If a participant edits the comment and removes the keyword phrase, the action is revoked again - together with the markers that relied on it.
Keyword Hunt#
The participant types the given word right in the activity mini app - post comments play no part here.
Parameters:
- Keyword - required, the condition cannot be saved without it
- Match mode - the word occurs in the text, an exact match, or a regular expression
- Hints on misses - one per line: the first opens after the first wrong answer, the second after the second, and so on
The number of attempts is unlimited, with a two-second pause between attempts - brute-forcing the word won't work, while an honest mistake costs nothing. In the "occurs in the text" and "exact match" modes case, punctuation and emoji are ignored; in the regular-expression mode the text is matched as typed, case-insensitively. The app answers right away whether the word is correct, and a correct answer completes the condition.
Available only in the Keyword Hunt activity type: in other types the participant has nowhere to type the word. For the same reason this action is incompatible with the Game Task. In a classic giveaway the code word is collected via a Comment with a keyword phrase.
Code-word scenarios#
The code word works the same way in a comment with a keyword phrase and in Keyword Hunt - only the place where it is typed differs. Two proven scenarios:
- The word is right in the post. The simplest option: "Write 'want it' and you're in". Good for collecting entries and quick engagement: the participant sees the condition and completes it in seconds. With a comment you also get activity under the post; with Keyword Hunt everything happens in the app and no comments are needed.
- The word is hidden in your content. The contest post doesn't name the word: it has to be found in earlier publications or assembled piece by piece. For example, one letter per post or reel for four days in a row, and on the fifth day a giveaway where those letters form the word. Or a riddle on your channel's topic whose answer is the code word. This way participants dive into the channel's content instead of just pressing a button. Keyword Hunt fits this scenario better: the answer isn't visible in the comments, and you can reveal hints on misses.
The word can be typed from any device and on any platform - Telegram, VKontakte or MAX.
Game Task#
The participant plays a mini-game embedded in the activity. The condition is considered fulfilled once a set goal is reached - for example, scoring a certain number of points or clearing a certain number of levels.
The specific goal depends on the game and is configured by the administrator when setting up the activity type. Example goals:
| Goal | Example |
|---|---|
| Minimum score | Score ≥ 500 points |
| Level / round | Reach level 3 |
| Survival time | Survive 60 seconds |
For more on available games and goal parameters, see Mini-games. For the activity type, see Mini-game.
Invite a friend#
The participant shares a personal link. A friend counts once they open that link and subscribe to the activity's channel. The invited person becomes a participant of the giveaway too.
Parameter: how many confirmed friends are required. The minimum is 1; zero is not allowed.
A required companion action. Invitations only work together with the Subscribe to channel action: confirming a friend is tied to their subscription. Without a "Subscribe to channel" action, invitations will never be confirmed. The creation wizard notices this and offers to add the subscription - accept it.
Reward for the inviter. Each confirmed friend earns the participant 1 🧲 magnet. It is credited the moment the friend is confirmed, whether or not the required number of friends has been reached.
Why a participant would bother. Magnets matter where a retry-for-🧲 rule exists: then inviting turns into extra attempts in the game. Without such a rule magnets pile up with nothing to spend them on in this activity, so inviting brings the participant nothing. For game activities the wizard offers to add a "attempt for magnets" rule.
The button does not disappear. Once the required number of friends is reached the condition is met, but the button stays - people can keep inviting, and magnets keep being credited for every new friend. Only its appearance changes: it stops being the screen's main action.
Effect on the prize. Like any other action, inviting affects the draw only if it belongs to a marker that a prize is tied to. If inviting is not part of a marker, it is a voluntary bonus: the participant earns magnets, but their odds of winning stay the same. See Tying a prize to a marker.
Verification Order#
By default, the participant must complete all added actions. The order in which they're completed doesn't matter.
Verification happens in two stages:
- On entry submission - an instant check of the available data
- During summarizing - a final check before winners are selected
Markers and Action Grouping#
If you need a multi-stage structure, use Markers.
One thing to keep in mind: an action on its own affects nothing. It becomes a condition for winning a prize only when it belongs to a marker and a prize is tied to that marker. An action outside any marker is still visible and completable, but it does not affect the draw. See Tying a prize to a marker.