You can export user or device data for a specific segment using the Pushwoosh API, for example to feed a data warehouse (Google BigQuery), a CRM, or cloud storage.
The export is a two-step, asynchronous process:
-
POST https://api.pushwoosh.com/api/v2/audience/exportSegment— starts the export. Send your API access token inauth, the segment infilterExpression(or a pre-madefilterCode), plusapplicationCode. Optional parameters includeexportData(hwids,push_tokens,users,tags,location),tagsList,format(csvorjson_each_line),includeWithoutTokensandgenerateExport. The response contains atask_id. -
POST https://api.pushwoosh.com/api/v2/audience/exportSegment/result— sendauthand thetask_idfrom step 1 to retrieve the result. The response returnsdevicesCountandfilename— a link to a ZIP archive that unpacks to the CSV or JSON file (per theformatyou requested).
Downloading the file requires authorization. Since 3 April 2025 the export link is protected: in a browser, simply be logged in to the Pushwoosh Control Panel; from server-side software, send the header Authorization: Token YOUR_API_TOKEN.
Other considerations
- By default the export contains HWID, User ID, push token, platform type, and the default tags (Age, Application Version, City) plus any account tags. Use
exportData/tagsListto narrow it down. - User and device data is volatile: push tokens are removed when an app is uninstalled and long-inactive devices are pruned, so your integration should treat each export as a snapshot rather than a stable key set.
Comments
0 comments
Article is closed for comments.