Default Events

Out-of-the-box events for any industry and use case

Available starting from SDK 5.2.2

What are Default Events?

Default Events are basic interactions that users perform in apps or websites regardless of their industry or functionality. These key user actions form the core of customer communication and can be leveraged for any product and customer at any stage of the customer lifecycle.

Default Events are available out of the box for up-to-date SDK versions and don't need additional settings (except for PW_InAppPurchase, see the details below).

To find and activate the Default Events available in Pushwoosh, follow these steps:

1. Navigate to the Events tab within the Audience section.

2. Click Create Event.

3. Select Default Event from the drop-down menu.

4. In the pop-up window, choose the desired event and click Activate.

Activating Default Event

Once activated, Default Events can be used in behavior-based messaging, for example, as a Trigger-based Entry in Customer Journey or a trigger for In-App messages.

PW_DeviceRegistered

For mobile apps only

This Event is fired only once for each device, upon the first-time app launch and the SDK initialization. As the name suggests, this Event tracks device registration in your app.

Use cases:

• Launch an onboarding campaign for newly registered users – add the Trigger-based Entry using PW_DeviceRegistered Event to an Onboarding Customer Journey.

• Identify acquisition activities that bring you more newcomers with the Event statistics.

• Engage users right at their first visit: meet them with In-Apps triggered by the DeviceRegistered Event.

Event-triggered In-App

PW_DeviceUnregistered

For mobile apps only

This Event fires when the app is uninstalled, or a user opts out of emails or push notifications.

Event attributes:

• message_id (string)

• message_code (string)

• campaign_id (string)

Use cases:

• Retain users when they decide to stop using your app. For example, you can send an email with a special offer to every user who has uninstalled the app.

• Maintain communication with users who have unsubscribed from one of your channels. For example, if a user doesn't want to receive push notifications anymore, you can send an email or show an in-app encouraging them to use the app more often.

PW_ApplicationOpen

For mobile apps only

ApplicationOpen Event is triggered every time a user launches your mobile app on their device.

Event attributes:

• device_type (integer device type code, refer to registerDevice for details)

• application_version

Use cases:

• Gather user retention stats based on the ApplicationOpen event statistics.

• Run in-app messaging campaigns for users who are active in the app.

PW_ScreenOpen

For mobile apps only

This Event is fired every time a user views a specific screen in your mobile app.

Event attributes:

• application_version

• device_type (integer device type code, refer to registerDevice for details)

• screen_name (tech screen name obtained from your app)

Use cases:

• Send perfectly relevant messages to users who showed their interest in specific app sections by starting Customer Journeys with the PW_ScreenOpen event.

• Evaluate & elevate effectiveness of your promotions: A/B/n test two or several versions of your offer, wait for the ScreenOpen event to take place and then see which content has perfomed best.

• Get to know what app screens are visited the most: filter the Event statistics by screen name.

Event stats filtered by screen name

PW_ApplicationMinimized

For mobile apps only

This Event is fired when a user minimizes (but not force stops) the app on their device.

Event attributes:

• device_type (integer device type code, refer to registerDevice for details)

• application_version

Use cases:

• Track the average session time between ApplicationOpen and ApplicationMinimized events.

• Send pushes while the app runs in the background to grab users' attention and return them to the app.

PW_SiteOpened

For web platforms only

The SiteOpened Event is fired every time a user opens any of your website pages.

Event attributes

• device_type (integer device type code, refer to registerDevice for details)

• title – the title of the page visited

• url – URL of the page visited

Use cases:

• Analyze your site traffic distribution and comparing the number of times users open specific site pages. For this, filter the Event stats by its attributes.

• Follow up on a user's website visit by a relevant communication: build a journey starting with the SiteOpened Event set up for a specific 'title' or 'url' attribute.

PW_InAppPurchase

For mobile apps only

The InAppPurchase Event is fired every time a user purchases an in-app item in your app, for example, a paid subscription, game mechanics elements, in-app currency, etc.

Please keep in mind these items must be specified on your app's App Store page.

To implement the In-App Purchase event:

• For iOS:

  • activate the PW_InAppPurchase Event in your Control Panel;

  • set the Pushwoosh_PURCHASE_TRACKING_ENABLED param of the Pushwoosh iOS SDK to 'yes'.

• For Android:

  • activate the PW_InAppPurchase Event in your Control Panel;

  • configure sending purchase information to Pushwoosh using this guide.

Event attributes:

• productIdentifier (obtained from the App Store)

• quantity – the number of items purchased

• transactionDate – date of purchase

• status – status of purchase

Use cases:

• Gather stats of in-app purchases.

• Run promotions and keep track of their success: set the Wait for Trigger event following the promo message.

Wait for In-App Purchase

PW_NotificationOpen

For mobile and web platforms

This Event is fired every time a user opens a push notification sent with Pushwoosh.

Use cases:

• Configure the optimal time to send a push.

• Create Segments based on notifications performance within a specific time period.

PW_NotificationSend

For mobile and web platforms

This Event is fired once a Pushwoosh message is sent to a user's device.

Event attributes:

• message_id (string)

• message_code (string)

• campaign_id (string)

Use cases:

• Track whether a message is sent, regardless of the channel used.

• Create user Segments based on the number of messages sent.

• View all messages sent to a user in the Events history and analyze the user's further behavior.

PW_EmailLinkClicked

For email platform only

This Event fires every time a user clicks a link in an email.

Event attributes:

• message_id (string)

• message_code (string)

• campaign_id (string)

• redirect_link (string)

• original_link (string)

Use cases:

• Run targeted campaigns for users who click on a specific link in an email.

• Send another message to users who ignored the link in the first email to encourage them to click on it (or take other action).