Hi @CJara1 You can make use of profile parameters to pull the datalayer value into target.  Reference: https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/odd-issues-with-profile-parameters/m-p/427214#M7068Once you have the datalayer variable in target you can use it in the offer...

@Siva_Sogalapalli ACS Commons asset importer can't be used to update metadata as the purpose of the tool is to import assets. Feel free to correct me if I'm wrong. And also I needed to have this done for existing assets in DAM.

Thanks @lukasz-m Another solution I tried was creating a package of all the metadata nodes under a path, and then update the xml by emptying the dc:description(done using VS Code searching all occurances under the folder), repackaging and installing it.

Could you provide an example on how JS Script can be used to update node properties? Thanks!

Thanks @Gokul_Agiwal I couldn't get the custom library header to work for me. However, in Adobe Launch, I came across the 'Add Params to Page Load Request' action. By definition it's equivalent to the targetPageParams() method as per Adobe docs:  Add Params to Page Load Request, which adds parameter...

It's for the customer.

Hello @Gokul_Agiwal Creating a target audience from AEM allows only to define audience bases on Geo, OS, Site etc. Even there is custom and visitor profile attributes. But how the AEM users can be defined as an audience? When I checked contexthub I have this attribute profile/displayName and target ...

Yes I do have that launch call in the network logs @Gaurav_Singh

Hi @Gaurav_Singh In the network log as well there's no trace of any target calls, it's not getting fired.

You can use the following js instead, in the browser console. $.ajax({ type: "POST", url: "/bin/wcmcommand?srcPath=/path/to/source&destParentPath=/path/to/destination&cmd=copyPage"}); Hope this helps