# Getting Started with Consent Experiences (/docs/consent-management/configuration/consent-experiences/getting-started-with-consent-experiences)

### What is Consent Experiences? [#what-is-consent-experiences]

Consent Experiences is Transcend's no-code consent interface builder. It gives compliance and governance teams full control over how consent banners and modals look, feel, and behave without filing a single engineering ticket.

Using a WYSIWYG editor, you can design, preview, and publish consent UIs across every jurisdiction your organization operates in. All from one interface. Changes go live in minutes, not days.

### Who is this for? [#who-is-this-for]

- **Privacy & Compliance team members** who need to configure compliant UIs and respond quickly to regulatory changes (GDPR, CCPA, and more)
- **Marketing Teams** who own the properties where consent banners are deployed and need them to match brand standards
- **Legal & Governance Teams** who need to review and approve consent copy before it goes live

You don't need to write code or CSS. If you can edit a document, you can use Consent Experiences.

### How it works [#how-it-works]

Consent Experiences is built around two UI components, a **Banner** and a **Modal,** that work together to deliver a complete consent flow to your site visitors.

The **Banner** is the initial prompt visitors see when they land on your site. It's lightweight and designed for quick action, accept, reject, or learn more. 

The **Modal** goes deeper, giving visitors a full view of your data purposes so they can make granular consent choices. You can use either component on its own, or combine them into a single connected experience.

You configure content and behavior in the experience editor, and apply visual styling like colors, buttons, logo through a reusable theme that can be shared across experiences.

### Key Concepts [#key-concepts]

**Experience -** A configured consent UI (banner and/or modal) that can be assigned to one or more regional experiences.

**Theme -** A reusable set of visual styles (colors, logo, buttons) applied to an experience.

**Regional Experience -** The logic layer that determines which experience and purposes a visitor sees based on their location.

**Draft -** An experience being worked on; not yet published or assignable to a live regional experience.

**Active -** An experience staged for publishing and available to assign to a regional experience.

**Published -** An experience deployed to production and live for end users.

### Before you begin [#before-you-begin]

Make sure the following are in place before setting up Consent Experiences:

1. Transcend's **Airgap.js** is installed on your site.
2. Your **Regional Experiences** are configured in Consent Management. 
3. **Consent Experiences** is enabled in Developer Settings → Visual Editor. See Enabling Consent Experiences for instructions.