You need a Parent Segment in Data Workbench (set up by your Data Engineer), PBP permissions granting you Administrator access (configured by your Admin), the Web SDK installed on your website (set up by your Web Developer), and at least one page with content spots registered in Personalization Studio.
A Parent Segment is a dataset in Data Workbench containing all profiles and attributes for your company, brand, or region. Every audience you create in Personalization Studio draws from the Parent Segment's attributes. Without it, you can't define audiences or run personalization.
Check the following:
- Is the URL accessible from your network?
- Does your site block embedding via
Content-Security-PolicyorX-Frame-Optionsheaders? See Browser Security & Embedding Workarounds for instructions on using the Requestly extension to remove blocking headers. - Is the URL exact? The Visual Selector does not support wildcards.
SPAs are not currently supported. The Visual Selector works with traditional server-rendered pages where each URL maps to a single page state.
No. The system blocks deletion and shows which campaigns reference the page. You must delete those campaigns first.
Audiences are reusable across all campaigns in Personalization Studio. Create an audience once and use it in multiple campaigns.
The highest-priority audience wins. Prioritize audiences by drag-and-drop ordering within the campaign during the Events & Audiences step.
The most recently updated campaign takes priority. A formal campaign prioritization feature is planned for a future release.
They see the fallback content — either the existing website content (no change) or a marketer-defined static fallback (image, text, or CTA).
The system targets sub-second decisioning, retrieval, and rendering. Note that image loading speed also depends on the digital asset management (DAM) platform hosting the image — ensure your image hosting service delivers assets with low latency.
All images must be provided through an external URL. Personalization Studio does not support direct image upload. You can use any image format that browsers support (JPEG, PNG, WebP, etc.) as long as the image is hosted at an accessible URL.
Initial API requests may take slightly longer as the system warms up. Subsequent requests respond in under 100ms. Consider implementing warm-up calls after deployment to ensure consistently fast response times for your visitors.
After launching a campaign, validate with these test scenarios:
| Category | What to Verify |
|---|---|
| Configuration | All event tables active in Data Workbench. Event definitions capture expected events. Attributes configured with correct data types. ID stitching includes all identity fields. |
| Web SDK | SDK properly captures website events. Personalization creatives load based on audience membership. |
| Business Logic | Each personalization creative renders correctly. Attributes return expected values. Audience membership is accurate. |
| Performance | Response times meet the sub-second SLA. System handles expected traffic load. |