Skip to main content
Follow these tests to verify that your Notifly Client SDK integration works.

1. Register a user and send events

1. Set the user ID

The SDK creates an anonymous user if you do not set a user ID. Call setUserId with the ID your app uses for that user so Notifly can identify them consistently.

2. Set user properties

Call setUserProperties to set the user’s properties.

3. Send events

  • Use the Notifly SDK’s trackEvent method to send user actions, such as page views and clicks, as events.

2. Verify the user and events

  1. Sign in to Notifly.
  2. In the upper-right corner, check that the selected development or production project contains the test user.
  3. Go to User Management > User List.
  4. Select the test user and check the following on the user profile page.
    • The user ID is registered.
    • User properties such as $email and $phone_number have the expected values.
    • The event log contains the events that you sent.
Example user list User list Example user profile User profile Example event log User event log

3. Test app push notifications

If you are testing push notifications on iOS, use a physical device.
  1. In the console, open the campaign creation page.
  2. In the tabs in the upper-right corner, select the project that contains the test user.
  3. Under Basic Information and Channel, select App Push.
  4. Under Message and Action, write the push message.
    • Enter the notification title in Message Title.
    • Enter the notification text in Message Content.
    • Under Action, enter the URL or deep link to open when the user taps the notification.
      • Test the tap action when the app is in the foreground, in the background, and terminated.
App push message settings
  1. Click Send Test in the lower-right corner. In the Test Send dialog, enter the test user ID under Recipients and click Send.
The device images below illustrate how an app push, an in-app popup, and a web push can appear. Illustration of an app push test notification The test is complete when the device receives the push notification.

4. Test in-app popups

Notifly automatically logs internal events such as notifly__session_start. Use this event to test whether an in-app popup appears.

1. Create an in-app popup template

  1. Open the in-app popup editor.
  2. Select a template and configure Image, Text, Button, and Design.
    • In Button, you must enter the destination link for main_button.
Create an in-app popup template
  1. Click Save, enter a template name, and save the template.
Save an in-app popup template

2. Create a test campaign

  1. Open the campaign creation page.
  2. Select the development or production project that contains the test user.
  3. Under Basic Information and Channel, configure the following.
    • Enter a campaign name.
    • Select In-App Popup as the channel.
  4. Under Delivery Timing, configure the following.
    • Select Event-Based Send.
    • Turn on Send Indefinitely.
    • Enter notifly__session_start as the event.
    • Under Delay After Event Occurrence, select Immediately after event occurrence.
Campaign basics and send time
  1. Under Delivery Target, enable Test Mode and enter the test user ID.
Campaign test mode
  1. Under Message and Action, select the in-app popup template that you created in step 1.
Campaign message and action settings Select an in-app popup template
  1. Review the final settings and create the campaign.
Review and create the campaign

3. Check the message on the test device

  1. Fully terminate the app on the device registered with the test user ID.
  2. Open the app to trigger notifly__session_start.
  3. Check that the in-app popup appears.
Illustration of an in-app popup on a test device If the message does not appear immediately, the new campaign may still be syncing. Restart the app and check again. The in-app popup test is complete when the message appears.

5. Test web push notifications

1. Send a test message

  1. In the console, open the campaign creation page.
  2. In the tabs in the upper-right corner, select the project that contains the test user.
  3. Under Basic Information and Channel, select Web Push.
  4. Under Message and Action, write the push message.
    • Enter the notification title in Message Title.
    • Enter the notification text in Message Content.
    • Under Action, enter the URL to open when the user clicks the notification.
      • Test both the foreground and background states.
Web push message settings
  1. Click Send Test in the lower-right corner. In the Test Send dialog, enter the test user ID under Recipients and click Send. The console displays “Test send completed successfully.”
Illustration of a web push test notification The test is complete when the browser receives the web push notification.

2. Troubleshoot delivery

If web push notifications do not arrive, check these common causes.
On macOS and Windows, allow notifications for the browser in the operating system settings.Example on macOS.Browser notification permissions in macOS settings
Browsers request notification permission differently. Check that notifications are allowed.Example in Chrome.Notification permission allowed in ChromeExample in Edge.Notification permission blocked in EdgeThe browser’s permission prompt may not appear automatically, depending on your Notifly JavaScript SDK configuration. For details, see Register a Service Worker in the JavaScript SDK guide.

Browser version

Notifly uses the Web Push Protocol. See Push API browser compatibility for supported browsers.For example, desktop Safari 15 and earlier do not support standards-based web push notifications.
Contact the Notifly team if you have other questions.