What is your data element type?How is it configured in Launch?

Since your nonce is generated per page, then you can still make it work with the Core extension. Recall that when your web page is loaded, the Launch library gets loaded too. This causes the Core extension to also be loaded, and when it does, it can get the nonce from your data element. So, the foll...

TL;DR If you're using Adobe Client Data Layer (ACDL) in Tags (Launch) and ordering of Rules is important to your setup, then setup your ACDL Events to listen to "All Events" only.

Adding my $0.02 to this reply: Fundamentally, Page VIews and Checkouts are tracked with 2 different methods: Page View: tracked with a s.t() beacon call.Checkout: tracked when a hit contains the "scCheckout" success event. The difference is immediately obvious: Checkouts can be tracked with any kind...

Is there any reason that your developers can't resolve the tracking problem for that one scenario? Given your setup, I would personally avoid trying any workaround within Launch. The reason is that your setup has basically standardised to use Direct Calls already, and future-you or your successors w...

@Herder , I appreciate that you want to track the page view when the content (red box in your diagram) is shown visibly to the user. However, in my experience, the Enters Viewport is not a reliable method to perform such tracking. The reason is that you're really dealing with HTML. I think what is h...

Launch doesn't have a native diff checker. However, if you're savvy enough with programming, you can write a script that uses the Launch API to programmatically read-and-diff your libraries. See the API guide: https://experienceleague.adobe.com/en/docs/experience-platform/tags/api/endpoints/librarie...

I don't know if there's a hard-and-fast rule about using the correct media type. Here's my take on the 4 values that you've listed: LIVE: This would be used with a live stream. Think of YouTube "Live" videos.LINEAR: This would probably be used with linear streams that have fixed programming. Think o...

You will need to configure the "Consent" section in the Web SDK extension's configuration:   You will need to have a custom data element that returns "in", "out" or "pending". Setting to "out" or "pending" should prevent the cookies from being written before the user has granted consent, as documen...

Ok, that's great that it's working for you now. Yes, it's better to leave that option selected. Even if the YouTube IFrame API script happens to be loaded elsewhere, e.g. your developers load it in the web page itself, then not to worry, having this option selected won't cause the script to get load...