Can you clarify if mean loading two different tags/launch properties _on the same page_ or on _different pages_? Definitely don't load two properties on the same page, but it is technically fine to load different tags/launch properties on different pages of the same domain. The _satellite object sho...

Try here:https://experienceleague.adobe.com/docs/experience-platform/edge-network-server-api/overview.html?lang=en

Hi @GersonFr ,There's no payment required for the API, assuming you have already licensed a Platform-based application like Real-Time CDP, Customer Journey Analytics, or Journey Optimizer. I just updated these videos last week to showcase the new OAuth API credential. Can you confirm that you've tak...

Hi,Can you share a little more details of where you are hoping to see the attributes? In the RTCDP interface? In the Target interface? In the end-users web browser? I made a few videos about this integration. These are the two most relevant to your question. Please let me know if they don't answer y...

I agree, they're very similar. Custom events are triggered by generic JavaScript, while direct call rules are triggered by tags/Launch-specific code. Personally, I think it's better to implement custom events in your web app. You might want to hook into them for other purposes besides tags/Launch ru...

Hi @JPFiber ,Hey no worries, and welcome to Adobe Target! Have you implemented the prehiding snippet before at.js? That's the first line of defense used to manage default content flicker. Also, What do you mean by "mbox is not in use"? "mbox" is a term we are trying to move away from, but some peopl...

Hi @Amrish_Popat ,Thanks for writing. Unfortunately the custom events are one of the at.js features which has not yet made it to Web SDK. The only event we have is the "send event complete" event which is available in tags with the Web SDK extension. I suggest you open a feature request ticket and l...

Did you check the build date of the library? Also, check the Publishing Flow page in tags/Launch to see if there were any build errors. Also double-check that you added the changes you are expecting to the library. Sometimes I forget!   

There's currently no way to override the datastream setting, unfortunately. The product team has heard this feedback before, though, and I hope there will be a way to do this in the future.

You mention a "collect" call. Is the endpoint used "collect" and not "interact" like in the third call below? I usually see "collect" calls made when i have Target click-tracking set up. What code is triggering your calls?