Hi @RP08,Try adding target="_blank" to the anchor tag element. By principle, activated tracking should not cause this behavior. I use similar types of links but the pdf opens in a browser tab.Let me know if that worked. Thanks.

@Ssb_94, if possible, can you share the screenshots of the configurations of the two offer spaces? Not sure if something can be spotted there, but can have a look. Do you get a response when you explicitly call the visitor offer space?

Hi @Ssb_94,Can you try to edit and republish an offer in both the offer spaces?

Can you check if the linked anonymous space is correctly configured in your live recipient environment's offer space configuration?This is the one thing that comes to mind. 

Hi @MarianaSimoes2021,Can you specify what you are trying to do when you get this error? Some screenshots would help.

Hi @Ssb_94,By completely blank response, do you mean there is not body at all, or a blank proposition? There could be an issue with the visitor live environment setup. Did it ever work previously?Thanks,Ishan

Hi @vavasol,Firstly, your xml has two elements with the same name "testData". You might want to club them into one, with two different attributes.The following script should update the attribute value.var seed = nms.seedMember.load(Your_seed_id).toDocument(); //load the seed address record seed.getE...

Hi @Rajesh_SS01,Here is the reason why your data update fails with duplicate rows intermittently.By principle, the update data activity inserts/updates data in the database in batches, default batch size is 10000.For every batch that is processed, let's say the operation will be an insert operation,...

Hi @Ajit_Tr,You can simply get that data from the broadLogRcp (delivery logs) and the trackingLogRcp (tracking logs) tables respectively. If these tables do not serve your purpose, then could you kindly explain the use case to add more context? Thanks,Ishan

Hi @_Manoj_Kumar_, Glad that you got a workaround for your problem. Did you also check if by any chance your user with "notSuperAdmin" named right also had the "admin" named right? The condition might not have worked if the "admin" right already existed.   Let us know if that helped.   Regards, Isha...