Skip to main content
RonJos
Level 2
August 13, 2026
Solved

Distinct Audiences in Adobe Target with AEP and Marketo under single IMS org

  • August 13, 2026
  • 6 replies
  • 87 views

If we have enterprise license for Adobe Target under a single IMS Org, how do I use distinct audiences in Target for multiple sites, where one site will be using Audiences from AEP while another needs to be use Audiences based out of Marketo.

E.g. If I have two websites

  • Site A with AEP and RTCDP (Websdk)
  • Site B with Marketo and not AEP or RTCDP (At.js)

How can I use Adobe Target Enterprise under the single IMS org for AB testing on both Site A and Site B using distinct audiences from AEP for site A, and Marketo Audiences from site B?

Best answer by Gokul_Agiwal

Hi ​@RonJos 

Yes, this can work under a single Adobe Target Enterprise license and IMS Org.

In both the case, think of Adobe Target as the activation layer, while audience qualification can come from different sources depending on how each site is implemented. 

For Site A, since it's connected to AEP/RTCDP through Web SDK, you can build audiences in AEP and share them to Target using the Target destination. Those audiences will then be available for targeting and personalization on Site A. 

For Site B, which uses Marketo and at.js without AEP/RTCDP, you would typically rely on Marketo-derived data being passed to Target (for example, segment membership, lead attributes, or profile data) and create Target audiences based on those values. 

The key point is that Target does not require all sites to use the same audience source. As long as each site sends the appropriate data to Target, you can run experiments and personalization activities for both sites while keeping the audience definitions completely separate. 

Would like to know , when you are referring to  "Marketo audiences",  for Site B, are those audiences already being passed to Target today, or are you looking for a way to make Marketo segment memberships available within Target for audience qualification?  Can you clarify this?  that determine to better approach. 

Hope this helps. 

Looking forward to hearing from you

Thank you. 

6 replies

TNxx
Level 3
August 14, 2026

Hi ​@RonJos ,

 

You can add OR condition and combine audiences from different sources while setting up AB test.

RonJosAuthor
Level 2
August 17, 2026

Thank you ​@TNxx - Here main question is what would be the source of the Audiences - AEP or Marketo. Or can i use them simultaneously toggling between them for Target use case. Note that these web sites also uses websdk for one with AEP and at.js for the one using Marketo audience. 

TNxx
Level 3
August 18, 2026

Ok, so what you can do is create AB test and add multiple pages, and in audience qualification add segments as OR condition from different sources. As long as Target loads on page, it shouldn’t matter if its At.js or WebSDK. But if you are using any mbox functions you might need to write conditions in code to check the script and run function accordingly i.e., 

if its at.js → regular mbox functions (trackEvent, applyOffer etc)

if its WebSDK → new XDM functions (sendEvent, applyPropositions)

 

So if I am on site A, and qualify for audience A, I will qualify for the experience. And if I am on site B and qualify for audience B, I will qualify for the experience. If both sites have different UI, you can add additional pages in setup and add changes accordingly.

 

Hope this helps!

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity AdvisorAccepted solution
Community Advisor
August 18, 2026

Hi ​@RonJos 

Yes, this can work under a single Adobe Target Enterprise license and IMS Org.

In both the case, think of Adobe Target as the activation layer, while audience qualification can come from different sources depending on how each site is implemented. 

For Site A, since it's connected to AEP/RTCDP through Web SDK, you can build audiences in AEP and share them to Target using the Target destination. Those audiences will then be available for targeting and personalization on Site A. 

For Site B, which uses Marketo and at.js without AEP/RTCDP, you would typically rely on Marketo-derived data being passed to Target (for example, segment membership, lead attributes, or profile data) and create Target audiences based on those values. 

The key point is that Target does not require all sites to use the same audience source. As long as each site sends the appropriate data to Target, you can run experiments and personalization activities for both sites while keeping the audience definitions completely separate. 

Would like to know , when you are referring to  "Marketo audiences",  for Site B, are those audiences already being passed to Target today, or are you looking for a way to make Marketo segment memberships available within Target for audience qualification?  Can you clarify this?  that determine to better approach. 

Hope this helps. 

Looking forward to hearing from you

Thank you. 

Thanks, Gokul
RonJosAuthor
Level 2
August 18, 2026

Thank you ​@Gokul_Agiwal . 

We would like to use the Audience identified from Marketo to be used in Site B with Target to do either personalization or AB test.  Just because we have AEP, we want ensure that Site B need to not be forced to use audiences from AEP. 

So our expectation is that

Target on Site A→ Uses WebSDK and uses AEP Audience 

Target on Site B → uses AT.js and uses Audiences from Marketo.

You have clarified that “..Target does not require all sites to use the same audience source. “ - thank you. 

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
August 19, 2026

Hi ​@RonJos Glad to know that your query resolved. 

Thanks, Gokul
Terms & ConditionsAccessibility statement

Loading footer...