Pushwoosh glossary
Missing a definition? Just send us a message and weâll add it to the list.
API-Based Entry
Section titled âAPI-Based EntryâAn entry block in the Customer Journey tool that allows you to launch a journey when specific events occur outside the app, such as an item returning to stock (typically tracked in the internal database).
Application
Section titled âApplicationâA mobile app or website that is registered with the Pushwoosh platform. A registered Application enables you to send push notifications, in-app messages, emails, and SMS messages to your users through Pushwoosh. Each Application has its unique settings, segments, and user data.
Application Code
Section titled âApplication CodeâA unique identifier associated with your mobile application or website within the Pushwoosh platform.
Audience
Section titled âAudienceâUsers who are intended to receive a particular push notification, email, or in-app message that you send through Pushwoosh. In marketing terms, a target segment.
Audience-Based Entry
Section titled âAudience-Based EntryâAn entry block in the Customer Journey Builder tool that automatically initiates journeys by enrolling users who meet specific criteria into pre-configured sequences of interactions. This approach leverages established segments of your appâs user base, ensuring relevant journeys are triggered only for the most appropriate audience.
Average Monetary Values (AMV)
Section titled âAverage Monetary Values (AMV)âThe average spend for each user in the segment, being that money, time, or any other countable metric.
Behavior-Based Messaging
Section titled âBehavior-Based MessagingâMessages targeted to specific segments of your audience based on user behavior and preferences.
Channel
Section titled âChannelâA specific communication medium through which you can deliver messages to your users. Pushwoosh supports various channels, including push notifications, in-app messages, emails, SMS, and WhatsApp.
Control Panel
Section titled âControl PanelâAn admin panel for using Pushwoosh features in the user interface. It allows you to create and send notifications, track user engagement, customize settings, and optimize your campaigns for success.
Conversion
Section titled âConversionâAny target action a user takes, like a purchase or sign-up, that aligns with your campaign goals.
Conversion Funnel
Section titled âConversion FunnelâA visual representation of the user journey that allows tracking conversion rates at each stage after a push notification.
Conversion Goal
Section titled âConversion GoalâA specific action or outcome that marks the successful completion of a customer journey.
Conversion Tracking
Section titled âConversion TrackingâA feature that presents data about how often users perform desired actions after receiving a push.
Custom Rich Media
Section titled âCustom Rich MediaâA deeply customizable HTML page containing images, videos, buttons, and other media content.
Custom Tags
Section titled âCustom TagsâTags that serve as a way to store user attributes and can be created based on the segmentation logic or targeting pattern that is appropriate for your unique business needs.
Learn more
Customer Journey
Section titled âCustomer JourneyâA campaign that uses communication to guide users through a series of interactions and influence their behavior toward a desired outcome.
Customer Journey Builder
Section titled âCustomer Journey BuilderâA tool for creating automated cross-channel campaigns. It allows you to keep track of user behavior and send relevant behavior-triggered and scheduled messages to your customers at every stage of their lifecycle.
Deep Link
Section titled âDeep LinkâA type of link that allows you to open a specified section and resources of your application once a user taps on a push notification, in-app, or email.
Default Tags
Section titled âDefault TagsâSome non-personal data about the end userâs device that is collected by Pushwoosh SDK by default (no integration required). This allows addressing some basic segmentation and lifecycle scenarios (e.g., Last Application open date to launch reactivation campaigns, Push Alerts Enabled (true/false) for opt-out recovery campaigns, App version â if you want users to update from the older versions)
Device Push Token
Section titled âDevice Push TokenâA unique key for the app-device combination issued by the Apple or Google push notification gateways. It allows gateways and push notification providers to route messages and ensure the notification is delivered to the unique app-device combination for which it is intended.
Dynamic Content
Section titled âDynamic ContentâPlaceholders within push content (body, title) that are automatically filled with tag values for content personalization.
Email Content
Section titled âEmail ContentâAn email layout that contains textual and multimedia elements, as well as email settings, which you can use to create and launch your email campaigns quickly and easily.
Email Editors
Section titled âEmail EditorsâA Drag & Drop Email Editor, which allows you to design emails easily without coding or design skills, and an HTML Code Editor for those proficient in HTML who prefer to write their own code. Both tools offer a range of content elements and layouts to help you quickly and effectively create and launch email campaigns.
Any user activity within the app, website, or backend system. They can be used in segmentation and as triggers for behavior-based messaging.
Global Frequency Capping
Section titled âGlobal Frequency CappingâThis feature that limits the number of messages a user receives within a specific timeframe. Once the message limit is reached for a channel, no further messages will be sent until the period resets.
High-Priority In-App
Section titled âHigh-Priority In-AppâA setting in Pushwoosh that ensures that in-app messages are displayed promptly, even if the Pushwoosh SDK is still downloading the message content. When this setting is enabled, the SDK will temporarily block the appâs UI for a few seconds while the message is being downloaded, ensuring that users see the message as soon as possible.
High-Speed Delivery Segments
Section titled âHigh-Speed Delivery SegmentsâOptimized user segments that are pre-calculated and updated every 10 minutes to ensure rapid message delivery. This feature eliminates the need for real-time segment recalculation when sending messages, minimizing latency and ensuring that messages reach the target audience promptly. This optimization is especially useful for large databases (e.g., those exceeding 1 million) and time-sensitive push notifications.
HWID (or Hardware ID)
Section titled âHWID (or Hardware ID)âA key identifier assigned to the device by Pushwoosh SDK.
In-App Messages
Section titled âIn-App MessagesâCustomizable HTML pages that can be displayed to app users within the app.
Journey Assistant
Section titled âJourney AssistantâA feature in Pushwoosh Customer Journey Builder that works as an automated campaign checker. It takes users through a basic journey-launch checklist, validating a campaign or suggesting any steps that might be missing.
Liquid Templates
Section titled âLiquid TemplatesâA syntax that allows populating dynamic placeholders in the content templates based on logical expressions.
E.g. {% if Language == âfrâ %}
Salut!
{% else %}
Hello!
{% endif %}â
Message History
Section titled âMessage HistoryâA section that shows the detailed statistics on each message sent. You can easily find information on a specific message using filters by campaign name, text, notification ID, or notification code.
Message Inbox (also known as Message Center or App Inbox)
Section titled âMessage Inbox (also known as Message Center or App Inbox)âAn extra communication channel allowing you to save push notification messages of your choice in a dedicated section within your app. There, the messages will stay available for users to read and take action during the time you specify. Also, you can deliver messages to the inbox even if a user has disabled push notifications. This functionality provides users with the flexibility to consider your special offers at their convenience and, thus, increases chances for higher engagement and conversion rates.
Mobile Push Notification
Section titled âMobile Push NotificationâA short message sent from a mobile app instantly, on a specified schedule, or upon a user-triggered event. It can only be delivered to opted-in users â then, it will appear on their mobile deviceâs screen.
Multi-Language Messaging
Section titled âMulti-Language MessagingâA feature that allows delivering the same message with different content depending on the deviceâs locale settings.
Multi-language Push Notifications
Section titled âMulti-language Push NotificationsâA feature that allows delivering the same message with different content depending on device locale settings. Pushwoosh suggests popular languages from your database, allowing you to create several versions of your text to overcome language barriers, ideal for multi-national apps.
Multi-Login Accounts
Section titled âMulti-Login AccountsâA feature within Pushwoosh that enables multiple team members to access and manage a single Pushwoosh account simultaneously.
No-Code In-App Editor
Section titled âNo-Code In-App EditorâA drag-and-drop tool that empowers users with no coding skills to create and customize in-app message content. The tool features various options for copy editing and visual design, such as built-in stock photo search and AI image generation. It also supports personalization methods, ensuring that messages resonate with target audiences.
Project
Section titled âProjectâA central organizational unit that encompasses all the settings and configurations related to a specific mobile or web application. Itâs a workspace for managing various aspects of your appâs communication and engagement strategy with users.
Project Overview Report
Section titled âProject Overview ReportâA dashboard where you can analyze your marketing campaignsâ performance with comprehensive stats for your entire project.
Push-Enabled Device
Section titled âPush-Enabled DeviceâA device with a valid push token that can receive notifications. On mobile devices, users can ban the display (rendering) of push notifications on the lock screen in the app-specific OS settings, however, such devices are still considered push-enabled because the token is preserved, and they can receive silent notifications (sent to the app inbox, containing custom data, etc.)
Push Token
Section titled âPush TokenâA unique key for the app-device combination issued by the Apple or Google push notification gateways. It allows gateways and push notification providers to route messages and ensure the notification is delivered to the unique app-device combination for which it is intended.
Pushwoosh
Section titled âPushwooshâAn omnichannel customer engagement platform allowing businesses to communicate with their end customers through mobile and web channels: mobile and web push notifications, in-app messages, emails, SMS, and WhatsApp. In addition to messaging, Pushwoosh serves as a customer data platform, providing features for audience segmentation and performance analytics.
Pushwoosh AI Composer
Section titled âPushwoosh AI ComposerâAn AI tool that generates engaging, high-quality copy for push notifications based on the keywords you specify.
Pushwoosh API
Section titled âPushwoosh APIâA set of publicly accessible methods to communicate to Pushwoosh to send messages, track usersâ behaviors, gain statistics, etc.
Reachable by In-App
Section titled âReachable by In-AppâAll devices that meet the Segment conditions, including those with push notifications disabled. You can show in-apps on all these devices, while some of them may be unavailable for push notifications.
Reachable by Push
Section titled âReachable by PushâDevices with push notifications enabled, including those that can only receive silent pushes. These devices are also available for displaying in-app messages.
Recipients
Section titled âRecipientsâUsers who have given permission to receive messages (push or email) and whom you can reach with your communication.
RFM Segmentation / (Recency, Frequency, Monetary) Segmentation
Section titled âRFM Segmentation / (Recency, Frequency, Monetary) SegmentationâAn analytics tool in Pushwoosh that allows you to segment your audience based on the Recency, Frequency, and Monetary criteria. The values are assigned upon user behavior tracked as triggered events. The tool can also be used for RF (non-monetary) segmentation, which is relevant for subscription-based or hybrid apps monitoring user engagement and retention metrics.
RFM Tags
Section titled âRFM TagsâA set of tags that store and categorize user data based on their Recency, Frequency, and Monetary value (RFM). These tags are used to create targeted segments of users for personalized messaging campaigns.
Segment
Section titled âSegmentâA cohort of app or web users complying with your specified conditions â assigned tagsâ values (user attributes) and/or triggered events (user behavior).
Send Rate Limit
Section titled âSend Rate LimitâA feature that allows you to restrain the push-sending speed. That means Pushwoosh will send no more than the specified number of messages in a second. Please note the available values are from 100 to 1000 pushes per second.
Scheduled Launch
Section titled âScheduled LaunchâAn automated start of a journey, either at regular intervals or pre-defined dates and times. This ensures your journeys are delivered at the optimal moment for each user, based on their time zone and any relevant segment updates.
Silent Hours
Section titled âSilent HoursâA feature that allows defining a do-not-disturb period during which no notifications or emails are sent to users.
Silent Push Notification
Section titled âSilent Push NotificationâA push that is not visible or audible to the user and allows passing some data to the app, updating the app in the background, or getting new data from your server without having users informed. Silent push notifications are delivered to usersâ devices with no alert, sound, or icon badge. When a silent push arrives, the app is woken up in the background. Users are not notified of any alerts and donât see any push content.
A way to store information about users based on their characteristics, preferences, and behavior.
Tag Operator
Section titled âTag OperatorâA logical operator that defines the relationship between the Tag and its values for segmentation purposes.
Tag Value
Section titled âTag ValueâA specific piece of information stored within a tag that helps make push campaigns more targeted or personalized.
Time Delay
Section titled âTime DelayâAn element of a Customer Journey that pauses the userâs progress for a specified duration before proceeding to the next step. This delay can be set to a fixed period, a specific time, a particular date and day of the week, or dynamically determined based on a user tag value or event attribute.
Trigger-Based Entry
Section titled âTrigger-Based EntryâAn entry block inside the Customer Journey Builder tool. It contains an event that a user should trigger to start the journey.
User Explorer
Section titled âUser ExplorerâA tool that provides in-depth insights into individual user or device data. It enables you to delve into various aspects of user behavior, including device usage, message interactions, and overall engagement patterns.
User ID
Section titled âUser IDâAs opposed to the HWID (Hardware ID), a user ID defines the user of the device. By default, it is equal to HWID but can be overridden with the /registerUser API (often called when a user logs into the app). Multiple devices (HWIDs) can be united under a single User ID.
Web Push Notifications
Section titled âWeb Push NotificationsâClickable push messages you receive in your web browser or mobile browser.