Auto Create Global Mbox vs. Custom Global Mbox | Community
Skip to main content
bkmills1
bkmills1
Level 3
July 23, 2018

Auto Create Global Mbox vs. Custom Global Mbox

  • July 23, 2018
  • 1 reply
  • 11112 views

Hello,

Our team is working to reduce flicker as much as possible in our test activities, and are weighing the options for using a Custom Global Mbox (current implementation) versus auto-creating a Global Mbox.

What are the potential adverse affects of switching from one to the other, particularly as it relates to live test activities? I understand that once saved, all activities will sync with the auto created mbox. This doesn't sound like an  ideal scenario.

Can the implementation be changed to use Auto Create and continue to use the custom name? Is there a way to sandbox this before committing to making the switch?

Thanks,

Brion

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

    1 reply

    R
    Adobe Employee
    RamiHammadAdobe Employee
    Adobe Employee
    July 23, 2018

    Hey Brion,

    In general at.js is better suited at reducing flicker on the page as per: How at.js Manages Flicker

    Having said that, if you are creating VEC activities, you must have Global MBOX Autocreate enabled in at.js to ensure content is delivered correctly to the page. In general we do not suggest to have any customization done to the at.js library, so it is best to test with an at.js with Auto create Global mbox.

      bkmills1
      bkmills1Author
      Level 3
      July 23, 2018

      Thank you, Ram!

      We are currently using at.js, but still experience some flicker in tests.

      Considering the VEC and auto creating Global Mboxes, does the same apply with regard to the Form-based Composer? We use both VEC and FBC.

      It sounds like the best (only) way to avoid flicker is to use Auto Create?

        R
        Adobe Employee
        RamiHammadAdobe Employee
        Adobe Employee
        July 23, 2018

        Hey bkmills1,

        The best way to go about this is to use the Global Auto Create with at.js.

        As for the form based composer auto create is not essential in this case.

        However, if you are still experiencing flicker with at.js and auto create global mbox, then try disabling the mbox on the page by using mboxDisable=1


        Troubleshooting Content Delivery

        if you are not continuing to have the flicker issue after disabling the mbox, then it may be best to create a support ticket with Customer Care as this would need more investigation

          Terms & ConditionsAccessibility statement

          Loading footer...