Skip to main content
All CollectionsAdvanced Topics
MetaLocator Staging Environment
MetaLocator Staging Environment

Access and behavior of the MetaLocator staging environment

Michael Fatica avatar
Written by Michael Fatica
Updated over a week ago

Periodically customers will require a sandbox or otherwise non-production environment for experimentation and testing in MetaLocator. MetaLocator offers three strategies for the establishment of a staging environment.

  1. Customers are free to establish a new trial account. This trial account must be created under a separate email address, in which they can perform all manner of tests as required. If needed, customers can request permissions and add-ons that mirror their production environment. Trial accounts last only 30 days and can not be used for production purposes.

  2. Customers can request access to our staging environment. The staging environment is a sanitized copy of the production data which is periodically synchronized with production. Staging accounts must not be used for production purposes (e.g. installation on customer production Websites). In this staging environment the following conditions are present:

    1. Customers log in with a numerical version of their production identity, (E.g., if your production User Id is 12345. This avoids the need to manage multiple email addresses.

    2. Staging does not send any email. This prevents the accidental email of real customers through our lead and other email functions. Password resets, normally handled via email, can be requested via the help desk.

    3. Staging does not send any text messages.

    4. Staging does not trigger or track internal analytics.

    5. Staging is initialized with an anonymized set of data from the production environment. Email addresses, leads, reviews and phone numbers are removed or anonymized.

    6. Staging is periodically refreshed with production data. This occurs every 30 days after the account is established, or upon request. Interface settings are not synchronized, as they can contain sensitive information.

    7. Staging should be used to store, backup or otherwise save data and settings. Staging is periodically refreshed and data loss could occur.

    8. When switching accounts between staging and production, deleting cookies may be necessary if you are unable to log in.

    9. Staging is not nearly as powerful as our production systems, and so performance is not indicative of production systems.

  3. Customers can purchase a separate, standalone production account. When staging requirements include publishing real data in a production environment as in a large migration or transition, a separate, standalone account can be purchased. Migrating data and settings between production would be done via the usual import and export controls.

Did this answer your question?