Embeds let you place Appcues content directly inside your product's layout — inline with the UI, not layered on top of it. Use them to guide, inform, or prompt users without interrupting what they're doing.

Unlike Flows (which overlay the page), Embeds sit within the interface itself. They look and feel like part of your product.

When to use Embeds

• Onboarding and adoption: Surface next steps, tips, or setup prompts in context — right where users need them.
• Contextual help: Show relevant guidance or explanations alongside the feature a user is actively using.
• Upsells and upgrades: Highlight plan-specific features or upgrade paths in parts of the UI users already look at.
• Personalized nudges: Tailor what each user sees based on their behavior, segment, or lifecycle stage.

How Embeds work

Embeds target a specific element in your product's UI using a CSS selector and render Appcues content at that location. You choose a placement mode — Append (after existing content), Prepend (before existing content), or Replace (swap out the existing content entirely) — to control exactly how the Embed sits relative to what's already on the page.

You define where the Embed appears, who sees it, and what it contains — all from the Appcues Builder, with no code changes required.

Content and layout

Embeds support different layout options and four content block types: Text, Button, Image, and iFrame. You can build multi-step Embeds where users navigate between screens using buttons.

Behavior and targeting

• Multiple Embeds per page. You can target several Embeds to the same page. If a user qualifies for more than one, they see all of them.
• No conflict with Flows. Embeds and Flows operate independently. Flows still display on a page even if Embeds are also present.
• Audience targeting. Embeds use the same targeting rules as other Appcues content — segments, properties, page rules, and events.
• Frequency and dismiss. Embeds can show once or every time a user visits the page. You can add a close button and control whether dismissing is permanent or temporary.

Embeds vs. Flows

Flows and Embeds solve different problems. Flows overlay the page — Modals, Slideouts, and Tooltips appear on top of your UI and require the user to interact before continuing. Embeds render inline — they sit inside the page layout and feel like part of the product.

When to use a Flow

• You need the user's full attention — onboarding walkthroughs, feature announcements, or surveys where a response is important.
• The content needs to guide users across multiple pages or elements.
• You want to gate progress — the user must complete or dismiss the step before continuing.
• The experience should show once (or a limited number of times) based on frequency rules.

When to use an Embed

• Guidance should feel native to the page — contextual tips, inline banners, or calls to action that look like part of your product.
• The content should be persistently visible as long as the user qualifies, not a one-time interruption.
• You want multiple pieces of content on the same page — Embeds don't compete with each other or with Flows.
• The use case is spatially specific — you need content inside a particular section, sidebar, or card in your UI.

Can I use both?

Yes. Embeds and Flows don't interfere with each other. A common pattern is using a Flow to introduce a new feature (one-time announcement) and an Embed to provide ongoing guidance in the relevant part of the UI after the Flow is dismissed.

Common questions

How are Embeds different from Pins?

Pins attach to a specific element and appear as an icon or tooltip on hover/click. Embeds inject content directly into the page layout — they're part of the DOM, not floating over it. Use Pins for contextual hints on specific UI elements; use Embeds for richer inline content like cards, banners, or multi-step guides.

How are Embeds different from Banners?

Banners are fixed to the top or bottom of the page. Embeds can target any element anywhere in your layout. Embeds also support multi-step content, flexible layouts, and iframes — Banners are simpler and better suited for brief site-wide announcements.

Can I use Embeds for localized content?

Yes. Embeds support multiple locales and RTL layout direction from the builder.