# Create Web Push

{% hint style="info" %}

#### Quick path

**Messages** → **Campaigns** → **Create New Campaign**

1. Set the campaign name and format in [**Step 1: Setup**](#step-1-setup).
2. Add content, links, and optional personalization in [**Step 2: What**](#step-2-what).
3. Define the audience in [**Step 3: Who**](#step-3-who).
4. Set timing, expiry, and delivery speed in [**Step 4: When**](#step-4-when).
5. Review, test, and send in [**Step 5: GO**](#step-5-go).
   {% endhint %}

Create Web Push is the guided flow for building a web push campaign from start to send.

Use it to:

* send one-time browser notifications,
* target broad or specific audiences,
* and test the message before launch.

### Before you start

Before creating a campaign, make sure:

* your web push channel is already configured,
* your audience data already exists,
* and your destination URL is ready.

{% hint style="info" %}
If you plan to personalize the message, prepare the required [**Profile Attributes**](/netmera-user-guide/customer-data/profile-attributes.md) first.
{% endhint %}

### Web push formats

Netmera offers two types of Web Push notifications to reach your users:

* **Text** — includes title, message, and icon.
* **Image** — adds a larger banner image for supported browsers.

{% hint style="info" %}
You can add **interactive buttons** to both formats.
{% endhint %}

{% @arcade/embed url="<https://app.arcade.software/share/BTSE1e98FeovGVSx88Ks>" flowId="BTSE1e98FeovGVSx88Ks" %}

### Campaign flow

When you click **Create New Campaign**, Netmera opens a five-step flow:

1. **Setup**
2. **What**
3. **Who**
4. **When**
5. **GO**

You define the format, content, audience, schedule, and final review in this flow.

<figure><img src="/files/SvUhANMwKKxuAXtVBVLn" alt=""><figcaption></figcaption></figure>

### Step 1: Setup

In **Setup**, define the basic campaign settings:

* **Campaign Name** — use a clear, searchable name.
* **Campaign Type** — select **Web Push**.
* **Notification Format** — choose **Text** or **Image**.
* **Add Buttons (Interactive)** — enable button actions if needed.

The right panel shows **Reach Estimate**. It breaks down the expected audience by browser and total recipients.

<figure><img src="/files/tZZurGaUKqy59t604aGS" alt=""><figcaption></figcaption></figure>

### Step 2: What

In **What**, define the content and behavior of the notification.

#### Core fields

Use these fields in most campaigns:

* **Category** — groups campaigns for consent and reporting.
* **Notification Message** — the main message body.
* **Title** — the short headline users see first.
* **Click URL** — the page users open after clicking.
* **Icon URL** — the thumbnail shown with the notification.

Use clear copy. Keep titles short. Make the click URL match the message intent.

#### Personalization

You can personalize the message with profile attributes such as `{@name}` or `{@age}`.

Example:

* Default: `Happy birthday!`
* Personalized: `Wishing you a sweet {@age}th birthday {@name}!`

<figure><img src="/files/R92ZkTaZIWg7OV8qXB3L" alt=""><figcaption></figcaption></figure>

Personalization requires [**Profile Attributes**](/netmera-user-guide/customer-data/profile-attributes.md). For a full walkthrough, see [**Personalized Web Push**](/netmera-user-guide/omnichannel-engagement/web-push/create-web-push/personalized-web-push.md).

#### Browser-specific options

{% hint style="warning" %}
**Image URL** is available only for Chrome and only for the **Image** format.
{% endhint %}

Available options:

* **Image URL** — adds a larger banner image.
* **User Interaction Required** — keeps the notification visible until interaction.
* **Push Button** — adds a predefined button set.

For image notifications, use a recommended aspect ratio of **2:1**.

If you use buttons, create the button set first in [**Button Sets**](/netmera-user-guide/omnichannel-engagement/mobile-push/button-sets.md).

#### Tracking and delivery options

You can also configure these options:

* **Disable Webhooks** — stops Netmera from sending interaction data to your backend.
* **Fallback (SMS / Call External URL)** — defines a backup action if push delivery fails.
* **Message Label** — tags campaigns for filtering and comparison.
* **Conversion Analytics** — tracks a downstream event after the click.
* **Control Group** — withholds a percentage of the audience for lift measurement.
* **Conversion Deadline** — defines how long a click stays eligible for attribution.

<figure><img src="/files/PKmFIb5wIflbVNn4nQ9a" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
Fallback delivery needs the required channel integration before use.
{% endhint %}

<figure><img src="/files/9gfmUALYxKnTJf0iEkjc" alt="" width="375"><figcaption></figcaption></figure>

#### Control Group

If you use a control group, Netmera withholds that audience from the send. This helps measure real campaign impact against users who did not receive the notification.

{% hint style="info" %}
Example: with an audience of **100,000** and a control group of **1%**, **1,000** users do not receive the notification.
{% endhint %}

#### Conversion Deadline

A conversion is counted when the user receives the message, clicks it, and completes the conversion event within the same session.

For a click to be attributed, it must happen within the **Conversion Deadline** window. This window starts at message delivery.

Clicks outside this window are not counted as conversions, even if the conversion event is completed later in the same session.

**Example**

<table><thead><tr><th>Scenario</th><th>Delivery</th><th width="141.27508544921875">Click</th><th width="136.802490234375">Deadline</th><th>Result</th></tr></thead><tbody><tr><td>Within window</td><td>14:00</td><td>17:30</td><td>2 hours</td><td>✅ Conversion +1</td></tr><tr><td>Outside window</td><td>14:00</td><td>18:30</td><td>2 hours</td><td>❌ Not counted</td></tr></tbody></table>

<figure><img src="/files/6gUqzEfFpVpiB4v6vbHu" alt="" width="563"><figcaption></figcaption></figure>

### Step 3: Who

In **Who**, choose which subscribers should receive the campaign.

<figure><img src="/files/aKbidMCvQB52U7HgnDUA" alt=""><figcaption></figcaption></figure>

#### Audience options

You can target the campaign with these options:

* **Send All** — sends to all subscribed web push users.
* **Select Users** — filters by selected criteria.
* **Advanced** — builds condition groups with AND / OR logic.
* **Distribution List** — uses a saved audience list when available.

#### Select Users

You can learn more about segments in [**Segments**](/netmera-user-guide/targeting/segments.md).

#### Advanced

Use **Advanced** to build more detailed logic with conditions and groups.

<details>

<summary>Advanced Users Options</summary>

Each condition represents a behavior or attribute. Groups combine conditions with:

* **AND:** Includes only users who meet *all* selected conditions.
* **OR:** Includes users who meet *any* of the selected conditions.

Netmera updates the matching audience in the right panel as you build the logic.

<figure><img src="/files/5HEkGEOieDGyF5Balci9" alt=""><figcaption></figcaption></figure>

The **Selection Criteria** panel shows the matching users, devices, and browsers.

<div align="left"><figure><img src="/files/bxJWyOl2AqoeMWAbo02W" alt="" width="285"><figcaption></figcaption></figure></div>

</details>

#### Additional controls

You can also adjust these controls:

* **Ignore User Message Limits** — bypasses frequency limits for this send.
* **Limit Target Users** — caps the number of recipients.

Use recipient limits for phased sends or smaller test campaigns.

<figure><img src="/files/gtQHoNWS5ZavqbvSp2eo" alt="" width="297"><figcaption></figcaption></figure>

### Step 4: When

<figure><img src="/files/ghW4GEIaTcExm1phQj40" alt=""><figcaption></figcaption></figure>

In **When**, choose when the campaign starts and how long it stays eligible for delivery.

#### Start Sending Messages

Choose one of these options:

* **Now** — sends immediately.
* **On Specific Time** — schedules the send for later.

<figure><img src="/files/a18JQmGD1IPe88B0G0Uf" alt="" width="540"><figcaption><p>Start Sending Messages</p></figcaption></figure>

#### Delivery Speed

Choose how quickly Netmera sends the campaign:

* **Send Fast:** Delivers the notification to all users at once.
* **Send in Packages:** Sends in batches of a defined size.

<figure><img src="/files/vHCLFZ3gZigDFNgsuSbR" alt="" width="544"><figcaption><p>Delivery Speed</p></figcaption></figure>

Use packaged delivery for larger audiences or traffic-sensitive campaigns.

#### Message Expiry when Not Reached to Client

Choose what happens when the user is temporarily unreachable:

* **Never:** The system keeps attempting delivery to the user.
* **Until a Specific Time:** The notification expires after a defined period.

<figure><img src="/files/S7ytIORRKXvb1sQgGHfD" alt="" width="531"><figcaption><p>Message Expire Time</p></figcaption></figure>

### Step 5: GO

In **GO**, review the full campaign before launch.

Before sending:

* confirm the content and targeting,
* preview the notification,
* test on registered devices,
* and send or submit for approval.

#### Test on device

You can preview the notification on supported devices and browsers.

You can test on:

* your registered test devices,
* or only your own device.

Manage test devices in [**Settings → Test Devices**](/netmera-user-guide/panel-settings/netmera-panel-settings/test-devices.md).

<figure><img src="/files/vpUpmVtiDkJduN80tmUz" alt=""><figcaption></figcaption></figure>

### Related pages

* [Personalized Web Push](/netmera-user-guide/omnichannel-engagement/web-push/create-web-push/personalized-web-push.md)
* [Profile Attributes](/netmera-user-guide/customer-data/profile-attributes.md)
* [Button Sets](/netmera-user-guide/omnichannel-engagement/mobile-push/button-sets.md)
* [Message Categories](/netmera-user-guide/omnichannel-engagement/mobile-push/message-categories.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/web-push/create-web-push.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.