Create a Batch DMO Activation in Data 360

Create a batch DMO activation to export an entire data model object (DMO). You can configure your activation to filter records, add additional attributes, and rank the audience before you publish.

Required Editions

Available in: All Editions supported by Data 360. See Data 360 edition availability.
User Permissions Needed
To create an activation

One of these permission sets:

  • Data Cloud Architect
  • Data Cloud Activation Manager
  • Data Cloud Activation Specialist

Create an Activation

  1. From the Activations tab, click New and select the Data Model Object (DMO) activation type.
  2. Select Batch.
  3. Select the data space.
  4. Select the DMO that you want to activate.
  5. Select an activation target.
  6. (Optional) Select your contact points. The order of attributes in the activation doesn’t match the order in the CSV file output.
  7. When you map contact points, select an existing path or click Edit to add, reorder, or delete sources and change source types and priority for each contact point.
  8. Click Next.
  9. To control what records activate, in Activation Membership, click Add Filters.
    1. Drag attributes from a DMO to create a filter for the activation membership. For filters using related attributes, you can access a DMO up to two relationships from your activation membership, limited to a single path.
      • You can add currency attributes to your activation payload. The Record Currency field isn’t automatically included in the payload, but you can add it if necessary.
      • You can use currency attributes to sort related attributes. The ‌currency conversion is implicitly performed, and the data is sorted accordingly.

      Note: For an engagement DMO, activation applies a default 90-day lookback filter. Activation considers engagement data within this window, and any records outside of this window aren't included in the activation output.

    2. Click Save.
  10. In Contact Points, click Edit Filters.
    1. Drag attributes to create a filter for the contact point. Attributes are only available from the selected contact point DMO and consent DMOs. To manage consent, select attributes from the Contact Point Consent (L3) and Contact Point Subscription Consent (L4) DMO.
    2. Click Save.

      Under Contact Point, the value is 1 for Max. # of Attribute Values because only one value is sent for each contact point channel.

    3. For Sort By, select an attribute and an operator to organize your data.
    4. Click Continue.

Configure Activation Attributes

  1. To activate more attributes, click Add Attributes.
  2. Drag up to 100 additional attributes to the canvas. If you select different columns with similar information, all the unique combinations are added to the output.
    • Direct Attribute—Attributes of the Activation Membership DMO.
    • Related Attribute—Attributes from any object in the DMO if a path to that object from the Activated On object exists and all the relationships along that path are either 1:1 or N:1.
    • Calculated Insights—Add your Calculated Insights metrics to the activation, and apply dimension filters for more granular insights.
  3. To provide a unique attribute name in the output file, click the Edit icon.
    When you activate additional attributes, primary or foreign key fields aren’t available as an option because they aren’t exposed for activation. To see primary or foreign key fields during activation, create a formula field that copies those fields. The formula field is included as an additional attribute for activation. In the lakehouse, number data type fields are stored as decimals, not integers. Therefore in activation, the fields appear as decimals, except for primary keys.
  4. Save your changes.
  5. (Optional) For SFTP, Google Cloud Storage, and Microsoft Azure activation targets, you can remove the default attribute that's included automatically based on the Activation Membership object chosen during activation creation. However, if you remove the primary key attribute of the activated entity, it’s added back to the activation output automatically.

(Optional) Refine the Audience

  1. To include campaign-specific data, expand Campaign Data, and click Add Campaign Attribute.
    You can include up to 20 standard attributes (Activation Name, Activation ID, Segment Name, Segment ID, Activation Run ID, and Activation Publish Start Time) and custom attributes. Each campaign attribute forms a new column in activation output.
    1. You can modify or remove campaign attributes when editing an activation. To remove all campaign attributes, choose the Delete All option from the Add Campaign Attribute dropdown menu.
    You can also manage campaign-specific data through the Activation Connect APIs.
  2. To use the same audience for multiple fixed-size campaigns across different channels with varying budgets, expand Provisional Audience Limiting, then click Rank Attributes.
    1. Drag up to three attributes to the canvas in your preferred hierarchy for ranking and move them up or down to rearrange.
    2. Select the sorting order (ascending or descending) for each attribute and the attribute path, then click Save.
    3. To remove an attribute, select the dropdown menu, then click Remove Attribute
    To rank attributes, you can include direct attributes and calculated insights.
  3. To limit the audience for this activation, enter a number from 1 through 10,000. The audience is selected randomly. If you ranked attributes, the audience is prioritized based on the ranking. To extend the audience limit to a maximum of 1 million, contact Salesforce Customer Support.
  4. Click Next.

Save the Activation

  1. Enter a name and description for your activation.
    • Key qualifier attributes are added to activations automatically
    • Your description can have up to 200 characters
      Important
      Important Don’t include these characters in the name: + ! @ # $ % ^ * ( ) = { } [ ] \ . < > / " : ? | , _ &
  2. Choose a refresh type for the DMO publish.
    A full refresh publishes all records in the DMO. An incremental refresh publishes only the added, updated, and deleted records since the last successful refresh. You can exclude modified or deleted records from the payload if they’re not needed.
  3. Click Save.
  4. Click Publish Now to trigger the activation.
    When you activate to file storage targets like Amazon S3, SFTP, GCS, or Azure,
    • The order of attributes or columns in the activated file can change. Use the column headers to identify and match the corresponding column data at the destination.
    • The Update Action field in the activation file in your file storage target corresponds to the Delta Type field in the Audience DMO Schema Attributes.
    • A metadata JSON file is added to the same directory as your activated data files.
      • For S3 (Legacy) and Amazon S3 targets, this metadata JSON file serves as a confirmation that the write operation to your destination is complete and the data is ready for consumption.

      • For SFTP, GCS, and Azure targets, the metadata file and the activated data files may arrive in any sequence. Hence, the presence of the metadata file doesn’t indicate that activation is complete. To check if the activation is complete, use the Get activation history connect API, or view the publish status in the Activation History section on the activation record home.

      • The metadata JSON file includes:

        • Activation ID and name
        • Data space ID and name
        • Activated record count
        • Refresh ID and publish type
        • Attribute names and their corresponding data types

If you use this batch DMO activation to create an activation-triggered flow, after the activation completes, the flow starts automatically and sends the activated data to the API-based destination configured in the flow. For more information, see Create an Activation-Triggered Flow.

To view linked activation-triggered flows for the activation, open the activation record and check the Associated Flows section. This section shows only activation-triggered flows that you have permission to view. The section is hidden if there are no linked activation-triggered flows or if you don’t have access to any linked flows.