All templates
Customer targeting

Churn scoring

Know which customers are ready to churn while there's still time to save them — using Aurora (MySQL)

You’ll need a Faraday account to use this template. It’s free to sign up and you can use sample data to start.

Aurora (MySQL) logoSure thing! If you're using Aurora (MySQL) and you're also a Faraday user, you might find that churn scoring predictions could be a great addition to your toolkit. With these predictions integrated into Aurora, you can seamlessly identify which customers are most at risk of leaving your brand. This allows you to act proactively and tailor your marketing or customer service efforts to retain those customers. By having this valuable information right at your fingertips within your Aurora database, you can make more informed, data-driven decisions without needing to juggle multiple tools or platforms. It's a straightforward way to enhance customer loyalty and ensure you’re addressing churn risks as efficiently as possible.
  1. Step 1

    Connect your data sources

    Use the link below to connect Aurora (MySQL) to Faraday. You can also skip this step and use CSV files to get started instead.
  2. Step 2

    Ingest your data into event streams

    This allows Faraday to understand what your data means. These links will guide you through ingesting the data necessary to power this template.
  3. Step 3

    Organize your customer data

    You'll create groups, called cohorts, that are the essential building blocks of Faraday and allow you to easily predict any customer behavior.
  4. Step 4

    Declare your prediction objectives

    With your cohorts defined, it's easy to instruct Faraday to predict the necessary behaviors. Follow the docs with the link below.
  5. Step 5

    Define your churn scoring pipeline and deploy to Aurora (MySQL)

    Finally, deploy your prediction with the link below.
  6. Step 6

    Deploy to Aurora (MySQL)

    Create a deployment target using the Aurora (MySQL) connection you created above. Or, get started by simply deploying to CSV.