Search translations

Impression diet

Impression events sample rate

Legacy hiding and impression counting support

I have a positive impression of Miraheze Stewards

Set a non-default sample rate for logging impression events.

I have a positive impression of Miraheze as a service

Impression events sample rate (should be between 0 and 0.01, inclusive)

Number of days to suppress large banner display after initial impression.

I have a positive impression of Miraheze Site Reliability Engineering (System administrators)

Edit created via the CentralNotice Admin UI

Edit of CentralNotice content created via the Translate extension

Automatically protected by CentralNotice; please edit only via [[Special:CentralNotice]] or [[Special:Translate]]

Banners of a specific category share tracking variables and group settings (e.g. hide cookies and impression counts). Category names can be magic words like <nowiki>{{{campaign}}}</nowiki> or <nowiki>{{{banner}}}</nowiki> which will be automatically expanded at display time. Values must be alphanumeric.

protect translatable messages handled by the Translate extension and included in CentralNotice banners

Sequences are set separately for each bucket. For any step, only banners assigned to the sequence's bucket are available. To always show a step, leave the "Skip with identifier" field blank. If an identifier is set, then once the step has completed, a flag will be stored in the user's browser using that identifier, and the next time the user reaches a step with the same identifier, it will be skipped. Identifiers from the "Large banner limit and switch" mixin are compatible and will also be taken into account. Once a sequence finishes, it starts again from the beginning. (To prevent a sequence from repeating, use the "Impression diet" mixin to limit impressions.)

Obtain the banner allocations for banners served by CentralNotice for all user types under the parametric filter.

An identifier for persistent client-side data stored by this feature (such as impression counts). This field is optional for most campaigns. If you leave it blank, campaigns in the same category will share impression counts, or, if this campaign does not use the category feature, counts will be specific to this campaign. To share this data across several campaign categories, specify the same identifier for each campaign. Note: certain campaign categories used to be configured to use cookies for this feature. For campaigns in those categories, this identifier was the cookie name; such legacy cookies will be migrated. Also note that if the identifier is changed during a campaign, all counts to date will be lost.

Obtain the banner allocations for banners served by CentralNotice for all user types under the parametric filter.

This is a JSON only call.

Large banner display is suppressed across campaigns with the same identifier. Default value 'centralnotice-frbanner-seen-fullscreen' may be used to migrate legacy cookies.

Devices on the mobile site which are not iPhones, iPads, or Android - ([https://github.com/wikimedia/mediawiki-extensions-CentralNotice/blob/master/modules/ext.centralNotice.bannerController/mobile/device.js Selector logic])

Banners display announcements of interest to Wikimedia communities and users.

Below are options that allow you to manage which types of announcements you see. Certain platform notices, such as those relating to site maintenance and special notices considered necessary to all users, will always be displayed. For further information, please read the [[metawikimedia:Special:MyLanguage/CentralNotice|documentation on Meta-Wiki]].