Welcome to the **Plug&Play Library** - a collection of our **ready-to-launch Use Cases** designed over thousands of hours and deployable within mere minutes. Previously, all P&P Use Cases needed to be deployed to client projects by business consultants. However, the Library makes the deployment effortless so that you can launch the campaigns **by yourself without assistance.**
# Why use the Plug&Play Library
What usually takes hours and an entire team of technically adept marketers, you can easily deploy yourself using the Library. Whether following our thorough documentation for each Use Case or using our newest in-app guide feature that walks you through the entire process, launching pre-set advanced campaigns is now effortless!
The Plug&Play Library elevated your campaigns, spanning from emailing and SMS to web personalization, with even [more Use Cases](🔗) continually added to the collection. Watch the Library increase your ROI, maximize your reach and deliver an unparalleled customer experience.
# How the Plug&Play Library works
The Library is comfortably located within the main menu on the left side.
All Use Cases currently available in the Library are in the form of tiles. The Use Cases are separated into categories based on the channel they utilize - e.g., Email marketing, SMS, and Web Personalization.

Every tile comes with a detailed overview, including what goal the Use Case serves, what metrics can be improved with it, and the maturity/difficulty of the Use Case.

Click the 'Build use case' button to start the deployment process through which you are guided via:
the documentation linked to each Use Case
in-app guide feature enabled by hitting the 'Start tutorial' button
Most Use cases have a set of requirements that have to be fulfilled before you can download the Use Case.

These requirements fall under two categories:
Automatically checked (mandatory/optional)
Manually checked
Engagement checks the automatically checked requirements by evaluating the project's data structure and determines whether they are fulfilled.
For those requirements that Engagement does not check, you need to check yourself. Usually, these refer to the data structure, and you should navigate to _**[Data Manager](🔗)**_ before checking the checkbox and moving forward.
Checking all the requirements enabled the 'Next' button to move forward.
Upon clicking 'Next', the Use Case will be downloaded. A Dependency Review will follow where you need to click on 'Apply' and continue with the process until the Cloning is complete.

If the Use Case has been downloaded previously, then during Dependency Review, some of the Use Case assets might need resolution - always click on Duplicate and then Apply.

Once the Use Case is downloaded, you will see the Use case setup. It usually contains a predefined and customizable Preview Campaign, a Production Campaign, and a Dashboard.

All that remains is following the concise in-app guide/documentation steps, and you will be all ready to launch your Plug&Play Library campaign.
# Common obstacles
### Cloning fails
Check whether another Use Case of the same name is present in the project. You can check this in _**[Initiatives](🔗)**_. If yes, renaming the initiative can help resolve the issue.
### Unfulfilled requirement
Check in the _**Data manager**_ whether such an event or customer property is set up. If your project uses a different name for the event/property, check in _**Data manager > Data mapping**_ if it is correctly mapped. In the _**Data manager**_, check whether values are tracked for the required event/property.
### Cannot access the next steps
Access depends on your access rights or the role you have. Not everyone might be able to download a Use Case as your rights might not allow it. The same goes for editing Use case Scenarios, Dashboards, Weblayers, etc. You might need help from users with granted access or ask to have their access updated.
### In-app guide disappeared
Sometimes, the guide disappears if some expected action has been skipped. Try to navigate back to the last step where you saw the guide. If not possible, try navigating back to the Use Case tile in the Library and restarting the guide by clicking on the 'Start Tutorial' button in case the guide disappeared before Downloading the UC. If a Use case has already been downloaded, you can rename/delete it and try again. If that is not an option and much time have been invested into the Use case setup, follow the documentation available, as that contains all the steps from the in-app guide and more.
### Repeated Use Case
If the Use Case has been previously downloaded, the following window will be displayed. Decide whether you want to open the existing use case or start anew and create a new Use Case.

Limitations
Upon downloading the Use Case into a project, a correct data structure, and well-filled-out data mapping will take care of most inconsistencies that could cause the Use Case not to download and display errors.
However, one known limitation is the inability to download a Use Case multiple times. Please navigate to _**Initiatives**_ and change the name of the previously deployed Use Case or delete it if you wish to start anew.
Naming conventions
To better distinguish the difference between the regular P&P Use Cases and those in the P&P Library, look at the first letter of the Use Case. Library Use Cases begin with the letter "L." For example, while the regular P&P Use Case of Abandoned cart is called OACP, the Library version is named **L**ACP.