A data element can return one value only, yet from your code, it looks like you want to return a value whenever a "Product Search" event is found in your digitalData.event array. So generally, that data element isn't going to work reliably. Also, recall that a data element only gets executed when it...

If "isPageView" is false, then your hit is being tracked most likely as a Custom Link. If you've implemented AppMeasurement.js directly, then verify that you're using s.t() to track your page views instead of s.tl(). If you've implemented via AEP Tags with the Analytics extension, then verify that y...

I assume that you're setting the "productListItems" field in the Web SDK hit's XDM object. For each item object in the "productListItems" array, there is a "priceTotal" field. As the field name implies, you should be using the total value of the items for the tracked quantity. For example, if your i...

I believe you should be using the getUrlVariables method: https://developer.adobe.com/client-sdks/documentation/identity-for-edge-network/api-reference/#geturlvariables See this tutorial: https://experienceleague.adobe.com/docs/platform-learn/implement-mobile-sdk/app-implementation/web-views.html?la...

Can you share the page URL where you have this YouTube video problem?

IIRC I too experienced a jump in Internal URLs when migrating to Web SDK. I never really figured out why that was the case. But it eventually "sorted itself out" after a month or 2.

Looks like an error in the Analytics product. Open a ticket with Customer Care for the Engineering team to check.

@igarciacufree ,  1. Yes, the missing "origin" parameter is the most likely cause. Although I would expect Adobe's extension to add that parameter to your YouTube embed URL if it's not already there. 2. Since there is the CORS error, then the YouTube IFrame API script is not being loaded, and so non...

I normally prefer to always use the latest version of AppMeasurement.js, because it would include all of the latest bug fixes and maybe some enhancements. From my experience, I haven't had any tracking breakage when always updating to the latest versions.

That incorrect s.pageURL was probably the reason. Since it had been incorrectly tracking the hostname only, so the "utm_medium" parameter would not have been tracked to AA. See if your problem gets resolved, now that you've set s.pageURL to really be the location URL.