Packages

A package is a container of functionality for something as small as an individual component or as large as a set of related apps. After creating a package, you can administer and distribute it to other users and business units within your account.

You can install packages into your account, and then configure and manage them. To view the packages installed in business units where you have permission to install and manage packages, go to Setup | Apps | Installed Packages.

Each package has one or more components that determine what the package can do. Use packages to create API integrations, install custom apps, or add custom Journey Builder components.

You create an integration with a third-party application, which needs access to the REST API or SOAP API. To get a client ID and secret, create an installed package with an API Integration component. You can have one API integration per package.

You create an external app and iFrame it into Marketing Cloud Engagement. Create an installed package with an App component. You can have one app per package. If your app needs access to the API, create an API Integration component as well.

You need a custom activity for one of your journeys that kicks off a REST API call in a third-party application. Create an installed package with a Journey Builder Activity component. You can have multiple Journey Builder Activities per package.

You need a custom entry source for one of your journeys that comes via a REST API call from a third-party application. Create an installed package with a Journey Builder Entry Source component. You can have multiple Journey Builder Entry Sources per package.

Instead of using Content Builder's CKEditor WYSIWYG for HTML editing, you'd like to use a different WYSIWYG, like QuillJS. Create an installed package with a Custom Content Block component.

• AppExchange
• Roles