How to Create an Automated Web Push Campaign

Automated campaigns are messages sent to a customer from a flow or operation when a specific event occurs. This guide walks you through every setting you need to configure to launch an automated web push campaign in Maestra.

​

In this article

• Add a campaign
• Campaign settings
  • Campaign name
  • Web push
  • Test send
  • General settings
  • Send restrictions
  • UTM tags
• After filling in settings
  • Readiness to send
• A/B test and control group

​

Add a campaign

To create an automated web push campaign:

1. Go to the Campaigns section.
2. Click Create campaign → Automation → Automated campaign.
3. Select the Web push channel, choose a folder, and click Create.

​

Campaign settings

​

Campaign name

The name helps you find the campaign among other campaigns and apply project filters. Pick something descriptive so the campaign is easy to identify later.

​

Web push

Fill in the content of the web push:

• Site — the integration point of type “Website” that the push will be tied to.
• Title, text, and redirect link — mandatory fields.
• Hide push — automatically removes the push from the screen without the customer clicking the close button.
• Optional fields: image, thumbnail, app icon for mobile browsers, and buttons.

You can use templating parameters and emojis inside the title, text, and other content fields.

​

Test send

Once the Web push section is filled in, you can preview the formatted push as a specific user would see it. During a test send, the selected customer actually receives the push in their browser. Test sends can only be delivered to devices that are already in the database. To add a device, visit the site and allow push notifications so the subscription is registered in the project. To run a test send:

1. Click Test send.
2. Select customers from the list, or add new ones.
3. Click Send to selected.

Test sends are not recorded in the customer profile. You can view their statuses through the provided link. To view the formatted message without sending it to the customer’s browser, click Preview.

​

General settings

• Brand — relevant for multi-brand projects.
• Topic — splitting campaigns into topics lets customers set flexible subscription preferences and receive communications only on topics they are interested in.
• Tags — action tags group campaigns by additional criteria when channel, topic, and folder divisions aren’t enough.
• Profile — defines the campaign type and which recipient restrictions apply or are skipped based on the selected profile:
  • Standard — for marketing campaigns. The basic recipient checks apply:
    • The customer has granted permission to show pushes on the selected site.
    • The customer is subscribed to the Web Push channel (or to a topic within Web Push, if one is specified).
    • The customer is not in the global control group (if enabled) — don’t confuse this with the campaign control group.
    • The frequency limit hasn’t been exceeded (if enabled).
    Any of these checks can be disabled inside the campaign using toggles.
  • Transactional — a campaign that the customer has requested and expects to receive immediately. None of the standard checks apply.

​

Send restrictions

• Send hours — limit sending by the customer’s timezone or the project’s timezone.
• Relevance — the time period during which sending the message still makes sense. Can be tied to the send time or set manually.

​

UTM tags

UTM tags identify the traffic source to your website and attribute traffic to a specific campaign and channel. You can create standard tags and reuse them across web push campaigns, or enter custom tags for a single campaign.

​

After filling in settings

​

Readiness to send

This section automatically checks that all required fields are filled in. Click any item in the checklist to jump to the corresponding section. When everything is filled in, the campaign moves from Draft to Ready to send. To use the campaign in flows and operations, change its status to Ready to use by clicking Finish editing.

​

A/B test and control group

• A/B tests let you compare different variants of a campaign by their impact on opens, clicks, and revenue.
• Control group (CG) measures the campaign’s effectiveness by comparing the behavior of customers who received the message with the behavior of customers who didn’t.

Available evaluation metrics for web pushes:

• Click rate — the percentage of customers who made at least one click during the test (available without a control group comparison only).
• Target action — a specific action completed by the customer during the test.

For details on configuring experiments, see the full A/B testing guide for automated campaigns.