Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Pushwoosh (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Pushwoosh in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

Pushwoosh(link takes you to an external page) 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

getting-started page anchor

Pushwoosh SDK integration

pushwoosh-sdk-integration page anchor
  • 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.
  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(link takes you to an external page) 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.


Property nameTypeRequiredDescription
Pushwoosh API Keypassword
required

Pushwoosh API Key from Pushwoosh Control Panel


Pushwoosh Application Codestring
required

Pushwoosh Application Code from Pushwoosh Control Panel


Pushwoosh has the following presets

Preset NameTriggerDefault Action
Track EventsEvent type = "track", Event type = "page", Event type = "screen"Track Event
Create or Update User ProfileEvent type = "identify"Create or Update User Profiles

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

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Create or Update User Profiles

create-or-update-user-profiles page anchor

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"

Property nameTypeRequiredDescription
External User IDSTRING

Optional

The unique user identifier


EmailSTRING

Optional

The user's email


App VersionSTRING

Optional

Version of the app


Device IDSTRING

Optional

Device ID


Device ModelSTRING

Optional

Device Model


Device PlatformSTRING

Optional

Device Platform


Device TokenSTRING

Optional

Device Token. This is not automatically collected by Segment Mobile SDKs. Add it into the Segment payload if needed


LanguageSTRING

Optional

Language


CountrySTRING

Optional

The country code of the user


CitySTRING

Optional

The city of the user


Current LocationOBJECT

Optional

The user's current longitude/latitude.


Device OS VersionSTRING

Optional

The version of the device OS


TimezoneSTRING

Optional

The timezone of the user


User AgentSTRING

Optional

User agent of the device


Custom AttributesOBJECT

Optional

Custom attributes to send to Pushwoosh

Record custom events in Pushwoosh

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

Property nameTypeRequiredDescription
External User IDSTRING
required

The unique user identifier


Device IDSTRING

Optional

Device ID


Device PlatformSTRING

Optional

Device Platform


NameSTRING
required

Event Name


TimestampDATETIME
required

When the event occurred.


Event PropertiesOBJECT

Optional

Properties of the event


Batch Data to PushwooshBOOLEAN

Optional

If true, Segment will batch events before sending to Pushwoosh. 100 events per request max.


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(link takes you to an external page).

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.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to Pushwoosh (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


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

Property nameTypeRequiredDescription
Pushwoosh API Keypassword
required

Pushwoosh API Key from Pushwoosh Control Panel


Pushwoosh Application Codestring
required

Pushwoosh Application Code from Pushwoosh Control Panel