Not all components showing in Adobe Target

[ChrisPhillipsUC]

hi all,

Very new to this Adobe Target world but wanted to ask why not all components are visible in the list when you are creating your experience(s).

Scenario:

Experience A: I have a hero banner with a simple text link in the description text.

Experience B: I want to ADD a button using my button component to the hero instead of the text link.

Shouldn't I be able to choose from my library of components and ideally "Drag n Drop" into place where I want these to be?
As this is more appealing to our AEM authors who don't know enough about HTML to create their own button.

If this is possible and it just needs to be configured to show my component library I would love to know where to go.

Thanks in advance.

Chris

[pradnya_balvir]

Hi @ChrisPhillipsUC ,  You’re experiencing is a common limitation or misconfiguration scenario when working with Adobe Target in combination with AEM (Adobe Experience Manager). Adobe Target does not inherently support all AEM components for drag-and-drop or visual authoring unless certain criteria are met.

Are you using AEM with Target via SPA Editor or Experience Fragments?

If you're working directly in Adobe Target and expecting the AEM component library (like buttons, hero banners, etc.) to be fully accessible, it won't work unless you're using AEM components exposed as Experience Fragments (XFs) or exported via Adobe Target integrations.

Fix: Make sure your button component is:

• Part of a reusable Experience Fragment

• Properly exported to Adobe Target via AEM’s Cloud Services (under Target Configuration)

Check if the Component is Marked as Allowed in the Policy

If you're in an AEM page and trying to access components via Target, ensure that:

• The component is enabled in the template/policy configuration.

• It’s listed as an allowed component for that container/layout.

Fix: Go to AEM Template Editor > Policy > Allowed Components and ensure your button component is added there.

Adobe Target Visual Editor Limitations

Target’s Visual Experience Composer (VEC) is not aware of custom AEM components unless they’re designed in a very web-friendly, client-rendered way. Even then, some components will not render correctly in the VEC or be draggable.

• Use Form-Based Composer for deeper control (if visual fails).

• Wrap your custom components inside HTML Offers in Target.

• Ask your dev team to expose a simplified HTML version of complex components for Target use.

Button Component Not Showing Because It's Not “Client-Rendered”

Adobe Target VEC only sees the rendered HTML/DOM on the client side. If your button is rendered via server-side logic or dynamically injected by JS, it might not appear in the DOM when Target loads it.

• Ensure button component is rendered on page load.

• Avoid JS-only render paths unless explicitly handled.

Some links:

https://league.adobe.com/docs/experience-manager-65/content/sites/administering/integration/experien...

Thanks.

Pradnya