Pushwoosh Setup Guide
Private Beta2 minute read
The Pushwoosh destination integration is maintained by the Pushwoosh team and is currently in Private Beta.
Reach out to Customer Success if you’re interested in enabling this destination for your workspace.
Add Pushwoosh as a destination in RudderStack. The destination supports cloud mode only.
Connection compatibility
| Destination Information | |||
|---|---|---|---|
| |||
Setup
In your RudderStack dashboard, add a source. Then, from the list of destinations, select Pushwoosh.
Connection settings
| Setting | Description |
|---|---|
| Destination name | Assign a name to uniquely identify the destination. |
| Application Code | Your Pushwoosh application code, in the format ABCDE-12345. Find it in the Pushwoosh Control Panel next to your project name. |
| API Token | A Pushwoosh API token with Device API access. Generate it in the Pushwoosh Control Panel under Settings > API Access. |
Other settings
| Setting | Description |
|---|---|
| Consent management settings | Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature. |
Region limitation
The destination supports only Pushwoosh’s EU (NUE) data center. Accounts hosted in other Pushwoosh regions fail withapplication not foundorstatus_code 210. A region setting is planned before the destination leaves Private Beta.
Send data using Reverse ETL
Reverse ETL is supported through the JSON Mapper only. Visual Data Mapper v1 and v2 aren’t supported.
Shape each warehouse row as one of these events:
identify, withuserIdandtraitstrack, withuserId,event, andproperties
The same event validation rules in the Pushwoosh Cloud Mode Integration apply.
Next steps
Send events with the Pushwoosh Cloud Mode Integration.