Form-Based Experience Composer and Visual Experience Composer
If your company uses the Form-Based Experience Composer and the VEC, content from multiple Form-Based Experience Composer and VEC activities can deliver. Previously, only one activity from the form-based workflow could deliver. There is no longer a limit to the number of form-based activities that can deliver.
Activity delivery is determined using the following decision flow:
-
Target server call comes to Target with information about the Target request and URL.
-
Target pulls every activity running in that Target request.
-
Target attempts to match the visitor into activities.
If the visitor is already in an A/B Test or Multivariate Test activity, they match into that test until they convert. If they were previously in an Experience Targeting activity, they must match into it again. If they meet the audience rules, then the visitor falls into those activities and into specific experiences.
-
If a form-based activity is the highest priority, then that activity content is returned along with all matching activity content from VEC activities.
-
If a VEC activity is the highest priority, then content from all matching VEC activities is returned, but no form-based activity content is returned.
The results from all activities that run on the page are counted and reflected in the reports.
Example
If you have two activities, one targeting the branded search keyword “Nike” and the second targeting the non-branded keyword “sneakers”, the priorities of both activities are checked. If the Nike activity has a higher priority, that content is displayed. If the sneakers activity has the higher priority, its content is displayed.
If both targeted activities have the same priority, the activity that was most recently viewed is displayed. If the visitor is new to the page, the activity that was activated most recently is displayed.
Form-Based Experience Composer with non-global Target requests
If your company uses Target requests other than the global Target request in the form-based composer, content from only one activity can be returned per call. Activity delivery is determined using the following decision flow:
-
The Target server call comes to Target with information about the Target request and URL.
-
Target pulls every activity running in that Target request.
-
Target attempts to match the visitor into the highest-priority activity.
If the visitor is already in an A/B Test or Multivariate Test activity, they match into that activity until they convert. If they were previously in an Experience Targeting activity, they must match into it again. If they meet the audience rules, then the visitor falls into those activities and into specific experiences.
-
If multiple activities share priority level, there are two tiebreakers:
- If only one activity has audience targeting, that activity is displayed.
- If all or none has targeting, then the activity that was approved first is displayed.
Examples
Response: offer1
Two activities use only offers created in the Visual Experience Composer for different selectors
- Activity 1: target-global-mbox, selector1, visualExpCompOffer1, priority low
- Activity 2: target-global-mbox, selector2, visualExpCompOffer2, priority high
Response: visualExpCompOffer1, visualExpCompOffer2
Two activities use only offers created in the Visual Experience Composer for same selector
- Activity 1: target-global-mbox, selector1, visualExpCompOffer1, priority low
- Activity 2: target-global-mbox, selector1, visualExpCompOffer2, priority high
Response: visualExpCompOffer1, visualExpCompOffer2