User

Web Push Segments

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

Choose a task

Open /portal/web-push/segments/create on your application domain, using the workspace account for this task.
Find the form containing Segment name, Site, Description. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Use the button shown for the current state: Save changes, Save segment. Creation and editing can show different labels; submit the form once.
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.

Field	What to enter or choose
Segment name	Required. Enter the segment name for this task, using the help or example shown by the form. Maximum 160 characters.
Site	Required. Choose All accessible sites.
Description	Optional unless the current form requests it. Enter the description for this task, using the help or example shown by the form. Maximum 500 characters.
Subscriber status	Required. Choose Active only, Inactive only, All subscribers.
Recent activity	Required. Choose Any last seen date, Seen in last 24 hours, Seen in last 7 days, Seen in last 30 days, Seen in last 90 days.
Field	Choose Browser, Operating system, Device, Language, Timezone, UTM source, UTM medium, UTM campaign.
Operator	Choose Equals, Does not equal, Contains, Starts with.
Value	Complete the visible field for the current selection; follow its validation message.
Segment status	Required. Choose Active, Paused.

Open /portal/web-push/segments/create on your application domain, using the workspace account for this task.
Find the form containing Segment name, Site, Description. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Add condition. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Segment name	Enter the segment name for this task, using the help or example shown by the form.
Site	Choose All accessible sites.
Description	Enter the description for this task, using the help or example shown by the form.
Subscriber status	Choose Active only, Inactive only, All subscribers.
Recent activity	Choose Any last seen date, Seen in last 24 hours, Seen in last 7 days, Seen in last 30 days, Seen in last 90 days.
Field	Choose Browser, Operating system, Device, Language, Timezone, UTM source, UTM medium, UTM campaign.
Operator	Choose Equals, Does not equal, Contains, Starts with.
Value	Complete the visible field for the current selection; follow its validation message.
Segment status	Choose Active, Paused.

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

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
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.

Problem	What to check
The screen or action is missing	Check the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read 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 empty	Check 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 pending	Check its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information

Method	Source-default route
GET	/portal/web-push/segments