# Engagement

> Reach your users after the install: push campaigns, in-app messages, journeys and the experiments that measure them.

Source: https://docs.grovs.io/docs/engagement

Engagement tools message people who already have your app. Pick an audience from a [segment](https://docs.grovs.io/docs/analytics/segments) or a list of users, and every message reports back what happened. In the dashboard they live under **Engage**.

- [Push campaigns](https://docs.grovs.io/docs/engagement/push-campaigns): Send a notification to a segment, a user list or single devices, now or scheduled. See who got it and who tapped it.
- [In-app messages](https://docs.grovs.io/docs/engagement/in-app-messages): Show covers, pop-ups, header and footer banners, alerts or your own HTML in your app or site, the moment people do something.
- [Journeys](https://docs.grovs.io/docs/engagement/journeys): Move people through waits, splits, pushes and in-app messages. They enter on an event or a segment and leave at a goal.
- [Experiments](https://docs.grovs.io/docs/engagement/experiments): Compare variants, hold back a control group, and see whether a message changed what people do and what it earned.

## Before you start

- **Install the SDK.** Messages reach devices through the Grovs SDK. Push campaigns need iOS SDK 3.1.0 or Android SDK 3.1.0 or later to report taps. See push notifications on [iOS](https://docs.grovs.io/docs/sdk/ios/push-notifications) and [Android](https://docs.grovs.io/docs/sdk/android/push-notifications).
- **Identify your users.** Set a user identifier in the SDK to target people by your own user ID and recognise them across devices.
- **Track events.** Segments, triggers and experiment goals are built from the events and screens your app reports.

## Settings shared by every message

**Engage › Engagement Settings** holds the project-wide rules:

| Setting                   | What it does                                                                                                                                                                   |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Control group             | Holds back 0 to 20% of people from every in-app message, journey and dashboard push campaign. Server pushes still reach them. Experiment reports show them as their own group. |
| Pushes per person per day | Caps pushes per person per UTC day, across every campaign and journey. Off by default.                                                                                         |
| In-app messages           | On/off switch and limits for in-app messages.                                                                                                                                  |

Anyone on the project's team can create, send and change messages and these settings.