Pushwoosh (Actions) Destination

Pushwoosh is a customer engagement platform that lets you create personalized messaging campaigns combining multiple channels, like push notifications, in-app messages, emails, and SMS.

Pushwoosh maintains this destination. For any issues with the destination, contact the Pushwoosh support team.

Getting started

Pushwoosh SDK integration

• If you configured Segment to receive push tokens, you don’t need to integrate the Pushwoosh SDK into your app.
• If your Segment implementation doesn’t receive push tokens, integrate the Pushwoosh SDK into your app before setting up the Pushwoosh integration.

Segment configuration

1. From the Segment web app, navigate to Connections > Destinations, and click Add Destination.
2. Search for Pushwoosh and select it as the destination.
3. Choose the sources you want to connect the Pushwoosh destination to.
4. Open the destination settings.
5. Enter your Pushwoosh API key and application code, which you can find below the project name in Pushwoosh. Verify that the Enable Destination switch is toggled on, then click Save Changes.
6. Go to the Mappings tab and verify that the Create or Update User Profile and Track Events options are enabled.

Once you’ve configured the integration, Pushwoosh will receive events and user attributes from Segment.

Destination Settings

Available Presets

Pushwoosh has the following presets:

Available Actions

Build your own Mappings. Combine supported triggers with the following Pushwoosh-supported actions:

• Create or Update User Profiles

• Track Event

Create or Update User Profiles

Create or Update a user’s profile attributes in Pushwoosh.

Create or Update User Profiles is a Cloud action. The default Trigger is: type = "identify"

Click to show / hide fields

Track Event

Record custom events in Pushwoosh

Track Event is a Cloud action. The default Trigger is: type = "track" or type = "page" or type = "screen"

Click to show / hide fields

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.