--- title: "Engagement rules" slug: "engagement-rules" updated: 2026-09-22T12:04:47Z published: 2026-09-22T12:04:47Z canonical: "docs.xtremepush.com/engagement-rules" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt > Use this file to discover all available pages before exploring further. # Engagement rules Discover and fine-tune the principles that govern subscriber engagement The options at **Settings > Channels > Engagement Rules** allows you to manage rules for engaging with subscribers. ## Engagement rules ### Disable broadcast messages By default, campaigns can be sent to all subscribers within a project with no segmentation applied. Users can disable this option by toggling the **Disable broadcast messages slider**; once disabled, a segment must be chosen for all campaigns before they are sent. ### Require audience count on campaign approval Off by default. This setting enforces an audience calculation at the campaign approval step before a scheduled send so a final check can be made to see expected send numbers. Calculating the audience will always be required regardless of the settings if SMS or WhatsApp are one of the selected channels for the campaign. ### Require engagement category By default, assigning an **Engagement category** to campaigns is optional. Enabling this slider makes it mandatory. This may be important to enforce any messaging limits set in your engagement categories. ### Enable targeting application By default, campaign messages are sent using all the available [apps & sites](/documentation/docs/apps-sites) that are available for user profiles selected for the campaign. This option allows campaign editors to further [target the campaign](/documentation/docs/campaign-segment) to specific apps. This can be useful if you have multiple brands in a single project and want certain messages to only be displayed on specific apps. Click **Save** to confirm any changes. ## Engagement categories This section has been relocated to **Campaigns > Engagement Categories**. Review our [dedicated guide](/documentation/docs/engagement-categories) for more details. ## Global Include Condition Global Include Conditions supersede all other rules, such as engagement categories and campaign-level segmentation. When enabled, these conditions must be met for any communication to be sent from the platform. It allows you to exclude users who don't meet these attribute-based conditions. For instance, if you want to exclude users who have deleted their account, you could configure global include conditions by adding a condition that the attribute `account_deleted` is not equal to `true`. This means that any recipients who have `account_deleted` with a `true` value or don't have this attribute set won't receive campaigns. ![](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/8b39e83-Screenshot_2023-01-10_at_13.50.47(1).png?sv=2026-02-06&spr=https&st=2026-10-31T12%3A41%3A05Z&se=2026-10-31T13%3A41%3A05Z&sr=c&sp=r&sig=fQWSvH3XebX6Xu3%2FtNiHlBrWPa8CgyNhoYxCom8V9IM%3D) > [!WARNING] > In the above example, the condition using `Not equals` only matches users who have the attribute set. Users with no `account_deleted` attribute at all aren't excluded by this condition, so they would still receive the campaign. > > > > To also exclude users with no location set, add a second row for `account_deleted` using `Not set` as shown below. ![](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/91998ca-Screenshot_2023-01-10_at_13.52.01(1).png?sv=2026-02-06&spr=https&st=2026-10-31T12%3A41%3A05Z&se=2026-10-31T13%3A41%3A05Z&sr=c&sp=r&sig=fQWSvH3XebX6Xu3%2FtNiHlBrWPa8CgyNhoYxCom8V9IM%3D) ## Channel Include Condition **Channel Include Condition** allows you to set attribute-based conditions that control who receives campaigns in any of your configured channels. You can configure a condition for each channel individually. These conditions then apply to all single and multistage campaigns. Like **Global Include Condition**, this condition also supersedes other rules, such as engagement categories and campaign-level segmentation, for the channel it applies to. If you’re using both global and channel conditions together, see [Using Channel and Global Conditions together](/documentation/docs/engagement-rules#using-channel-include-condition-with-global-include-condition). > [!NOTE] > **Channel Include Condition** supports custom attribute-based conditions only. To set up a **Channel Include Condition** : 1. **Enable** the channel you want to configure. 2. Set your condition by choosing an **Attribute**, an operator, and a value. Select **Add new row** if you want to add more conditions to the same channel. > [!WARNING] > For each channel, you can use either **AND** or **OR** conditions but not a combination of both. 3. Click **Save**. ### Example Use Cases - You may want to send in-app and onsite campaigns only to premium-account users who are KYC-verified. The image below shows an example of how to set up this condition. ![](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/Screenshot 2026-09-14 at 14.28.00.png?sv=2026-02-06&spr=https&st=2026-10-31T12%3A41%3A05Z&se=2026-10-31T13%3A41%3A05Z&sr=c&sp=r&sig=fQWSvH3XebX6Xu3%2FtNiHlBrWPa8CgyNhoYxCom8V9IM%3D) - You may want to exclude users from receiving campaigns. For example, you want to exclude users based in Dublin from receiving web push campaigns. The image below shows an example of how to set up this condition. ![Web push settings with conditions for user location and campaign targeting options.](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/Screenshot 2026-09-01 at 14.27.18.png?sv=2026-02-06&spr=https&st=2026-10-31T12%3A41%3A05Z&se=2026-10-31T13%3A41%3A05Z&sr=c&sp=r&sig=fQWSvH3XebX6Xu3%2FtNiHlBrWPa8CgyNhoYxCom8V9IM%3D) > [!WARNING] > In the above example, the condition using `Not equals` only matches users who have the attribute set. Users with no `location` attribute at all aren't excluded by this condition, so they would still receive the campaign. > > > > To also exclude users with no location set, add a second row for `location` using `Not set`. ### Using Channel and Global Conditions together If you have **Global Include Condition** enabled, a user must meet both conditions to receive a campaign on that channel. For example, say you set up: - A **Global Include Condition** to exclude users who have deleted their account, using the attribute `account_deleted` is not equal to `true`. This applies across every channel in your project. - You then want an extra restriction just for Web Push, so you add a **Channel Include Condition** on Web Push where `location` is not equal to `Dublin`. In this scenario, a user needs an active account (the Global condition) and a location other than Dublin (the Channel condition) to receive a Web Push campaign. On other channels, like email or SMS, they only need to meet the Global condition.