@Jennifer_Dungan , my point was that you can't have the Pages dimension (from the Page View hit) be WITHIN the same Hit as the Scroll (v46) dimension (from the scroll hit), because the dimensions are tracked with 2 different hits. That's why I had proposed using WITHIN 1 Page View or AFTER 1 Hit.

You can use the Google Data Layer extension to help you work with your Google Tag Manager-based dataLayer.

Yes, in AA terminology, Natural Search = organic search.

Adding on to @Satyam_Gupta1's answer: unfortunately, you can't fix the number of breakdown rows. If you were to replace a broken down dimension that has your desired number of rows with another dimension, that replacement breakdown will retain your desired number of rows.

It should be WITHIN 1 Page View or AFTER 1 Hit, not WITHIN 1 Hit. Since a Hit is AA's unit of measure, the page view hit and the scroll hit cannot happen in the same hit (assuming that the scroll gets tracked with a Custom Link beacon).

In AA terminology, image request = beacon = hit. So yes, all hits.

What if you add a new field in your schema for the array of string? So you have 2 fields: one that is the original one that is of string type, the other new one that is of array of string type. That also gives you the flexibility of sending data with either type.

I assume you're referring to AEP Tags. What you've described is correct for Custom Code actions. However, Custom Code events and conditions are always included in the JS file. Also, all other extensions' components get included in the JS file too (unless the extensions developers have done otherwise...

This screenshot shows your "New" and "Repeat" values only. The values look correct.

Try this: use a list prop to track your search term. Reference for list props: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/prop.html?lang=en#list-props For example, let's say you have configured prop13 as a List prop and track your search terms to it. Assuming you...