Actable Predictive Destination
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.
Go to the Data Pipelines tab and click Connections.
Click Add New under Destinations.
Select the Actable Predictive destination.
(Optional) Select the sources that you want to connect to this destination. You can always connect sources to your destination later. We’ll only show you eligible sources.
Configure your destination.
Client Id: Your Actable-supplied Client ID.
Client Secret: Your Actable-supplied Client Secret.
Click Enable Destination.
When you’re done setting up your destination, you can go to the Actions tab to see how we map source events to your destination.
You may need to add actions for this destination
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 destination. See our actions page for help setting up actions.
|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.
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 Data Pipelines 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
transaction, and then map your transaction fields.