Perhaps that endpoint was down at the time I was hitting it.  I am now getting a more reasonable response code. 

You could use the Reactor API https://developer.adobelaunch.com/api/# to do this.  The problem is that the learning curve is a bit steep unless you're already up on the development techniques involved.  Let's say that you could do this manually to 2000 rules at 15 seconds per rule.  You'd spend abou...

Yep, I assume that doing a new build and publishing to production (Publishing workflow in Launch) will resolve the issue.  Do you have a person who normally does this job?  If so, speak with them.  If not, let me know and I'll see if I can help out.  There is a slight chance that your Launch library...

The Data Layer Manager extension will support this use case. As long as the pushed event has an "event" key, DLM will work just fine. https://techdocs.searchdiscovery.com/adobe-solutions/adobe-launch/launch-extensions/data-layer-manager 

There is an API.  I've used it.  I'm not sure if it has public docs or not.  As with pretty much everything else, the Data Stream management functionality was developed in an API-first fashion.  Remember that "DataStreams" were originally called "EdgeConfigs". The API endpoints operate on https://ed...

I see that you are asking about "dataStreamId" and not "dataSetId".    The dataStream is selected (per Launch environment) in the AEP Web SDK main configuration.  This setting is tied to the "instance" - most people only have one instance and take the default instance name of "alloy".  What you're a...

According to Andrey, you should not use the "defer" attribute in the Launch embed script tag. See here: https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/adobe-launch-async-javascript-differing/td-p/371879 

It looks like they are running on different turbine versions and have vastly different build dates (one was last built over two years ago).   "Turbine" is the internal name for the Tags (Launch) runtime engine.    

POSTing to the mappingSets/preview endpoint as described here https://developer.adobe.com/experience-platform-apis/references/data-prep/#operation/previewMappingSetand here https://experienceleague.adobe.com/docs/experience-platform/data-prep/api/mapping-set.html?lang=en#preview-data-for-mappingsret...

Try using the AA Set Variable UI.  In the example below I set eVar3 to %event.$rule.name%