There are three activities that often get conflated or confused: Continuous Integration, Continuous Delivery, and Continuous Deployment.
Continuous Integration is simply integrating the work of individuals or teams on a continuous basis. You want to frequently merge code changes from multiple individuals or teams into a shared, common branch frequently. You then want to run automated tests to ensure that you can build the software and that it remains stable. Automated builds tests are key to Continuous Integration, as is frequently merging code from multiple people or teams. Although you have confidence in the software product, you don't have a deployable artifact yet - you may not have release build executables, installers, configurations, and so on.
Continuous Delivery is the next step beyond Continuous Integration. The outcome of Continuous Delivery is a deployable product. Not only do you build and test, but you produce a production-ready build frequently. However, this build is not deployed to production. The decision to deploy a build is still a human decision. I have seen cases where the end result of Continuous Delivery is an automated deployment to a test, staging, pre-production, or similar non-production environment. Deployment may be a manual process or an automated one, but the outcome of Continuous Delivery is the input to your deployment process.
Continuous Deployment automates the deployment. Every successful build represents a deployment, often to a production environment. It requires Continuous Integration and Continuous Delivery to be successful.