How would this work on activities that run on every page of the site, such as a nav bar? You could capture ttMeta on every page and push into the products variable to get a rough estimate of the stated goal.
I like the idea. If you wanted to solve on your own, you could stand up a repo and push the offers via API.Target API v1.0 Not ideal for other folks benefitting from the comments in the Target interface, though.
I do not think this would be possible since the initial call to Adobe will not have all of the potential selectors that are on the page. In addition, I like that target-global responds with more than one activity since it can cut down on other test areas on the page. Less network calls.
Your global mbox (as defined in the setup panel) does return multiple offers. I am pretty sure that is why VEC is tied to global because Target does not know the HTML that will be on the page. You may have to parse the response from target-global client side before applying them.at.js functions