Avatar

Level 2

@Robert_Calangiu

 

Hello, repost my previous questions: 

 

All my questions below are for “form based exp composer”:

 

  1. We use form based experience composer to create Target A/B test. Currently we are using a few regular mboxes on the page. Can I introduce Target global mbox together with regular mbox? aka. Is there an issue to mix global mbox and regular mboxes together? Is global mbox better than regular mbox? 
  2. I understand we can use “targetPageParams” to pass additional parameters to global mbox.  In at.js 2.x, the global mbox uses 2 functions [adobe.target.getOffer() & adobe.target.applyOffer()]. But how does Target know where exactly to apply offers on a page when using global mbox? With regular mbox, you wrap content in <div>. With global mbox, how to specify the location on the page?
  3. We have 1 target account shared across 2 different teams for 2 different domains. So if my team switches to use global mbox, the other team also need to make the same change?
  4. When passing parameters to global mbox using “targetPageParams”, is there any preference to use one method over the other 2 ?  “An array” or “JSON” object or “Query String”, which one is better?