You are here:
Package Your External Activation Platform for Distribution with Package Manager
After you created your External Activation Platform and custom metadata, use Package Manager to package and distribute your External Activation Platform to Data 360 Admins. A managed package is recommended because you can provide updates to admins when anything changes with the package. Only managed packages can be distributed through AppExchange.
Warning Distributing unmanaged packages could expose your Amazon S3 credentials and
prevent you from pushing new package versions to admins.
- Navigate to Package Manager.
- Under Namespace Settings, make sure you have an existing Namespace before creating a package. If you don’t, click Edit to create one.
- Under the Packages section, click New or select an existing package.
- For a new package, enter information about your package. The Package Name is what your Data 360 Admins see to install.
- Select the Managed checkbox.
- Click Save.
- In Components, click Add.
- For Component Type, select Activation Platform.
- Select your External Activation Platform.
- Click Add to Package.
- Under the Components tab, click Add again.
- For Component Type, click the dropdown list and select ActivationPlatformCredential.
- Select the checkbox next to your auto-created custom metadata. For JSON-based external activation platforms, the platform credential displayed matches the platform's developer name specified in the JSON configuration.
- Click Add to Package.
- Click Upload. Package Manager generates a URL for your package.
- Enter information about your package details like Version Name and Version Number.
- In Release Type, select Managed - Release production
distribution.
Tip Select Managed - Beta for testing in a non-production environment before production distribution. - Click Upload.
- When your upload is complete, share the installation URL directly with admins, or become an ISV Partner and list your package as an app on AppExchange.
Your External Activation Platform is packaged and ready for Data 360 Admins to install and use.
Note Some changes to your external activation platform versions require admins
to resave previously created activation targets. To avoid problems when distributing new
versions of your package, we recommend:
- Not removing existing identifier types, like hashed email, in future version upgrade.
- Maintaining the same optional or required settings for fields and the same default value for hidden fields.
- Testing an Activation Platform Package
Test an activation platform package by installing it either in an Enterprise or Developer Edition org that has a provisioned Data 360 license. For more rapid testing and inspection of file outputs as you develop your app, use a Dev org to trigger manual activation publish. When testing your activation platform app in an Enterprise org, activation files are published every 24 hours if the activation output is grouped by user identifiers (PER_USER). If the activation output is grouped by segments (PER_SEGMENT), the refresh schedule is tied to the segment publish schedule.
Did this article solve your issue?
Let us know so we can improve!
