---
updatedAt: 2025-11-11T02:47:31.000Z
agentTools:
  projectIndex: https://docs.webengage.com/llms.txt
---

# In-app Messaging

No additional steps are required for enabling *In-app Notifications.* However, we recommend that you track the various sections of your app as *[Screens](in-app#section-step-2-set-up-in-app-message-targeting)* to customize In-app message placement. You can also track specific app-user interactions as *[Screen Data](in-app#section-step-2-set-up-in-app-message-targeting)* to contextually show the In-app message. These data points can be used to [configure In-app message targeting](https://knowledgebase.webengage.com/docs/creating-in-app-campaigns#section-step-2-specify-when-to-show-which-screen-to-show-on-how-many-times-to-show) while creating the campaign.

> 🚧 Before continuing, please ensure that you have [added the WebEngage SDK to your app](xamarin-android).

## Tagging App Screens

Screens are mobile equivalent of web pages, which can have associated properties. WebEngage SDK allows you to tag whenever a user sees a screen in your Xamarin.Android app pages. These tags allow you to pinpoint screens in your app where you would later render in-app messages using WebEngage dashboard. A Xamarin.Android app can have multiple screens and vice versa is also possible. Note that screens are only usable for targeting in-app engagements.

All screen related APIs are part of WebEngage Android SDK's Analytics object. You get an instance of WebEngage Analytics object as follows.

```csharp
// import WebEngage SDK
using Com.Webengage.Sdk.Android;
...
	
// Get an instance of ‘Analytics’ object
Analytics weAnalytics = WebEngage.Get().Analytics();
```

You can tag screens from the `onStart` of your Android activity as shown below.

```csharp
using Com.Webengage.Sdk.Android;
using Java.Lang;
...

  public class YourActivity : Activity
  {
    ...
      protected override void OnStart()
    {
      base.OnStart();
      weAnalytics.ScreenNavigated("Purchase Screen");
      ...
    }
  }
```

> 🚧 `ScreenNavigated` informs WebEngage SDK that the user has navigated to a new screen. Any previously set screen data is lost.

## Tracking Screen Data

Every screen can be associated with some contextual data, which can be part of the targeting rule for in-app messages. Your app can update the data associated with a screen using the screen APIs described below.

```csharp
IDictionary<string, Object> screenData = new Dictionary<string, Object>();
screenData.Add("productId", "~hs7674");
screenData.Add("price", 1200);

weAnalytics.SetScreenData(screenData);
```

> 🚧 These APIs can be called any number of times after calling `screenNavigated`.

You can set the screen name and data in a single API call as shown below.

```csharp
weAnalytics.ScreenNavigated("Purchase Screen", screenData);
```

Please feel free to drop in a few lines at *<support@webengage.com>* in case you have any further queries. We're always just an email away!