Copy configurations between sandboxes
Last update: February 14, 2025
- Topics:
- Sandboxes
CREATED FOR:
- Intermediate
- Admin
- Developer
Learn how to copy configurations between Experience Platform sandboxes using packages. Easily replicate schemas, datasets, journeys, and more across your sandboxes to support release processes and multi-region/multi-brand deployments. For more detailed information, see the sandbox tooling documentation.
Transcript
In this video, we will showcase how Sandbox Tooling can drastically help you reduce time to value and optimize your development lifecycle, enabling customers and implementation teams to replicate successful configurations across multiple sandboxes effortlessly. In the typical development cycle, you often create objects like schemas, audiences, and journeys. Unfortunately, replicating those objects from the development sandbox to other sandboxes is painstakingly manual and repetitive. But by introducing the Sandbox Tooling in Adobe Realtime CDP and Adobe Journey Optimizer, we bring you an innovative solution, packages. These packages allow for a smooth and seamless export and import of objects you add to them between different sandboxes. Now, let’s dive into a practical demonstration. ImagineLuma, a global airline company, is interested in sending a promotional email to their US Gold loyalty members, who have visited their website but have yet to book a ticket. Start in Luma development sandbox. Once data engineers and marketers build and test the required artifacts for the promotional email, I can create a package and start adding loyalty schemas to it. I can also keep adding artifacts to the package as needed, such as the PromotionJourney object. Once I have added all artifacts to the package, I can now go to the package inventory page and review it. Then, when I confirm all my artifacts are there, I can publish the package to make it ready for import into other target sandboxes. The package is available on the organizational level to be imported to various target sandboxes that are representing different business units, brands, teams, and geographies. I will switch to the Luma UI sandbox to import this package into the production sandbox. Click Import Action on the package. In the import workflow, select the target sandbox as Luma US. In the next step, I can review all assets included in the package. And what’s even more powerful, the system will auto-detect the dependent objects that are required for importing the selected artifacts. I can also choose to replace the dependent objects with an existing one in the target sandbox. This is important to help reduce object proliferation when not necessary. Monitoring and alerts are enabled to provide transparency for both package export and import jobs. I will also get a notification. When I see the package is successfully imported to Luma UI sandbox, I can go to the Schema, Audience, and Journey Browse pages to validate all artifacts are successfully created. Also worth noting is that all governance and consent labels added on schemas and audiences are copied over in the same import job. All export import operations are recorded in the audit log, ensuring your business is effectively compliant with corporate data stewardship policies and regulatory requirements. Sandbox tooling is a foundational capability that supports both real-time CDP and Journey Optimizer objects. Thank you for watching this demo.
Previous pageUse sandboxes
Next pageShare packages across IMS Orgs
Experience Platform
- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Platform-based applications
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- User interface
- Roles and project phases
- Introduction to Real-Time CDP
- Getting started: Data Architects and Data Engineers
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- AI Assistant
- Audiences and Segmentation
- Introduction to Audience Portal and Composition
- Upload audiences
- Overview of Federated Audience Composition
- Connect and configure Federated Audience Composition
- Create a Federated Audience Composition
- Audience rule builder overview
- Create audiences
- Use time constraints
- Create content-based audiences
- Create conversion audiences
- Create audiences from existing audiences
- Create sequential audiences
- Create dynamic audiences
- Create multi-entity audiences
- Create and activate account audiences (B2B)
- Demo of streaming segmentation
- Evaluate batch audiences on demand
- Evaluate an audience rule
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Audit logs
- Data Collection
- Collaboration
- Dashboards
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Delete datasets and batches
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Lifecycle
- Destinations
- Destinations overview
- Connect to destinations
- Create destinations and activate data
- Activate profiles and audiences to a destination
- Export datasets using a cloud storage destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Activate through LiveRamp destinations
- Adobe Target and Custom Personalization
- Activate data to non-Adobe applications webinar
- Identities
- Intelligent Services
- Monitoring
- Partner data support
- Profiles
- Understanding Real-Time Customer Profile
- Profile overview diagram
- Bring data into Profile
- Customize profile view details
- View account profiles
- Create merge policies
- Union schemas overview
- Create a computed attribute
- Pseudonymous profile expirations (TTL)
- Delete profiles
- Update a specific attribute using upsert
- Privacy and Security
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- Set up customer-managed keys
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries and Data Distiller
- Overview
- Query Service UI
- Query Service API
- Explore Data
- Prepare Data
- Adobe Defined Functions
- Data usage patterns
- Run queries
- Generate datasets from query results
- Tableau
- Analyze and visualize data
- Build dashboards using BI tools
- Recharge your customer data
- Connect clients to Query Service
- Validate data in the datalake
- Schemas
- Overview
- Building blocks
- Plan your data model
- Convert your data model to XDM
- Create schemas
- Create schemas for B2B data
- Create classes
- Create field groups
- Create data types
- Configure relationships between schemas
- Use enumerated fields and suggested values
- Copy schemas between sandboxes
- Update schemas
- Create an ad hoc schema
- Sources
- Use Case Playbooks
- Experience Cloud Integrations
- Industry Trends