Wallet Page View Extract
The daily Wallet Page View extract is used to sync wallet data between Vibes platform and a Customer Relationship Management (CRM) or Campaign Management system.
Standard File Name
The following is the recommended best practice for file names. File naming conventions may be changed upon request.
walletpageviews_<company_key>_<date>.<extension>
How to Read Files
Extract files will be delivered in tab-separated value (TSV) text files. The information is separated into rows and columns. Column data will be separated by tabs, while each new row will be separated by a hard return.
Contents of Each File
Each row represents a page view of a Wallet page created by the Vibes platform.
File Body
Field Name | Data Type | Description |
---|---|---|
view_uid | String | Unique Vibes-specified GUID representing each page view. |
campaign_uid | String | Global Unique ID representing the campaign at Vibes. |
company_id | String | A unique identifier for your Vibes company account. |
wallet_page_type | String | Key value indicating the specific page/flow that was viewed. These will map to the various pages in the specific campaign flow. Valid values include: - UNKNOWN, smartlink, location_selector, passbook |
user_agent | String | The first 255 characters of the browser user-agent header value. |
uuid | String | This is a campaign-specific identifier that is used to identify wallet objects. This is generally customer defined, as it can be included in links and used before a wallet object is created. Note: uuid = wallet_item_id. |
platform | String | The string for the specified device platform. Example: 'Android 7.1.1', 'iOS 10.2', and so on. |
viewed_at | Date/Time | The date/time when the page was viewed. Format example: "2017-04-05 14:30:00 UTC.” |
Example File
Updated about 1 month ago