Roster is where users create the high-level organizational frameworks for their messaging campaigns. Three kinds of items help define these frameworks: Organizations, Accounts, and Credentials.
The top-level organizational unit in Roster is the Organization, Accounts belong to Organizations, and Credentials refer to accounts through which messages are deployed. These credentials authorize the Launchpad application through a Roster account, and, once authorized, are available to any account in the Organization.
Knowledge is where all of the data used in Launchpad is created and stored, and where the relationships between data are defined.
Generally speaking, Knowledge is an interface into Launchpad’s graph database. Graph databases differ from relational databases in that, while relational databases store tabular information in rows and columns, and connect (or “join”) those tables on the fly using columns of related data, data points in graph database are called “nodes,” and their relationships, called “edges,” are persistent attributes of the nodes.
Editor & Composer is where message templates are created, then connected to data defined in Roster and Knowledge.
Editor uses a modified version of the open-source Liquid language template. Using a template-tag structure, Editor is able to incorporate data nodes in Knowledge and combine them with inline variants of many parts of speech, to create nearly limitless variations in rendered messages.
Composer & Editor is where message templates are created, then connected to data defined in Roster and Knowledge.
Create message templates at scale that contain placeholders for the data nodes that lives in your graph. Templates created in Composer can have 100,000+ unique message variations, creating a highly asymmetrical labor productivity ratio.