Custom Field: Are messages sent to a set of Subscribers.
Broadcast: Are messages sent to a set of Subscribers.
The following Vibes Mobile Engagement Platform terminology is commonly used when working with the Platform APIs and Callbacks.
|Acquisition APIs||Used to add or search for Participants and Get Acquisitions Campaigns.|
|Acquisition Campaign||An Acquisition Campaign defines a keyword or keywords, and/or API methods that you can use to opt into a Mobile Database list.|
Application Program Interface.
|API Key||The API Key is found at the top of the Campaign page. Your Vibes account manager can help you with your API Key when you create an Acquisition Campaign in the Vibes Platform.|
|Broadcast||Messages sent to a set of Subscribers.|
|Callback||A callback entity is a registration to receive callback to an external URL. It is identified by a CallbackID, which uniquely identifies the record. Additionally, each callback is unique for a given callback type and active date range.|
|Campaign Manager enables interactive campaigns, which includes acquiring People to lists, as well as running contests, voting, and info-on-demand campaigns and incentives.|
|Client Certificate Authentication||Vibes supports Client Certificate Authentication as an extra layer of security for API calls.|
|CRM||Customer Relationship Management.|
|Custom Field||Data about a person that is custom to an account.|
|Custom Short Domain||Vibes provides a proprietary URL shortener for use in Short Message Service (SMS) campaigns.|
|E.164||E.164 is the official format for all international phone numbers that includes a plus sign (+) followed by a country code and phone number. |
|Event||In Vibes Mobile Engagement Platform, Events are occurrences that can be submitted into the system and linked to actions that will be executed within the system. Each event is an individual occurrence that will be checked and routed to an appropriate action for execution based on the event_type.|
|Event Triggered Message||You can use events to trigger Vibes Mobile Engagement Platform messages. You need to work with your Vibes account manager to help you pre-configure any message content. You also need to define the event data ahead of time.|
|external_person_id||A Person entity is an identified entity that has interacted with or been loaded into the Mobile Database. It is identified by a person_id, which uniquely identifies the record, or an external_person_id, which is a unique identifier from the customer system for reference and cross-linking.|
|Incentive Manager||The Incentives Manager is a module in the Vibes Mobile Engagement Platform that allows the issuance and redemption of incentive codes.|
|Incentive Code||A single code that can be issued or redeemed.|
|Incentive Code Issuance||A record of an issuance of an Incentive Code.|
|Incentive Code Redemption||A record of a redemption of an Incentive Code.|
|Incentive Pool||A collection of Incentive Codes.|
|Integration Files||Vibes-supported Integration files are an alternative way to load and update data into Vibes Mobile Engagement Platform.|
|MDN||Mobile Directory Number.|
|Message||An individual communication sent to or from a Person.|
|The daily Message extract is used to sync message data between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system.|
|MMA||Mobile Marketing Association.|
|MO||Mobile Originated (A message the client sends from their mobile phone).|
|Mobile Database||The Vibes Mobile Database stores information about Persons who have already interacted with, or may interact with your campaigns. It also lets you segment, target, and personalize messages to Subscribers.|
|MT||Mobile Terminated (A message sent to a client’s mobile phone).|
|Participant||A Person who has one or more mobile interactions, such as sending a text message, with a company but has not yet subscribed to|
|a Subscription List.|
|A Participant that has requested to opt-in to a Subscription List, has been sent a prompt to join|
|An individual in your Mobile Database. A Person entity is an identified entity that has interacted with or been loaded into the Mobile Database. It is identified by a person_id, which uniquely identifies the record, or an external_person_id, which is a unique identifier from the customer system for reference and cross-linking.|
|person_id||A Person entity is an identified entity that has interacted with or been loaded into the Mobile Database. It is identified by a person_id, which uniquely identifies the record, or an external_person_id, which is a unique identifier from the customer system for reference and cross-linking.|
|Push||Vibes offers a Push Notifications SDK to let you send push messages to consumers, track your App interactions with notifications, and allow mobile applications to register themselves to receive push messages from Vibes Mobile Engagement Platform.|
|Recipient List||An externally defined set of Persons that is used|
Standard Field: Are messages sent to a set of Subscribers.
|Security Assertion Markup Language is an XML-based data format for exchanging authentication and authorization data between parties. Vibes Mobile Engagement Platform allows customers and Partners to use SAML 2.0 to authenticate users into the Platform.|
|SDK||Software Development Kit. An SDK is a programming package that enables a programmer to develop applications for the Vibes Platform.|
|SFTP||Secure File Transfer Protocol. The use of integration files requires a Vibes’ Secure File Transfer Protocol (SFTP) account. Contact your Vibes account manager to get your SFTP account set up.|
|SMS||Short Message Service.|
|SOAP||Simple Object Access Protocol.|
|Standard Field||The field is defined and available to all companies, but the data is always specific to a company.|
|Subscriber||A Participant who is subscribed to one or|
|A Person's membership in a Subscription List.|
|Subscription Entity||The Subscription entity contains the information and metadata for a Person's Subscription to a Subscription List.|
|Subscription Extract||The daily Subscription extract is used to sync Subscriptions between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system.|
|Subscription List||A collection of Subscribers that have all subscribed to the same type of certain content. A Subscription List entity contains the information about a particular Subscription List.|
Tag: Are messages sent to a set of Subscribers.
|Text Delimited Files||Text delimited files are standard text fields with one record per line, and the various columns separated by a delimiter.|
|URL Click Extract||The daily URL Click Extract is used to sync URL click data between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system.|
|UUID||A Universal Unique Identifier is a 128-bit number used to uniquely identify an object or entity on the Internet.|
|Wallet Instance Extract||The daily Wallet Instance extract is used to sync Wallet data between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system. It will contain all of the Wallet instances that have been registered or unregistered since the last data extract.|
Vibes’ Wallet Manager platform enables updates to offers and loyalty cards already saved to a Person's Apple Wallet/Passbook or Google Wallet/Android Pay application.
|Wallet Page View Extract||The daily Wallet Page View extract is used to sync Wallet data between Vibes Mobile Engagement Platform and a Customer Relationship Management (CRM) or Campaign Management system.|
|White Labeling||Vibes Mobile Engagement Platform white labeling capability lets Partners easily customize their logos and URLs.|