You are here:
Set Up an External Activation Platform
Reach more customers by connecting an external activation platform to Data 360. Install an external activation platform from AppExchange or a packaged URL.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| To access Data Cloud Setup | System admin profile OR Data Cloud Architect permission set |
- From Setup, select Data Cloud Setup.
- Under External Integrations, select External Activation Targets.
-
Select the external activation platform.
Note Segment names are included in activations. To exclude segment names in the metadata file sent to the external activation platform, turn off Include segment name in activations to this platform. - To enable filtering by data privacy requirements, select the privacy type to indicate how
your customers are impacted by the California Privacy Rights Act (CPRA).If your customers aren’t impacted by CPRA (see California Privacy Protection Agency), select Not Applicable.
-
For ISV-created JSON-based External Activation platforms, review the ID Type Mapping
tab. If the ISV has configured supported IDs, update the ID Type field to map to the
corresponding partner-supported identifiers. Mapping ID types normalizes the ID type,
ensuring records are activated to the appropriate destination folder when the output is
grouped by
PER_USER(user identifier). The ID Type values are case-sensitive. For example, map Google to GAID, GoogleId, or GId as comma-separated values. - Save your changes.
-
Click Enable to use the platform for activations.
You can disable an external activation platform. However, activations associated with a disabled platform won’t be processed.
Considerations for External Activation Platforms Created by ISV Partners Using JSON
- After mapping the ID values and including them in the activation definition's Contact Point Digital ID filters, all records with these contact point filtering values are activated to the ISV partner’s S3 bucket when the activation runs.
- If an ISV partner discontinues support for an identifier during a package upgrade, you'll need to update the activations to reflect the changes made by the ISV partner during the upgrade.
- If you have mapped all possible values for the IDs supported by the ISV partner, and no additional contact point digital Id filters are applied, all records in the Contact Point Digital Id DMO linked to the supported identifiers are activated. However, applying filters allows for more control over which records are included in the activation.
-
Note See Ingest and Model Digital Identifiers for JSON-based External Activation Targets to learn how to model and map digital identifiers to the ContactPointDigitalId DMO to successfully use the activation toolkit for external platforms.
Did this article solve your issue?
Let us know so we can improve!

