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://edge.a...
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
According to Andrey, you should not use the "defer" attribute in the
Launch embed script tag. See here:
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
Best practice (especially) for SPA sites is to work with the site
developers to implement an event driven data layer. Take a look at
as an example. In this example, there are four e...
It appears that you are using slashes instead of dots within the altId.
This is from the docs:curl -X GET \
\ -H 'Accept: application/vnd.adobe.xed-full+json; version=1' \ -H...