Wallet Instance Extract

The daily Wallet Instance Extract is used to sync Wallet data between Vibes Platform and a Customer Relationship Management (CRM) or Campaign Management system. It will contain all the Wallet instances that have been registered or unregistered since the last data extract.

Standard File Name

The following is the recommended best practice for file names. File naming conventions may be changed upon request.

walletinstance_<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 file will contain the subscription activity for each day. To help you understand a few common scenarios, below are a few examples:

If wallet object is registered on 4/5/2017:

wallet_instance_uidinstance_eventregistered_atunregistered_atwallet_object_uidwallet_providerPlatformcompany_idcampaign_uiduuidcurrent_flagshared_instance
111b2c1234d1e1234567f123456789abcdefghijk123456registered2017-04-05 14:30:00 UTCAB123B23-45CA-56D1-EF7G-HIJK89012BZPassiOSA2bc3dFgz1a2a-123a123456a1-b001TRUEFALSE

If wallet object is registered and unregistered on 4/5/2017:

wallet_instance_uidinstance_eventregistered_atunregistered_atwallet_object_uidwallet_providerPlatformcompany_idcampaign_uiduuidcurrent_flagshared_instance
111b2c1234d1e1234567f123456789abcdefghijk123456unregistered2017-04-05 14:30:00 UTC2017-04-05 15:30:00 UTCAB123B23-45CA-56D1-EF7G-HIJK89012BZPassiOSA2bc3dFgz1a2a-123a123456a1-b001FALSEFALSE

If wallet object is registered and unregistered on 4/5/2017 and the same object is registered again on 4/5/2017:

wallet_instance_uidinstance_eventregistered_atunregistered_atwallet_object_uidwallet_providerPlatformcompany_idcampaign_uiduuidcurrent_flagshared_instance
111b2c1234d1e1234567f123456789abcdefghijk123456unregistered2017-04-05 14:30:00 UTC2017-04-05 15:30:00 UTCAB123B23-45CA-56D1-EF7G-HIJK89012BZPassiOSA2bc3dFgz1a2a-123a123456a1-b001FALSEFALSE
111b2c1234d1e1234567f123456789abcdefghijk123456registered2017-04-05 16:30:00 UTCAB123B23-45CA-56D1-EF7G-HIJK89012BZPassiOSA2bc3dFgz1a2a-123a123456a1-b001TRUETRUE

File Body

The file body can contain the following fields as data, separated by the delimiter and a header row.

Field NameData TypeDescription
wallet_instance_uidStringUnique Vibes-specific Identifier for each wallet instance that's been installed.
instance_eventStringType of wallet instance event. Valid values: Registered and Unregistered.
registered_atDate/TimeThe date/time when the wallet object was installed. Format example: "2017-04-05 14:30:00 UTC".
unregistered_atDate/TimeDate/time when the wallet object was uninstalled. Format example: "2017-04-05 14:30:00 UTC".
wallet_object_uidStringUnique identifier for the wallet object of this instance.
wallet_providerStringString name for the installed provider. Valid values are Pass and Wallet.
platformStringString for the specified device platform. Example: 'Android 7.1.1', 'iOS 10.3', and so on.
company_idStringUnique string representing the id of your Vibes company account.
campaign_uidStringGlobal Unique ID representing the campaign at Vibes.
uuidStringThis 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.
current_flagBooleanIt is True if the instance is currently registered, or False if the instance has been unregistered.
shared_instanceBooleanIt is False if this the first installed instance for the Wallet object, or True otherwise.

Example File