---
schema_version: "1"
id: 027fc6680df3bb56270a90266ceee7f8f87c7a2aca0a5ac8d42d36f93b8c133c
title: Personalization Data Extension
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_dm_personalization_data_extension.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_dm_personalization_data_extension.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: eec93ceb4aa3ce3d154138b265453cf159b3ed99322796ac24a0add6a1a22927
description: Distributed Marketing creates personalization data extensions in Marketing Cloud Engagement to store personalization data Distributed Marketing users enter when personalizing email messages. We automatically create a personalization data extension for you when you first connect a journey to a campaign or enable a journey for quick send. Custom SMS messages aren’t stored here, but are available on the journey’s event data extension.
products:
  - Marketing
  - Cross Cloud
release: "264"
---
# Personalization Data Extension

Distributed Marketing creates personalization data extensions in Marketing Cloud Engagement to store personalization data Distributed Marketing users enter when personalizing email messages. We automatically create a personalization data extension for you when you first connect a journey to a campaign or enable a journey for quick send. Custom SMS messages aren’t stored here, but are available on the journey’s event data extension.

You can find these data extensions in a folder nested under your root Data Extension folder. The folder is named **Distributed Marketing <sfOrgId> Data Extensions**, where <sfOrgId> equals your Org ID. For example, **Distributed Marketing 00D1I000002xfLyUAI Data Extensions**. By default, these data extensions don’t include a retention policy.

Each journey has a unique personalization data extension named **PersonalizationDE\_<sfOrgId>\_<journeyId>**. For example, **PersonalizationDE\_00D560000004xlfEAA\_f960e193-c696-4247-8cba-ea6b83cc891c**. If this data extension is deleted or renamed, an error message displays stating that we can’t locate the data extension. If a connected campaign is modified to connect to a different journey, the personalization data extension for the newly connected journey is used. If the data extension doesn’t exist, a new one is created.

Each row in the personalization data extension contains one piece of personalization data per recipient, per running user. For example, you select a unique image for two members in a Journey with ID 1234 from Org ID ABC. Two rows are then created in the data extension called PersonalizationDE\_ABC\_1234 in the folder Distributed Marketing ABC Data Extensions.

Each data extension row contains two columns, id and value:

  
|   | id | value |
| --- | --- | --- |
| Description | Identifies what variable it is, such as hero\_image, and is a combination of the CampaignMemberId, emailID, and blockId. For example, 00v1F000000Im0MQAS19059intro. | Contains the personalized content. |
| Primary Key | Yes | No |
| Type | Text | Text |
| Length | 100 | 4000 |
| Nullable | No | No |