Last Updated: Wednesday, February 26, 2020
The daily Push Message extract is used to sync push message data between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system.
Tab Delimited Files
Extract files will have each column delimited by a tab, as well as each record delimited by a line feed.
The push message field is quoted with double quotes. Any double quotes within the push message body will be escaped with two double quotes.
Contents of Each File
Each row represents a push notification sent by the Platform to a device.
The file body can contain the following fields as data, separated by the delimiter and a header row.
|Field Length||Allows Nulls|
Unique Vibes-specified GUID representing the Person
External system's Person identifier to include in the Subscription List
|vibes_device_id||String||255||✔︎||Vibes unique identifier for each device|
Operating system of the push device (Android or IOS)
|push_token||String||255||✔︎||Android or IOS Push token|
|message_id||String||255||Unique message ID defined by Vibes|
|client_message_id||String||255||✔︎||Unique message ID defined by a client|
|receipt_at||Date/Time||N/A||Date and time push message received|
|response_text||String||255||✔︎||The response text: Success, Unregistered, or DeviceTokenNotForTopic|
|activity_type||String||255||✔︎||Type of activity the message is associated with (Push, Broadcast, Acquisition, and so on)|
|activity_id||String||255||✔︎||ID of the activity the push message is associated with|
|company_id||String||255||ID of the company|
|app_id||String||255||ID of the mobile app|
|content||String||1000||✔︎||The content of the push message|
|subject||String||255||✔︎||The subject of the push message|
List of Activity Types