Picked documentation

Picked lets you build personalized UI flows in a visual editor. The SDK then serves them to the visitors on your site.

There are two paths to follow. Choose the one that matches your work.

Work in the dashboard

Build experiences, write content, and publish.

Start with build your first experience. It takes you from an empty project to a survey on your own site, and it needs no development tools.

One thing must happen first: a developer adds the Picked SDK to your site one time. After that, the dashboard is all you need.

Then:

• Build — experiences, flows, conditions, and A/B tests.
• Content — Models, Blocks, entries, pages, and assets.
• Publish — preview, publish, and roll back.
• Administer and measure — members, API keys, analytics, and the tools that connect Picked to Google Tag Manager and to an AI tool.
• Dashboard reference — every dashboard screen and every option, plus the glossary.
• How Picked works — what happens when you publish.

Integrate with code

Add Picked to a site or an application. Your code then renders the experiences that the dashboard describes.

Start with add Picked to your application. It goes from an empty project to a survey that runs in React or in Svelte.

Read the dashboard documents above also. Everything your code renders is described there, so the two paths link to each other rather than repeat.

Then:

• Integrate the SDK — install, register a component, read a feature flag.
• Build a step form — render fields, act on a submission, validate input.
• Server-side rendering — a page that a search engine can read.
• Authenticate — the management API.
• SDK reference, Delivery API, PickedQL.
• Why it works this way — the design behind the SDK.