---
schema_version: "1"
id: 5a242733861f924f75a50ce0e422f210e0697f2d28628c734722fbcb9a8c31f3
title: Package Your External Activation Platform for Distribution with Package Manager
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_package_external_activation_platform_distribution.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_package_external_activation_platform_distribution.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 640a37f10a03ee66a0be1b73a9e0d8a701743f228eae4dfd2e6f6e987ee7209b
description: 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.
products:
  - Data 360
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_warning.png)

Warning Distributing unmanaged packages could expose your Amazon S3 credentials and prevent you from pushing new package versions to admins.

1. Navigate to Package Manager.
2. Under Namespace Settings, make sure you have an existing Namespace before creating a package. If you don’t, click **Edit** to create one.
3. Under the Packages section, click **New** or select an existing package.
    
    ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_important.png)
    
    Important Each org supports only one managed package. If you already have an existing managed package in this org, select that package and upload a new version to it instead of creating a new package. Adding a new version doesn't affect previously published versions.
4. For a new package, enter information about your package. The Package Name is what your Data 360 Admins see to install.
5. Select the **Managed** checkbox.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)
    
    Note The Managed checkbox is only available when creating a new package. If the checkbox is grayed out, your org already has a managed package. In that case, select the existing managed package and upload a new version.
6. Click **Save**.
7. In Components, click **Add**.
8. For Component Type, select **Activation Platform**.
9. Select your External Activation Platform.
10. Click **Add to Package**.
11. Under the Components tab, click **Add** again.
12. For Component Type, click the dropdown list and select **ActivationPlatformCredential**.
13. 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.
14. Click **Add to Package**.
15. Click **Upload**. Package Manager generates a URL for your package.
16. Enter information about your package details like Version Name and Version Number.
17. In Release Type, select **Managed - Release** production distribution.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_tip.png)
    
    Tip Select **Managed - Beta** for testing in a non-production environment before production distribution.
18. Click **Upload**.
19. 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

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](https://help.salesforce.com/s/articleView?id=data.c360_a_test_your_new_activation_platform_package.htm&release=264.0.0&type=5)**  
    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.