Hi @DishaSharma, Managing delivery.content.html.source as an object and string sometimes brings problems. Try with this new JS, and let me know how it goes.// Define the source tag var sourceTag = "E00040S3000D99908"; // Ensure the delivery content is accessible if (delivery && delivery.content && ...

Check that AEM passes what you want to track by adding parameters to your email or even using Adobe Analytics or Adobe Launch if required

Hi @jkkkkkkkkkkkkkkkkk, Have you integrated properly AEM with campaign?   Regards,Celia

Hi  @vks60, I answer to your questions in blue: Q- So you are saying that we don't have currently the capability to link any schema with the event like we did in adobe campaign standard? Yes, in Campaign v8 there is no direct capability to link any schema with an event like in Adobe Campaign Standar...

Hi @Shruti1, Under Adminisitration-Campaign Management-Typologies you can create a typology rule applying the following JavaScript // Define the source tag var sourceTag = "E00040S3000D99908"; // Function to check if a URL already contains the source tag function appendSourceTag(url) { var sepa...

Hi  @CampaignerForLife, Have you checked the web log file? Regards, Celia

Hi @SankarRa1, Don't worry, more than happy to follow up. I share with you possible steps that you can follow to sort it out:-Check that the right schema is mapped and storage is enabled in the offer space sttings-Manually try to add a test entry via a workflow or xtk.session.write to check if propo...

Hi @DishaSharma, Try with the following codes: For method 1: (typology rule)// Time to add that SOURCETAG magic to all URLs in the email before sending // Define our special source tag for FB var sourcetag = "SOURCETAG=C0030P3000A99P0000F0000MCD0"; // Loop through all the URLs in the email cont...

Hi @Shruti1, It would be more practical, to create a typology rule, cause it is more flexible and allows you to process all URLs dynamically within the email content before sending or you can modify the NmsTracking_Clickormula). Applying JavaScript you can do it, defining the variables and a for to ...

Hi @LakshmiPravallika,I would try with the following code: var query = xtk.queryDef.create( <queryDef schema="xtk:workflow" operation="select"> <select> <node expr="@id"/> <node expr="@internalName"/> <node expr="activities/scheduler/@label"/...