I do not send __view__ decision scope but the form-based activity from Target is returned (the one with target-global-mbox). If I set up page view event like that, does that mean that __view__ decision scope is returned by default? How that works?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
the __view__ scope is equivalent to the classic global-mbox and is afaik implicitly set.
Views
Replies
Total Likes
So its ALWAYS send by default with page view event or with any other decision scope?
Views
Replies
Total Likes
From my experience, you have to manually set the "__view__" scope in order to send the data to Target.
You can do it by manually entering the scope as a string or as a Data element.
The "__view__" scope is a general one, so it will render in any page. If you need your activity to only render in one specific URL or for a specific use case, I will use a different scope.
For example, for "categoryAffinity", I need to pass the "entity.categoryId" in all my pageViwes, so I will pass that info with a "__view__" scope, otherwise, if I need to only know "lastPurchasedItem", I will only use the "lastPurchasedItem" scope in the purchase Send Event.
Hope that helped.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies