Some documentation here:
Analytics segments are not for 1st page hit and have latency.
Thank you, @GentryLin, very helpful! For 1, the context is it seems
there are two ways of integrating AEM and Target, one being Target is
part of AEM and test build is within AEM, another is to have AEM and
Target connected but Target is separated from AEM, but fragments can be
exported. I'm looking at how to assess the two different approaches,
flexibility, agility, efficiency and future expandability and
scalability. Thanks much!
Hi @GentryLin, Another very specific use case on how data is passed
between AEP and Target. Hypothetically if experiences created in Target
needs to tailor to an audience based on click event on 3rd party
properties (clicked on a social ad for example), how does the data flow
between GTM, AEP, and Target? Thank you!
Hi @GentryLin, good morning! Would love to get your input on two
questions: 1: Target and AEM. Will Target be decoupled from AEM in the
future? 2: Target and AEP. For Target to consume AEP audience info, are
there additional requirements on the Target side? Thank you!
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
Wouldn't you first set up audience who qualified for B? then split the
traffic and then exclude that from A and split again. By default, you
are already artificially separating the segments. So it's not 50%/50%
for A and B, it is B, then 50/50, and then exclude B, then 50/50 again.
Hello! Can I get some clarification wrt to how to connect AEP and
Target? From what I gathered, currently AEP has to leverage Audience
Manager? In the absence of Manager, it can work with tag extension as
well? With the beta release, I'm assuming the connection becomes