Hi @sidkgoel ,This was an underlying issue with the API itself not with
the UI. So there is currently the ability to delete the base
connection/account, but if you were to attempt to recreate a base
connection using the same exact name, it would fail and give an error
claiming that the name of that connection has already been used.
Whatever process the deletion request is initiating in the background
isn't fully functioning as expected.
Hi @keeTee , are these conditions based on data element you are setting,
and how are you actually sending the skus? Depending on wether your site
is a SPA or not, you (or a developer) may need to determine the best way
of storing the skus that meet the conditions across several pages.
You're logic could be, during every new page (or product view click for
SPAs), check the stored location for three skus, based on some
predetermined delimiter. Business logic should be separated to events
that are ...
Hi @francis_harris , I think your question is getting a bit confusing
because a POST request may refer to the linked page, the beacon sent to
Adobe, or even some other resource altogether. In fact, you can even
influence Launch's choice of whether to send a beacon with a GET vs.
POST requests using the useBeacon setting and meeting other criteria for
payload size. Sorry, I see you were referring to the postMessage API, to
send everything to the parent. For the issue of capturing referrer in an
Hi @Luca_Lattarini , That's something my org is doing. It works the same
way as enabling SSO/SAML within your instance of Admin Console, and is
already pretty good granularity of permissions that can be specified
within product profiles. As a note, there are some workflows within
these apps that might require some access to AEP as well. So it would be
best practice to put your CJA/CJO users in a given user group and then
assign both the corresponding product+AEP product profiles to that user
Description - There is currently no way to remove a base connection for
data ingestion, not even with the existing API.Why is this feature
important to you - This would add two benefits. First, it keeps the UI
clean of unused or unwanted connections. Second, it would allow for
better automation of AEP architecture. Any scripting to generate base
connections would need to correctly create a connection of a desired
name on the first try since editing isn't possible and reusing the name
of a connec...
With regards to observation 4, when constructing the XDM for HTTP API
(stream) ingestion, there are two fields that seem to be optional and
don't serve any purpose:1. There is a "flowId" field that can be
included, ref, but that same field isn't specified in the API request
body documentation, here.2. There is a field in the request body schema
called SOURCE_NAME which is optional, but it seems this value can be set
to anything without impacting the ability to ingest the data. For
It looks like the Admin Console has been updated recently so that one
must specify the products a user is meant to be a developer for. This
seems like a great new addition instead of giving blanket access to all
products the user has access to, but now it appears that some of the
products which our organization has licensing for doesn't include the
ability to set developers. How do we enable the ability to develop for
all of the products we hold licensing for?
So Adobe doesn't publicly give any details about that error response, so
we may need to see what they say. On the API side, ref, the xdmEntity is
where the actual values are described. So to say that the entity can't
be processed is pretty vague, but probably has to do with the mapping.
Seems most likely to be a bug with the connector itself which is maybe
using the API incorrectly or not performing any validation on your
behalf. So, on your side, there could be some field validation issue...
Launch and Analytics are two separate products.Launch is a tag manager
for picking up on data on a site and sending it different
places.Analytics is just one possible place to send the data, and is a
product for data analysis and visualization that also plays nice with
other Adobe products. As far as putting Launch on someone else's site,
it is at the discretion of the site's webmaster(s) to allow their
developers to put on tag managers/external scripts. Since it has the
potential for incredible...