To global or to regional, that is the question | Community
Skip to main content
T
THE_DK
Level 2
April 30, 2020
Solved

To global or to regional, that is the question

  • April 30, 2020
  • 2 replies
  • 9449 views

I'm a bit new to Target and trying to build some guideline docs.  Can anyone point me to a 'best practice' on when to choose a regional mbox over global mbox?  

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by ryanr7

    Hi @the_dk,

    If you are talking about web use then typically the global mbox (AKA pageLoad for at.js 2.x) is the way to go as it allows you to use the visual experience composer (VEC) for experience setup.

    Regional mboxes (AKA locations) are used in other channels/use-cases such as IOT, native mobile app, email, and server-side implementations of Target. They can also be used in a regular client-side web deployment though the vast majority of cases can be accomplished with the global or pageLoad request.

    Here's a help doc that covers a little of this topic: https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/mbox-implement/global-mbox/understanding-global-mbox.html

    Hope that helps

    2 replies

    R
    Adobe Employee
    ryanr7Adobe EmployeeAccepted solution
    Adobe Employee
    May 6, 2020

    Hi @the_dk,

    If you are talking about web use then typically the global mbox (AKA pageLoad for at.js 2.x) is the way to go as it allows you to use the visual experience composer (VEC) for experience setup.

    Regional mboxes (AKA locations) are used in other channels/use-cases such as IOT, native mobile app, email, and server-side implementations of Target. They can also be used in a regular client-side web deployment though the vast majority of cases can be accomplished with the global or pageLoad request.

    Here's a help doc that covers a little of this topic: https://docs.adobe.com/content/help/en/target/using/implement-target/client-side/mbox-implement/global-mbox/understanding-global-mbox.html

    Hope that helps

      T
      THE_DKAuthor
      Level 2
      May 14, 2020
      Again thanks! we have A4T set, so good there. Our use case is concerning the case of say 3rd party data needed for an Activity. Another case is we need to derive a data layer data point from the DOM, assume we have no server-side generated data layer., to pass as a param to Target. In both of these instance, the global mbox use would hold up delivery of said global mbox right? and introduce massive FOOC right? Or am I missing something?
      K
      Adobe Employee
      karandhawanAdobe Employee
      Adobe Employee
      May 20, 2020

      @the_dk  If you are building a Target activity through VEC, then these would always be configured using the target-global-mbox.

      Regional mboxes are used to configure form based activities which are used for channels such as mobile apps.

       

      Regards,

      Karan

        Terms & ConditionsAccessibility statement

        Loading footer...