---
schema_version: "1"
id: b575c05b8ef2ec9b1e9e43f3b7f3af721b6b31d3e06738311b332a1768d7621b
title: September 2021 Features in Interaction Studio
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_pers_new_features_september2021.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_pers_new_features_september2021.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b405108be71cedd5ae2d54ddcff8843836b5cae9e9e9fd8f63602191d8056f25
description: The following functionality was released in September, 2021.
products:
  - Marketing
  - Salesforce Personalization
release: "264"
---
# September 2021 Features in Interaction Studio

The following functionality was released in September, 2021.

## Use More than One Identity in Your Serverside Campaigns

Now you can use more than one identity attribute in your Serverside Event API requests to get more flexibility when you configure Serverside campaigns. Previously, you configured requests to include one identity attribute for lookup and merge.

Why: Any identity attributes that you now provide in the request are used in lookup and merge. And you aren’t required to pass a default identity as user ID in the Serverside Event API. Instead, you can pass identities as user attributes to Interaction Studio.

Where: This change applies to Premium Edition.

## Gain More Flexibility in Identity Setup with Profile ID

The Interaction Studio Multiple Identity System now has another built-in identity for export or merge. Profile ID is the new system-generated ID for each unique and known customer profile that gives you more flexibility when you set up your identity system.

Where: This change applies to Premium Edition.

## User Profile Objects

You can now extend profile data storage by configuring Profile Objects containing user-specific or business-related catalog information. User Profile Objects increase customer access to existing data storage mechanisms for user profiles and provide a rules framework to help you use this data for segmentation and campaign targeting.

Why: Profile Objects eliminate the distinction between Item Types and Dimensions. And Catalog Objects now avoid the mistaken assumption that there’s a parent and child relationship between items and dimensions.

Who: To use this feature, you must have Configure Catalog and Profile Objects permissions.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <thead class="slds-text-title_caps ">
          <tr><th class="slds-cell-wrap" scope="col" id="d60850e69">User Profile Objects (New Feature):</th>
          <th class="slds-cell-wrap" scope="col" id="d60850e72">Catalog Objects (Updates or Existing Catalog System):</th>
        </tr></thead>
        <tbody><tr class="">
          <td class="slds-cell-wrap" data-label="User Profile Objects (New Feature):" headers="d60850e69">
            <ul>
              <li>New Object type for Users “User Profile Objects”</li>

              <li>New Enhancements to Catalog Objects</li>

              <li>New Profile Object tab on the user profile</li>

              <li>New User Profile Object ETL</li>

              <li>New User Profile Object rules for segmentation and campaign targeting</li>

            </ul>

          </td>
          <td class="slds-cell-wrap" data-label="Catalog Objects (Updates or Existing Catalog System):" headers="d60850e72">
            <ul>
              <li>Catalog Set-Up screen moving to Settings &gt; Catalog and Profile Objects</li>

              <li>Removing separation of Item Types and Dimensions to be simply “Catalog Objects”</li>

              <li>All catalog items on the catalog and profile object set-up screen will be grouped
                under Catalog Objects</li>

              <li>Concept of “Dimensions” changing to “Related Catalog Objects”</li>

              <li>All ETLs and sitemaps that use Dimensions will continue to function (update is
                backwards compatible)</li>

              <li>Dimension ETL being deprecated and replaced with Catalog Object ETL<ul>
                  <li>Any existing dimension ETL’s that are running will continue to function</li>
                </ul>
              </li>

              <li>Cardinality now defined at the relationship level instead of at the object
                level</li>

            </ul>

          </td>
        </tr>
      </tbody></table>