Micro Experiences FAQs

General FAQs

How does MX compare to secondary orgs?

MX is set to eventually replace secondary orgs. We’ll provide a clear migration path once all secondary org use cases are covered by MX. In the meantime, you can deploy the same bundle used in your secondary org to a new MX and test.

Can I optimize client-side bundle size and page speed performance using MX?

Yes, but proceed with caution. While splitting your bundle across multiple MX instances can potentially optimize bundle size and improve page speed, improper implementation could lead to issues like redundant downloads of similar assets (e.g., React.js). We recommend thorough testing to ensure that splitting doesn’t negatively impact performance. We have an example of this scenario in How does Micro Experiences work?, “How does your Reader see MX related changes?” section.

Is there any negative impact on reader experience?

Splitting a multi-site setup into separate MXs should have no impact on reader experience. However, if you split a single-site experience into multiple MXs, it’s crucial to test the final bundle sizes. Readers transitioning between pages rendered by different MX instances might experience re-downloads of static assets, even if they are identical or similar.

What is the impact of MX on my SEO scores?

While there might be some impact on reader experience due to page loading times, crawlers won’t experience the same effects. In fact, smaller individual bundles and assets might improve your page speed scores, potentially leading to a positive effect on your SEO rankings.

Can I use Audience Targeting with MX?

Audience targeting is currently only supported on your default MX instance.

Can I use Bandito with MX?

Bandito is also limited to your default MX instance.

Can I copy pb-data between Micro Experiences using PB Data Sync API?

PB Data Sync API currently only works within the default MX instance.

How will my staff access multiple MX instances?

All staff members with PageBuilder access will see all MX instances.

Can I restrict a staff member’s access to only one MX?

No, if a staff member has access to PageBuilder, they will see all MX instances.

Can I use MX for testing?

MX can be integrated into your testing and QA workflows, though it may not support every QA use case. We encourage you to share your unique testing workflows and use cases with us for further consideration.

How does content authoring apps impacted by MX?

Content authoring tools like Composer, WebSked, Photo/Video center, are MX agnostic, even PageBuilder agnostic. These tools does not know how that content is delivered to readers. It is agnostic of wether PageBuilder is used, and to the same extent, which MX a piece of content should be rendered with.

When I request a new MX to be provisioned, do I get them in all environments?

Micro Experiences are environment specific. When you request provisioning a new MX to be created, you can ask your TAM that you want the same MX to be created in all environments, or on a specific environment.

Is Micro Experiences free?

Micro Experiences is free, opt-in feature, available to customers who currently use PageBuilder.

How many MX can I have?

Customers can have up to 5 Micro Experiences including the default MX. If you have a unique use case that requires more than 5 Micro Experiences, please reach out to your TAM.

Editor / Curator FAQs

I see multiple PageBuilder buttons (tiles) in my Arc Admin panel. Which one should I select?

Each tile represents a different MX instance. Select the one that corresponds to the content area or site you need to work on. For example, if you’re editing sports content, choose the PB-Sports tile.

I don’t see experiences, and there is no change in PageBuilder. Why?

This could be because you’re in the wrong MX instance. Double-check that you’ve selected the correct PageBuilder tile. If you’re still not seeing the expected content, verify with your team that the content is assigned to the right MX instance.

Why am I not seeing a feature I used to see?

Some features may be specific to certain MX instances. If a feature is missing, it might only be available in another MX. Check with your technical team to ensure the feature is enabled in the correct MX instance.

I don’t see pages I used to see. Why?

Pages are now segmented by MX instances. If you’re not seeing certain pages, they might belong to a different MX. Make sure you’re working in the right PageBuilder instance, or check with your team if the pages have been reassigned.

How can I preview or test my pages before going live with an MX?

See How to preview pages with MX for more information.

Developer FAQs

How do I troubleshoot issues?

We covered troubleshooting changes and methods in How to troubleshoot issues across multiple experiences

Will my redirects get impacted by MX?

No, redirects will work as expected.

Consider the scenario, a story gets updated with new circulation that changes it’s canonical URL, that creates a redirect object in Content Platform. When a reader goes to the old URL, the output of that first (old) URL hit will respond with the MX that renders the old url, and the response will have redirection header with the new URL. An the new URL can be rendered by another MX. This makes the redirections and content platform meta data, completely independent from experience platform (wether you use single MX or multiple MX to serve your reader traffic).

My static resources (logo, favicon, fonts) is not loading correctly

You need to adjust how you refer to your static resources in your code. If you haven’t replaced deployment() function you previously used to wrap your static asset references, you need to replace it with pageBuilderURL() function. See “Changes in Resource URLs“ section in Changes in Resource URLs in the MX Developer Guide for more information about this.

How does encrypted secrets works across MX?

Secrets are global within an organization and shared across multiple MX. You can safely use your secrets that you encrypted using Deployer > Secrets tool previously in your new MX and bundle. A common example is to use same .npmrc-encrypted file between your bundles. The encrypted value in your environment files, or files like .npmrc-encrypted gets decrypted at compile time when you make deployments before it is placed in its final render runtime.

How about secrets when migrating a bundle from one org to another?

If you are migrating your bundles from one organization to another (i.e: migrating from Secondary Org to Primary org), you need to use encrypted values in your bundles from the organization you’ll deploy your bundle to. For example, if you have OrgPrimary and OrgSec, and you had your bundle in OrgSec and moving to OrgPrimary, you need to update all encrypted references with new ones after re-encrypting your secres using Deployer > Secrets tool in the target org, in this example OrgPrimary. Previous secrets from OrgSec will not work when deploying same bundle on OrgPrimary.

Migration FAQs

How can I migrate my current pages and bundle to new MX?

See Planning your Micro Experience Migration for more detailed guide about migration strategy.

I Have 1,000 Pages, How Do I Migrate?

If you have a large number of pages to migrate, it’s important to approach the migration in stages. Start with the most critical pages and components, and gradually move other parts of your site. Use automated tools where possible to streamline the process, and ensure thorough testing at each stage to catch and resolve issues early.

Can I copy PB-Data to a new MX?

PageBuilder Data Sync API only works on default MX and once secondary experiences are supported with this API, it will still operate within the same MX.