Hi Florian,ok, Campaign expects that the address in the deliveryLog contains the encrypted Line ID and then tries to decrypt it.That's the place where it fails for you.You should crypt the ID Ud7* with the NmsLine_AESKey before sending a message.

Hi,which ACC version are you using?Can you check following:Verbose logs when a new follower is addedID stored after following, can you decrypt that with a decrypt string call in JS?Normally the encrypted user ID should start with a @ sign in current version, so the ID shown in your screenshot looks ...

Hi Eveline,if your are in A, you will have read-only access to those in "All" org unit.So you can see them and also add them to audiences.But you won't be able to modify any profile properties or delete profiles in "all" unit

this will be a full blacklist on the E-Mail address.i.e. all profiles sharing same Email address would not receive communication anymore

Unfortunately I don't know of any easy way to solve the problem.

No, that won't work.A user can be only in 1 distinct org unit which is dynamically determined.If in your case they are in A+B, they can't login anymoreAdobe Campaign Help | Managing groups and users If a user is in several groups:    The roles of the different groups are cumulated. Here, users are i...

You may do a DB trace on WriteCollection.If I remember correctly, this is not doing one insert into a temp table but rather looping over each entry of the collection. For each, it would chdck for changes and potentially do another 1 record UPDATE/INSERT statement.

DB activity should normally always be the faster way.WriteCollection may trigger a lot of small SQL calls to the database which is slow.Also for JS, you woukd have tondo all in loops / chunks if you have a lot of data as the query activity might not fetch all data in 1 go.

Hi,please check to post in the Campaign Classic forum for such topic.Campaign Standard does not have the JS activity so people there might not help.If you use the default JS activity, it won't be in a document scope.createElement needs a DOMDocument instance for being able to work.So please check th...

It is working fine for me here following these steps:Create & Publish the new Event with adding the deisred fieldOpen the transactional templateClick on Pencil iconGo to section "Content"Click on button "Initialize content variant"Then it will initialize the chosen language besides the "Default" var...