# Getting Started

Before creating your first personalization campaign, complete these one-time setup steps. Different team members own different steps.

## Team Roles

| **Role**  | **Responsibilities** |
|  --- | --- |
| **Data Engineer** | Set up the Parent Segment in Data Workbench and configure the RT 2.0 real-time infrastructure. |
| **Admin** | Manage Policy-Based Permissions (PBP) for Personalization Studio access. |
| **Web Developer** | Install the Web SDK, configure browser security workarounds, register website pages, and define content spots. |
| **Digital Marketer** | Create audiences by importing batch segments, create and manage campaigns. |
| **Creative Marketer** | Design creative assets in the drag-and-drop editor for each content spot and audience pair. |


## Step 1: Set Up Parent Segment & Real-Time Configuration

**Owner:** Data Engineer

The Parent Segment is the foundation of all audience targeting. It contains every profile and attribute for your company, brand, or region. You also need to configure the real-time infrastructure that powers sub-second personalization on the website.

1. **[Create a batch Parent Segment](/products/customer-data-platform/data-workbench/parent-segments/creating-parent-segments)** in Data Workbench (or verify an existing one). Include the batch attributes your marketers will use for audience rules:
  - Demographics (age, gender, location)
  - Purchase behavior (total spend, order count, last purchase date)
  - Loyalty tier, subscription status
  - Any custom attributes relevant to your personalization strategy
2. **Set up the real-time configuration** by following the [Creating a Real-Time Configuration](/products/customer-data-platform/real-time/creating-a-real-time-configuration) guide. This provisions the RT 2.0 reactor and connects it to your Parent Segment.
3. **Configure the build/refresh schedule** — this determines how frequently batch data is updated for real-time audience evaluation. Options include hourly, daily, or on-demand.


Important
Both the batch Parent Segment and the RT 2.0 real-time configuration are required. Without both, personalization cannot function. RT 2.0 requires activation by the Treasure AI team — contact your account team or support to request enablement.

### Requesting RT 2.0 Enablement

1. **Gather your information:**
  - **Instance ID** — go to **My Settings > API Keys**. Your instance ID is the number before the forward slash (for example, if your API key shows `11874/[rest of key]`, then `11874` is your instance ID).
  - **Parent Segment ID** — navigate to Audience Studio, click on your parent segment, and find the ID in the URL after `/ps/`.
2. **Submit your request** to your Treasure AI account team or support with your Account Name, Instance ID, and Parent Segment ID.
3. **Receive configuration details** — upon approval, you'll receive: confirmation of RT 2.0 enablement, a Reactor Instance ID (format: `a11874n4`), and next steps for setup.


## Step 2: Configure Permissions

**Owner:** Admin

Grant users access to Personalization Studio through [Policy-Based Permissions](/products/marketing-cloud/personalization-studio/permissions):

1. Navigate to **Control Panel > Policies**.
2. Grant **Full Access** access to campaign creators, web developers, and creative marketers.
  1. Grant **Additional Permissions** to marketers and data engineers
3. Set **None** for users who should not access Personalization Studio.


## Step 3: Configure Browser Security Workarounds

**Owner:** Web Developer

Several features in Personalization Studio (Visual Selector, content preview) embed your website in an iframe. Most websites block this with security headers.

See [Browser Security & Embedding Workarounds](/products/marketing-cloud/personalization-studio/web-sdk-integration#browser-security--embedding-workarounds) for detailed instructions on:

- Installing the Requestly browser extension
- Removing `X-Frame-Options` and `Content-Security-Policy` response headers
- Configuring [third-party cookies](https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Third-party_cookies) for authenticated content
  - Only cookies with `SameSite=None` will be available to your website rendered inside Personalization Studio.


Prerequisite
This step must be completed before you can register pages or use the Visual Selector in Step 5.

## Step 4: Install the Web SDK

**Owner:** Web Developer

The Web SDK is the client-side script that powers personalization on your website. Add the SDK script tag or async loader to every page where personalization will run.

See [Web SDK Integration](/products/marketing-cloud/personalization-studio/web-sdk-integration) for installation instructions and [anti-flicker best practices](/products/marketing-cloud/personalization-studio/web-sdk-integration#anti-flicker-best-practices).

## Step 5: Register Website Pages & Content Spots

**Owner:** Web Developer + Digital Marketer

Register the website pages and DOM elements that will be available for personalization.

1. Align with your Digital Marketer on which pages and content areas to personalize (hero banners, CTAs, promo bars).
2. Ensure target DOM elements have stable `id` attributes.
3. Navigate to **Assets > Pages** in Personalization Studio.
4. Add pages and use the Visual Selector to define content spots.


See [Pages & Content Spots](/products/marketing-cloud/personalization-studio/managing-pages) for the full walkthrough.

## Step 6: Create Audiences

**Owner:** Digital Marketer

Create audiences by importing existing batch segments from Audience Studio:

1. Navigate to **Audiences** in Personalization Studio.
2. Click **Create Audience**.
3. Select a batch segment from the dropdown.
4. Name and save the audience.


Audiences are reusable across all campaigns. See [Managing Audiences](/products/marketing-cloud/personalization-studio/managing-audiences) for details.

## What's Next

Once setup is complete, you're ready to [create your first campaign](/products/marketing-cloud/personalization-studio/creating-campaigns).