Understand the Global mbox
- Topics:
- at.js
CREATED FOR:
- Developer
Information about the global mbox, a name used to refer to the single server call made at the top of each web page in your Adobe Target implementation.
By default, the global mbox is named target-global-mbox
. It can be renamed for your account, if necessary.
There are several differences between a regular mbox (non-global mbox) and the global mbox, including:
Regular mbox | Global mbox |
---|---|
A regular mbox typically wraps around content with a <DIV> tag. | The global mbox is “empty” and does not wrap around any content. |
Content from only one activity can be delivered in a regular mbox. | Content from multiple activities can be delivered in one response to a global mbox. |
If multiple activities are delivered via the global mbox or via multiple regular mboxes, Target determines the priority by which the activity (or activities) are delivered to a web page.
Additional page-level data can be sent to Target along with the global mbox by using the targetPageParams
function. This is similar to the mbox parameter functionality. For more information, see Passing Parameters to a Global mbox.
Target
- Adobe Target Developer Guide
- Getting started
- Before you implement
- Privacy and security
- Privacy overview
- Privacy and data protection regulations
- Target cookies
- Delete the Target cookie
- The impact of third-party cookie deprecation on Target (at.js)
- Google Chrome SameSite cookie policies
- Apple Intelligent Tracking Prevention (ITP) 2.x
- Content Security Policy (CSP) directives
- Allowlist Target edge nodes
- Methods to get data into Target
- Target security overview
- Supported browsers
- TLS (Transport Layer Security) encryption changes
- CNAME and Adobe Target
- Client-side implementation
- Overview: implement Target for client-side web
- Adobe Experience Platform Web SDK implementation overview
- at.js implementation
- at.js overview
- How at.js works
- How to deploy at.js
- On-device decisioning
- at.js functions
- at.js functions overview
- adobe.target.getOffer()
- adobe.target.getOffers() - at.js 2.x
- adobe.target.applyOffer()
- adobe.target.applyOffers() - at.js 2.x
- adobe.target.triggerView() - at.js 2.x
- adobe.target.trackEvent()
- mboxCreate() - at.js 1.x
- targetGlobalSettings()
- mboxDefine() and mboxUpdate() - at.js 1.x
- targetPageParams()
- targetPageParamsAll()
- registerExtension() - at.js 1.x
- sendNotifications() - at.js 2.1
- at.js custom events
- Debug at.js using the Adobe Experience Cloud Debugger
- Use cloud-based instances with Target
- at.js FAQs
- at.js version details
- Upgrading from at.js 1.x to at.js 2.x
- at.js cookies
- User-agent and client hints
- Understand the Global mbox
- Server Side implementation
- Server Side: implement Target overview
- Getting started with Target SDKs
- Sample apps
- Transition from Target legacy APIs to Adobe I/O
- Core principles
- Integration
- On-Device Decisioning
- Node.js SDK Reference
- Java SDK Reference
- .NET SDK Reference
- Python SDK Reference
- Hybrid implementation
- Recommendations implementation
- Mobile app implementation
- Email implementation
- API guides
- Implementation patterns