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

To global or to regional, that is the question

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.
    ryanr7Accepted solution
    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

    View reply

    5 replies

    karandhawan
    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

    Translate
      ryanr7Accepted solution
      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

      Translate
        THE_DKAuthor
        Level 2
        May 8, 2020
        thanks Ryan! Hoping you can help me get my head around this use case though. We may have the need to load a mbox or 'location' passing in data captured from user interaction or data that is fetched from a server call. If I'm following correctly, this would cause holding up the global mbox from completing and thus holding the whole UI causing lots of flicker. Would it be a best practice to maybe say that if an activity/test needs specific data not available at page load, use a region? l?
        Translate
        Terms & ConditionsAccessibility statement

        Loading footer...