- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
@ca90883831 wanted to provide some feedback in case you might be interested...
1. My experience is that you can have multiple mboxes placed on the page this includes a global mbox and a custom mboxes. I like to think of the global mbox as the one you fire on each page. This will make sure we can introduce experiences into the page using the VEC editor. Then if we have unique experiences using the form based editor, we then use a dedicated custom mbox so as to limit the scope.
2. Since the global mbox is focused on supporting use cases that leverage the VEC editor, and the VEC editor in turn captures a css selector from the user from one of the options when editing(insert after, before, or manually), the global mbox response on the client side will always have a "selector" value under "action" object. You can actually pass in this key value pair in your applyOffer() function and when the at.js script runs the script it will do the same and find the css selector and inject the html into that spot.
3. The auto create global mbox is something you can control at the script level, so you can create two versions of the script for each domain. Additionally if you use Launch you can control it from there.
4. Typically arrays perform slightly better than objects in terms of efficiency. I dont know if the at.js script has any conditions that look at one over the other first as an example therefor being executed faster.
Hope this helps and best of luck!