Skip to main content
The ad is displayed by the supported app after the subscription update via gateway Axottle. remnawave.manage is required to change. The settings relate to the Remnawave connection and are used by all of its design-enabled pages.

Personal communications

In Registration → User → Messages, select the personal ad mode. In mode, no personal text is added from the original subscription; a suitable general ad can still replace the original message. The temporary announcement term is introduced at the local time of the operator. In Happ, the description uses the same slot as the ad: it is not an additional independent block.

Advertising to the audience

Open Subscription Page → Ads and create a rule:
  1. Set the title and text up to 200 characters.
  2. Choose the recipients: everyone, internal squad Remnawave or specific users.
  3. If necessary, specify excluded users, the platform, and the exact Remnawave tag.
  4. Set a beginning, an end and a priority. The higher the priority, the higher the priority.
  5. Include the rule and keep it.
Audience, platform, tag, and schedule must match at the same time. Audience membership is double-checked at issue. User search uses synchronized connection data, the squads list is downloaded from Remnawave.

How the message is selected

For personal messages, the order is as follows: support response → temporary announcement → message about connection changes → description. Support response and temporary personal announcement take precedence over audience announcements. A suitable audience announcement, in turn, replaces the description and takes precedence over the message about connection changes. Among the suitable audiences, individual users are first considered, then the team, then everything; then the numerical priority is taken into account. Check the result through Check the issuance of: the presence of an active rule does not guarantee that it will defeat the higher priority message.

Notification of support response

The current Remnawave user’s connection to Telegram and the request of the same project is checked; responses sent to the client are counted; internal notes and unsuccessful sendings do not create a notification; the text of the response is not transmitted to the subscription. The notification is removed after a new message from the client, the completion of the request or seven days after the response, it is a signal that there is a response, not a confirmation of not being read. Specify a client support link, such as an HTTPS link to a bot, and the administrative reference is not suitable for this.

Verification

Select a test user that fits the rule, and check the results for the right platform. Check the source of the message and the deadline. Then update your in-app subscription. Separately check the user from the exception list.

Rollback

Turn off or delete the audience rule. For a personal message, clear the temporal text or return the original mode and save. The client will receive the result the next subscription update. If versions conflict, reread the rule and combine the changes instead of overwriting someone else’s edits. Related pages: registration, API ads . Displaying messages depends on the header support of the client application.