how to send data to two destination at sandbox level

[Pradeep-Jaiswal]

lets say there is a requirement that any data that is exported out from AEP to any destination, that data should also be exported into inhouse datawarehouse for audit purpose. Now instead of marking every audience activation at two destination manually, is there a way better way to do it sandbox level so that every export automatically gets exported into inhouse datawarehouse as well ?

[itsMeTechy]

Hi @Pradeep-Jaiswal 

i don't think any option available to activate an audience by default to a destination with out explicitly configuring it. 

you can also think of doing dataset export of profile snapshot, then data warehouse you can have this data loaded. You can also think of having some level of transformation to load only the details you want for audit. segment membership will also be available, so you know which profile is qualified for which segment. or you can keep the data set export file as it is in data lake, and use it only when needed.

[Pradeep-Jaiswal]

The qualification status in profile snapshot would not indicate if the audience was shared to which destination.

One option i can think of is, exporting the profile snapshot of all qualified profiles into external datawarehous. and from external dataware house share those profile with actual destination, so that warehouse can mark which profile is being shared with which destination. We would unfortunately loose the AEP destination capability if we do this inside the datawarehouse, Is there any API or something which has details of which profile is part of which destination ?

[Sukrity_Wadhwa]

Hi @itsMeTechy,

Can you please help @Pradeep-Jaiswal further with their query?

Thanks!

[Pradeep-Jaiswal · Accepted solution]

After further investigation i found that following tables have the information related to destination name, audience name, audience profile details.

qsaccel.profile_agg.adwh_dim_br_segment_destinations
qsaccel.profile_agg.adwh_dim_destination
qsaccel.profile_agg.adwh_dim_segments,
profile_snapshot_export_

so an easier way is build a data distiller query which join these table, and export all the profiles along with destination information to external system.

This eliminate the need of having third system doing the data transformation or transportation outside the adobe ecosystem. The downside of DD is its batch based.