# Actable Predictive

## About this integration

Actable Predictive is a customer prediction tool marketers. It trains models on your customers’ behavioral data (sent from any number of our CDP sources), and automatically scores your new data against those models. The scoring output helps you drive higher levels of customer engagement, lower levels of churn, and increased purchases.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

N/A

Actable Predictive

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Actable Predictive** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Client Id**: Your Actable-supplied Client ID.
        
    2.  **Client Secret**: Your Actable-supplied Client Secret.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Send Email Event

Send an email event to Actable for prediction. Use this to supply clicks, opens, and unsubscribes.

Send Web Activity Event

Send a Web (or app) event to Actable for prediction. Use this to supply events like page views, link clicks, etc.

Send Transaction Event

Send a purchase event to Actable for prediction. Purchase events should be in v2 Commerce Spec.

Send Custom Event

Send a custom event to Actable for prediction. Use this to supply events that are not in Actable 's customer view.

## The Stream Key and custom events[](#the-stream-key-and-custom-events)

Each action includes a `stream_key` field that determines type of event we’ll send to Actable. In general, you shouldn’t change this field **except when you set up a Custom Event Action**.

You might use Custom Event actions if your implementation contains transaction/purchase events that do not use the eCommerce Spec. For example, if you send purchase/transaction events that don’t conform to our specification, you might set up a custom event action and set the `stream_key` to `transaction`, and then map your transaction fields.