in our implementation Analytics hit data get copied to Audience manager
server-side as a result all segment based on analytics hit get qualified
real-time (next click)Segments based on Analytics variable (evar or
prop) has few hours delay (due to completion of post processing)Note: We
only publish segments from Analytics where complex journey and if/then
condition is use. Also analytics segments are limited based on your
Correction: there are limitations to my suggestion below for at.js 2.x.
But here's a workaround provided by my colleague in another community
___ Hi @muerben , in addition to Moses's suggestion, try adding this
parameter to override location to test geo-segmentation and check the
response:?mboxOverride.browserIp=Be sure to do
this in incognito mode...
It really depends on a lot of factors. If it is a new Target
implementation, you could start with Web SDK. If you have a mature
Target program you will find that not every Target feature is supported
in Web SDK at this time and that there would be migration steps involved
to switch to Web SDK. But the goal is to have the single library support
all use cases. The product team maintains a public list of
supported/unsupported features here:
Hello, Do anyone have any tips on whether MVT can support a 2x3 on two
pages? For example, page A has two locations and 3 variables, we want to
carry the experience to page B and make it consistent, location A, say
color a should carry to page b location A also have a color a. Or this
has to be done via A/B? Thanks
Given both tests are running on the same page, have you tried excluding
test B audience from test A? When editing audience for activities,
there's an option called "visitor profile" and one of the drop-down
options is "not from other activities" Haven't personally tested this
before, but maybe you can create some kind of a rule combination of "not
from other activities" + "page name where you are running the tests"
Another possible solution is to add additional query parameters in the
URL where ...