Set up your project environment

During the sales process, members of the Purple team will usually create a demo app for you to check out some Product Features.

As soon as the contract is signed, we create at least two apps on your behalf: An app for the staging environment and an app for the production environment. Both Apps use the latest version of the Purple Experience (PXP) by default.

Throughout the project lifecycle, the version of the software running in your apps may vary: We utilize the staging app to test the integration with any third-party tools you may require before pushing changes to the production environment. We also change any custom development and styling on staging to avoid causing issues with your editor's preview. To do so, we use Purple Experience Builder (PXP Builder).

To get the most value from this setup, you must provide the proper configuration to have all your 3rd Party integrations configured in that staging environment. 3rd party integrations include, but are not limited to Tracking, Ads, Widgets and Entitlements.

You'll need to keep a close eye on your staging and production environments setup, particularly for configurations that can be made from the Purple Hub. We only loosely structure them through the software, so there are degrees of freedom that can cause variations in configuration, which oftentimes results in some confusion throughout the project lifecycle.

Defined Apps are set up with Performance monitoring, if applicable. If we do this, we usually configure both, the released software and the latest nightly version, to ensure there is no performance degradation introduced neither from the product nor via configuration.

Your apps are connected to Purples' Content Cloud. Any content you control is stored and managed in that cloud, utilizing Purple Manager and Purple Hub (depending on your Product). Your staging environment may access multiple Purple Hubs to ensure that proper test content is provided.