All templates
Customer targeting

Repeat purchase readiness

Know which customers are ready to buy again — using Google Cloud SQL (SQL Server)

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

Google Cloud SQL (SQL Server) logoIf you're using Google Cloud SQL (SQL Server) for managing your customer data, integrating Faraday's Repeat Purchase Readiness predictions can be a smooth and beneficial move. With these predictions, you can easily identify which of your customers are most likely ready to make another purchase, directly in your existing database setup. This means you can make smarter marketing decisions and target your campaigns more effectively without having to juggle between different tools. It keeps everything streamlined and lets you get the most out of both your data and your marketing efforts, all within the familiar environment of Google Cloud SQL.
  1. Step 1

    Connect your data sources

    Use the link below to connect Google Cloud SQL (SQL Server) 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. This link 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 repeat purchase scoring pipeline and deploy to Google Cloud SQL (SQL Server)

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

    Deploy to Google Cloud SQL (SQL Server)

    Create a deployment target using the Google Cloud SQL (SQL Server) connection you created above. Or, get started by simply deploying to CSV.