Create Web Push

Quick path

MessagesCampaignsCreate New Campaign

  1. Set the campaign name and format in Step 1: Setup.

  2. Add content, links, and optional personalization in Step 2: What.

  3. Define the audience in Step 3: Who.

  4. Set timing, expiry, and delivery speed in Step 4: When.

  5. Review, test, and send in Step 5: GO.

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.

If you plan to personalize the message, prepare the required Profile Attributes first.

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.

You can add interactive buttons to both formats.

spinner

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.

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.

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}!

Personalization requires Profile Attributes. For a full walkthrough, see Personalized Web Push.

Browser-specific options

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.

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.

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.

Example: with an audience of 100,000 and a control group of 1%, 1,000 users do not receive the notification.

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

Scenario
Delivery
Click
Deadline
Result

Within window

14:00

17:30

2 hours

✅ Conversion +1

Outside window

14:00

18:30

2 hours

❌ Not counted

Step 3: Who

In Who, choose which subscribers should receive the campaign.

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.

Advanced

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

Advanced Users Options

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.

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

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.

Step 4: When

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.

Start Sending Messages

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.

Delivery Speed

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.

Message Expire Time

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.

Last updated

Was this helpful?