The new library doesn't need any of the previously approved assets.  Try not using the 'add all changed resources' button, I've found that it confuses most people and gets in the way of a more linear workflow.There might be a specific workflow that will work for you...  Try this idea and let me know...

If you go to the "Publishing" section, you can click on a library - and then select "Add a Resource".  It's not as fast as the method you described (which is a good idea to implement!), but it is an organized one-stop shop for library management.

I'm surprised that you haven't gotten an answer on this one yet.  Unfortunately, it probably due to the fact that there isn't much you can do in the current scenario.  The catch of using information in a data layer, is that the data layer must exist before your code trying to use it.  In this scenar...

Hi chuneek49107156,Because this custom code is not embedded in the library itself (i.e. the rule isn't triggered by 'Page Top' or 'Page Bottom'), you are seeing the results of using postscribe to execute the custom code.  It's also important to know that this code is executed outside of the timing c...

Any status update for this request?  Forced natural ordering or manual sorting would be really helpful.

On the left-sidebar, you should see a series of 3 icons: Reports, Segments, and Metrics.  These toggle the additional sidebar navigation on and off, see below:

dataLayers don't have to be confined to the specific purpose of "what the application can expose for you".    They can also be created and managed by you as well.For instance, let's say that your organization uses ' window.digitalData ' as a dataLayer that the application will populate for you.You c...

^ I believe this is correct.  Haven't actually validated that myself, but makes sense in your scenario here.I would recommend using a few different methods to store and retrieve this data that would work with code inside a data element:Using a javascript variable created within the window (I prefer ...

^ this is the right answer.GigazelleThat page should be updated to include ' _satellite.property ' as well, which gives the name of the Launch Property.

This kind of error can occur from an incompatibility with prototype.js and the Analytics Extension & Deployment within Launch.  If someone can chime in and say why there incompatibility exists, that'd be great - I have not been able to identify where the issue is other than the fact that some protot...