We are migrating a client to the Web SDK. Their front end used to make a bunch of target.getOffer() calls using named mboxes to get back JSON data telling it which experience to render. To migrate to alloy, we duplicated this with (roughly) this code:
alloy("sendEvent", {
renderDecisions: false,
decisionScopes: [
"mbox_name_goes_here"
].flat(),
data: _satellite.getVar("Target Profile Params") || {}
})
It works like a champ from a test delivery standpoint. However, when I look at the edge trace, I see that in addition to the scope that we include in the array, __view__ is added as well. The target_trace items show the global mbox being called. There are several of these calls made on one page (working to get that changed, but that is another tale), so it seems a lot of extra work.. We eventually WANT the global mbox tests evaluated when we track the page view.
Something worse that I think might be related to this is that even though no tests had propositions returned that would be rendered automatically (we have to do propositionDisplay calls later for those), there is an analytics hit sent. Since this can be a landing page, this means the first hit in the visit is NOT the page view, and our campaign first touch is usually unspecified AND when looking at evars using the Visit metric we frequently see Unspecifieds for everyone (along with the value we want).
Is this expected behavior? Any way around it? If I wasn't already bald, I would be pulling my hair out.
