Use a Global mbox from a legacy implementation
- Topics:
- at.js
CREATED FOR:
- Developer
By default, Target creates a global mbox called target-global-mbox, which is used to run activities created in Target. However, if you have already created a global mbox on your pages for your legacy implementations, you can use that mbox for your Target activities.
To use your existing global mbox for both Target and your legacy implementation, you must set a few parameters.
-
Go to Target, then click Administration > Implementation.
By default, Page load enabled (Auto-create global mbox is enabled, and the custom global mbox is named
target-global-mbox
. -
If you want to use an existing mbox, disable Page load enabled (Auto-create global mbox, and specify the name of a previously created global mbox in the Global Mbox field.
The Global Mbox drop-down lists all mboxes in your account. If you want to use an mbox that does not yet exist, create the mbox.
-
Click Save.
The settings for your account are updated.
-
Download the new at.js file and reference it on your site.
All existing activities update to use the specified global mbox, including activities that have previously been created and implemented.
Troubleshooting global mbox implementation
The following FAQs can be used to troubleshoot your global mbox implementation:
Why is the global mbox not loading, or why is there latency in loading the global mbox when the page loads?
Make sure the at.js reference is the first JavaScript call on the page. For other solutions to this problem, see Global mbox Frequently Asked Questions.
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