All guides
User

Web Push Campaigns

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/web-push/campaigns on your site.

Steps

Use Save A/B test

  1. Open /portal/web-push/campaigns/ab-test on your application domain, using the workspace account for this task.
  2. Find the form containing Campaign, Title, Body. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save A/B test. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
CampaignRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
TitleComplete the visible field for the current selection; follow its validation message.
BodyComplete the visible field for the current selection; follow its validation message.
Click URLComplete the visible field for the current selection; follow its validation message.
Variant A traffic (%)Required. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 10. Maximum 90.
Winning metricRequired. Choose Click rate, Conversion rate.
Minimum deliveries per variantRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 20. Maximum 100000.

Use Use Variant A

  1. Open /portal/web-push/campaigns/ab-test on your application domain, using the workspace account for this task.
  2. Find the form containing Campaign, Title, Body. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Use Variant A. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
CampaignEnter the campaign for this task, using the help or example shown by the form.
TitleComplete the visible field for the current selection; follow its validation message.
BodyComplete the visible field for the current selection; follow its validation message.
Click URLComplete the visible field for the current selection; follow its validation message.
Variant A traffic (%)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 10. Maximum 90.
Winning metricChoose Click rate, Conversion rate.
Minimum deliveries per variantEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 20.

Use Engagement score: :score

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Campaign name, Audience segment. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Engagement score: :score. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteEnter the site for this task, using the help or example shown by the form.
Campaign nameEnter the campaign name for this task, using the help or example shown by the form. Internal name used to find this campaign later.
Audience segmentEnter the audience segment for this task, using the help or example shown by the form. Leave empty to target all active subscribers on this site.
Notification topicChoose General, Updates, Offers, Alerts. Only subscribers who enabled this topic will receive the campaign.
Notification titleEnter the notification title for this task, using the help or example shown by the form.
MessageEnter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews.
Click URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification.
TitleComplete the visible field for the current selection; follow its validation message.
MessageComplete the visible field for the current selection; follow its validation message.
DeliveryChoose Save as draft, Send now, Schedule.
Scheduled timeEnter the scheduled time for this task, using the help or example shown by the form. Required when delivery is scheduled.
Repeat scheduleChoose Every day, Every week, Every month.
Repeat until (optional)Enter the repeat until (optional) for this task, using the help or example shown by the form.
Scheduled delivery timingChoose Send at the selected workspace time, Deliver at each subscriber local time.
Local hour (0–23)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Subscribers with a detected timezone are queued when this hour begins locally. Others use the selected workspace time. Minimum 0. Maximum 23.

Use Send test

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Test recipient, Notification title. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Send test. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
Test recipientRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
Notification titleRequired. Enter the notification title for this task, using the help or example shown by the form. Maximum 120 characters.
MessageRequired. Enter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews. Maximum 5000 characters.
Click URLOptional unless the current form requests it. Enter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification. Maximum 2048 characters.

Use Review current draft

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Campaign name, Audience segment. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Review current draft. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteEnter the site for this task, using the help or example shown by the form.
Campaign nameEnter the campaign name for this task, using the help or example shown by the form. Internal name used to find this campaign later.
Audience segmentEnter the audience segment for this task, using the help or example shown by the form. Leave empty to target all active subscribers on this site.
Notification topicChoose General, Updates, Offers, Alerts. Only subscribers who enabled this topic will receive the campaign.
ToneChoose Professional, Friendly, Urgent, Playful.
LanguageChoose Vietnamese, English.
Notification titleEnter the notification title for this task, using the help or example shown by the form.
MessageEnter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews.
Click URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification.
TitleComplete the visible field for the current selection; follow its validation message.
MessageComplete the visible field for the current selection; follow its validation message.
DeliveryChoose Save as draft, Send now, Schedule.
Scheduled timeEnter the scheduled time for this task, using the help or example shown by the form. Required when delivery is scheduled.
Repeat scheduleChoose Every day, Every week, Every month.
Repeat until (optional)Enter the repeat until (optional) for this task, using the help or example shown by the form.
Scheduled delivery timingChoose Send at the selected workspace time, Deliver at each subscriber local time.
Local hour (0–23)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Subscribers with a detected timezone are queued when this hour begins locally. Others use the selected workspace time. Minimum 0. Maximum 23.

Use Generate

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Campaign name, Audience segment. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Generate. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteEnter the site for this task, using the help or example shown by the form.
Campaign nameEnter the campaign name for this task, using the help or example shown by the form. Internal name used to find this campaign later.
Audience segmentEnter the audience segment for this task, using the help or example shown by the form. Leave empty to target all active subscribers on this site.
Notification topicChoose General, Updates, Offers, Alerts. Only subscribers who enabled this topic will receive the campaign.
Campaign goal or offerRequired. Enter the campaign goal or offer for this task, using the help or example shown by the form. The form’s example is Example: Announce 20% off annual plans before Friday, including the key benefit and destination.. Replace it with your own value. Maximum 2000 characters.
ToneChoose Professional, Friendly, Urgent, Playful.
LanguageChoose Vietnamese, English.
Notification titleEnter the notification title for this task, using the help or example shown by the form.
MessageEnter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews.
Click URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification.
TitleComplete the visible field for the current selection; follow its validation message.
MessageComplete the visible field for the current selection; follow its validation message.
DeliveryChoose Save as draft, Send now, Schedule.
Scheduled timeEnter the scheduled time for this task, using the help or example shown by the form. Required when delivery is scheduled.
Repeat scheduleChoose Every day, Every week, Every month.
Repeat until (optional)Enter the repeat until (optional) for this task, using the help or example shown by the form.
Scheduled delivery timingChoose Send at the selected workspace time, Deliver at each subscriber local time.
Local hour (0–23)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Subscribers with a detected timezone are queued when this hour begins locally. Others use the selected workspace time. Minimum 0. Maximum 23.

Use Use this draft

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Campaign name, Audience segment. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Use this draft. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteEnter the site for this task, using the help or example shown by the form.
Campaign nameEnter the campaign name for this task, using the help or example shown by the form. Internal name used to find this campaign later.
Audience segmentEnter the audience segment for this task, using the help or example shown by the form. Leave empty to target all active subscribers on this site.
Notification topicChoose General, Updates, Offers, Alerts. Only subscribers who enabled this topic will receive the campaign.
Notification titleEnter the notification title for this task, using the help or example shown by the form.
MessageEnter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews.
Click URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification.
TitleComplete the visible field for the current selection; follow its validation message.
MessageComplete the visible field for the current selection; follow its validation message.
DeliveryChoose Save as draft, Send now, Schedule.
Scheduled timeEnter the scheduled time for this task, using the help or example shown by the form. Required when delivery is scheduled.
Repeat scheduleChoose Every day, Every week, Every month.
Repeat until (optional)Enter the repeat until (optional) for this task, using the help or example shown by the form.
Scheduled delivery timingChoose Send at the selected workspace time, Deliver at each subscriber local time.
Local hour (0–23)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Subscribers with a detected timezone are queued when this hour begins locally. Others use the selected workspace time. Minimum 0. Maximum 23.

Use Add language

  1. Open /portal/web-push/campaigns/create on your application domain, using the workspace account for this task.
  2. Find the form containing Site, Campaign name, Audience segment. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Add language. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
SiteEnter the site for this task, using the help or example shown by the form.
Campaign nameEnter the campaign name for this task, using the help or example shown by the form. Internal name used to find this campaign later.
Audience segmentEnter the audience segment for this task, using the help or example shown by the form. Leave empty to target all active subscribers on this site.
Notification topicChoose General, Updates, Offers, Alerts. Only subscribers who enabled this topic will receive the campaign.
Notification titleEnter the notification title for this task, using the help or example shown by the form.
MessageEnter the message for this task, using the help or example shown by the form. Keep the message concise for browser previews.
Click URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Where subscribers go when they open the notification.
TitleComplete the visible field for the current selection; follow its validation message.
MessageComplete the visible field for the current selection; follow its validation message.
DeliveryChoose Save as draft, Send now, Schedule.
Scheduled timeEnter the scheduled time for this task, using the help or example shown by the form. Required when delivery is scheduled.
Repeat scheduleChoose Every day, Every week, Every month.
Repeat until (optional)Enter the repeat until (optional) for this task, using the help or example shown by the form.
Scheduled delivery timingChoose Send at the selected workspace time, Deliver at each subscriber local time.
Local hour (0–23)Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Subscribers with a detected timezone are queued when this hour begins locally. Others use the selected workspace time. Minimum 0. Maximum 23.

Create or update: Export CSV / Exporting...

  1. Open /portal/web-push/deliveries on your application domain, using the workspace account for this task.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Use the button shown for the current state: Export CSV, Exporting.... Creation and editing can show different labels; submit the form once.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Use Submit for review

  1. Open /portal/web-push/campaigns and select the record you want to work with. Its detail/edit address follows /portal/web-push/campaigns/{campaign}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Find the form containing Review note. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Submit for review. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Review noteEnter the review note for this task, using the help or example shown by the form.

Use Approve

  1. Open /portal/web-push/campaigns and select the record you want to work with. Its detail/edit address follows /portal/web-push/campaigns/{campaign}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Find the form containing Review note. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Approve. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Review noteEnter the review note for this task, using the help or example shown by the form.

Use Request changes

  1. Open /portal/web-push/campaigns and select the record you want to work with. Its detail/edit address follows /portal/web-push/campaigns/{campaign}. Use the application’s record link; do not type a placeholder such as {id}.
  2. Find the form containing Review note. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Request changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Review noteEnter the review note for this task, using the help or example shown by the form.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information
MethodSource-default route
GET/portal/web-push/campaigns
GET/portal/web-push/analytics/export
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
form.site_idmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.segment_idmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.topicmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.namemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.titlemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.bodymodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.icon_urlmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.image_urlmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.click_urlmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.send_modemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.scheduled_atmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.send_time_modemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.send_time_hourmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.recurrencemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.recurrence_untilmodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.localizations.*.localemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.localizations.*.titlemodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php
form.localizations.*.bodymodules/WebPush/WebPushCampaigns/Livewire/CampaignsIndex.php