This is not possible. Technically, Adobe Campaign will send 1 individual technical E-Mail per recipient. To: is always the information of the actual recipient, you can't have a list of all recipients shown in a mail generated by ACS

How was the content migrated on AEM side? Full migration including all properties? Then the easiest way might be to just change the existing external account to point to AEMaaCS, then no need to change on the individual mail   If the content was migrated on AEM side, the unique ID which is generated...

Does this happen all the time for this E-Mail? It could be that some "invalid" personalization data is used (e.g. reference to a profile field in a transactional message)   1 trick: open the developer console of your browser and look in the network tab for the result message of the API call done by ...

The Update Data by default sets the org unit of the user executing the workflow. To have it assigned to a different org unit: Add a reconciliation in the workflow which does a lookup for the corresponding org unitUpdate data Under reconciliation ensure the org unit is part of the reconciliation crit...

For ACS the approach described by Craig also works: Create a workflowQuery for deliveryUse reconciliation to lookup campaign (under Relations tab)Use update data and assigned the looked up campaign to the campaign object

As said, this is unfortunately not possible in a standard way. Depending on the profile count / number of fields you are interested in, you could do: Create a table where you copy the corresponding profile fields with a schedule workflowANother scheduled workflow which checks all changed profiles to...

I think this is related to Campaign Classic and not Standard?

There is no such automatic propagation possible in ACS   There is some way to reconcile the delivery log with the events and potentially store data in a custom table (with a link to the delivery log). But that is not straight-forward and also needs to be done before the regular cleanup removes the e...

There are basically two ways to solve this: Create the profile on a common parent org unit for the two, then both will be able to access/target it though only in read-only modeCreate 2 distinct profiles A profile can't have more than 1 org unit, thus creating 2 profiles might be an optionBut they ar...

Unfortunately there is no such shortcut in ACS to add that automatically in the tracking link