hi @Pratibha_Mallya Similar question was posted earlier today actually and what you want to achieve is not supported by Campaign.The Tracking label is created and stored when a Delivery is saved and as such you can have only 1 label per URL per delivery and it is the reason in the sample you provide...

Hi @igorku Outside the error, why are you using JavaScript and not a Query activity within a Workflow?In JavaScript, you would use queryDef object (https://experienceleague.adobe.com/developer/campaign-api/api/sm-queryDef-BuildQuery.html)I would not recommend to use the DBEngine, you're exposing you...

Hi @Gangadhar_Reddy1 If I understand you well, you want the URL label to be dynamic that it includes a Product (let say Code) in its label?In Campaign, URL Labels are static as they are created when a Delivery is saved.Saying that, depending on how many such URL you would have in your delivery, if y...

Hi @anjee78 What is a Profile from a licence point of view is mentioned in the documentation that was pointed earlier. https://helpx.adobe.com/legal/product-descriptions/adobe-campaign-classic---product-description.html#:~:text=Definitions-,Active%20Profile,-means%20a%20ProfileThanksDenis

Hi @NeelamBakre It is a very classic error whenone starts to use ACC API (Mkt and RT) and the error is due to IP missing authorisation , Go to ACC Control Panel, section Instance setting and authorise your IP address for API. That would solve the Access Denied error.Thanks a lotDenis

Hi @GMar Profile logs as it name infers are delivery and tracking logs for deliveries sent to a Profile.When creating a transactional event, you select which type it would be:Profile: the delivery will be sent to a Profile and you would have to ensure to pass the reconciliation field in the event to...

Hi @SmritiFotedar O i see, you can't map it to the field within the link if the link doesn't exist yet, so you can't map the field directly on country.@isoA2 because the link"country" does not exist yet.... Check the link definition on nms:recipientThat's the reason you put the ISO2 from your file i...

Hi @SmritiFotedar If you have the field in your CSV and the new field available in the Recipient entity, in the Update activity, you just select the field from the CSV in the Source section and you select the new field from the Recipient entity in the Target section...Sorry I might miss something bu...

Hi @SmritiFotedar What is the format of the country in the file? Is it ISO2 value or is it just the country name itself? If it is ISO, then you can used the standard field "@countryCoide"If it is the country name, you would need to extend the schema nms:recipient to add the country name as a new fie...

Hi @SmritiFotedar I am a bit confused by your workflow:You do a query on nms:recipient to get get a list of recipient --> fair enough.How do you get the country code you want to update these recipients, do you bring it in Additional Data?The field to update is simply @countryCode in the destination ...