Multiple Merge Policy - Target connections

[Michael_Soprano]

If I have multiple Merge Policies then I need to have different Target connections ....

Then I need to have different Datastreams ....

Then I need to have multiple Web SDKs on specific web page ...

Do you have any ideas on that?

Only the default merge policy (active on EDGE) is able to share audience to Target. Do you have any workaround how to send audience to Target with different Merge Policy?

[Devyendar]

@Michael_Soprano Adobe Target destination connection works only on 'active on Edge' merge policies, and at a given time only 1 merge policy can be 'active on Edge'. other merge policies can’t directly send audiences to Target, so the workaround is export the data and import into Target via API this is not real-time though or use separate sandboxes if you truly need different edge policies in real-time.

[Michael_Soprano]

Thanks @Devyendar 

My business case in details is as follows:
I do project for a company with multiple entities:

1. We are going to have one sandbox - but with multiple merge policies
a) default - containing all data - on EDGE
b) entity 1
c) entity 2
d) entity 3

2. Two datastreams
a) dev
b) prod

3. In Target we assume 4 workspaces:
a) common campaigns
b) workspace for entity 1
c) workspace for entity 2
d) workspace for entity 3

If entity 2 would like to send audience using their merge policy to Workspace for entity 2 its not possible because you can activate only audiences to Target using only on EDGE merge policy......
Creating multiple Datastreams do not make sense because it would be decicated for one web page - shared between all of these 3 entitites

I see two solutions:

1. Using AJO more - but what with real-time event use-cases ...

2. One Schema for data from Data Mart and one dataset but with four separate objects. 

a) object 1 - shared data

b) object 2 - entity 1

c) object 3 - entity 2

d) object 4 - entity 3 

However while doing audience for only with entity 2 data Audience Creator has to be super careful to use data regarding object 3 ....

Do you have any ideas?

[KevinFosterDX]

With additional enhancements to AEP and related apps there are fewer and fewer reasons to have multiple merge policies. From what I've seen, most combinations of use cases function perfectly fine with a single merge policy that is used for all segmentation and all integrations. Having unnecessary additional merge policies only adds unnecessary delays to the daily batch segment job.

There's also a new requirement (May '25?) that says:

"Any new or edited segment definitions that qualify for streaming or edge segmentation must be on the “Active on Edge” merge policy."

https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/eligibility-criteria-upd...

As a policy I would not leave any existing segment definitions in violation of this new rule either, as you never known when or which segment definitions may needed to be edited unexpectedly some day. Better to plan the required changes in my opinion than to have it forced upon you on the afternoon before your long-awaited holiday. 

Just anticipate that such changes will impact elapsed time for segmentation for audiences with large profile counts, so you might want to tackle them in batches using Flexible Audience Evaluation outside of the normal daily full batch segment job.