In this Help Center article, you'll learn how to connect OneSignal as a destination in GrowthLoop and use it to trigger templated push notifications from journeys.

Prerequisites

Before you begin, make sure you have the following in place:

• A OneSignal account and app. If you need to create one, visit OneSignal.
• Your OneSignal App ID and App API Key. In OneSignal, you can find these under Settings > Keys & IDs for your app.
• At least one push template created in OneSignal.
• A field in your dataset or realtime event payload that stores a valid OneSignal Subscription ID for each user you want to message.

Set up destination

1. In GrowthLoop, navigate to the Destinations tab from the left sidebar and click New Destination.

2. Search for OneSignal in the destination modal and click Add OneSignal.

3. In the destination setup modal, enter the following information:

   1. Destination Name: The name your team will see in GrowthLoop when selecting this destination.
   2. Sync Frequency: The default sync cadence for this destination. Marketers can adjust this later when configuring exports or journeys.
   3. App ID: Your OneSignal App ID.
   4. App API Key: Your OneSignal App API Key.

4. Click Create.

GrowthLoop validates the destination by connecting to OneSignal and loading the templates available for the configured app.

Use OneSignal in a journey

Once your destination is connected, you can use it in a journey to send push notifications.

1. Create a new journey or open an existing journey in GrowthLoop.

2. Drag a Destination node onto the canvas and select your OneSignal destination.

3. In the destination node configuration, choose Send Push.

4. Configure the destination node:

   1. Subscription ID: Select the field in your dataset or realtime event that contains the user's OneSignal subscription ID.
   2. Push Template: Choose the OneSignal template you want to trigger.
   3. Template Variables: Map GrowthLoop fields to any template variables required by your OneSignal template.
   4. Send Test Push: Send a test notification before publishing to confirm the template and variable mappings are correct. You'll need to provide a valid test OneSignal Subscription ID for the device that should receive the test message.

5. Save the node and publish the journey.

Every time a user reaches that destination node, GrowthLoop will call OneSignal and trigger the selected template for that user's subscription ID.

Template personalization

GrowthLoop can map fields from your dataset or realtime event into your OneSignal template.

If your template references values from message.custom_data, those variables appear in the GrowthLoop configuration screen so you can map them to warehouse or event fields.

For example, you can map fields such as:

• first_name
• order_id
• status
• campaign_name

Those values are then sent to OneSignal as template personalization data when the push notification is triggered.

Here's what a configured OneSignal destination can look like in the journey canvas:

📘

Note

Experiencing any issues when connecting to OneSignal or sending push notifications from a journey? Reach out to us at [email protected] and we'll be in touch shortly to help resolve the issue.