--- schema_version: "1" id: afd986fb707c156f35ba5974471a241fcbc3173b357a1a691987a95c38a1d1aa title: Data Actions in Data 360 collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_data_actions_cdp.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_data_actions_cdp.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e2fb4685b3276881e27fe675f9998399696b3a99696b99915b0eb05965063792 description: Monitor data changes in data model objects and calculated insight objects in Data 360, and send the change data events to the Salesforce Platform Event, Marketing Cloud Engagement, Webhook, or Amazon Kinesis targets. products: - Data 360 release: "264" --- # Data Actions in Data 360 Monitor data changes in data model objects and calculated insight objects in Data 360, and send the change data events to the Salesforce Platform Event, Marketing Cloud Engagement, Webhook, or Amazon Kinesis targets. A data action can be triggered based on certain conditions and can enable downstream systems to drive an action or orchestration. Three categories of data that can trigger a data action: - Change Data Capture events: For example, a profile record is inserted/updated/deleted in a data model object (DMO). - Streaming events: For example, data comes in from your SDK, ingestion API, or Marketing Cloud Personalization. - Streaming Calculated Insights: For example, insights that are based off streaming data coming into Data 360. You can use a data action to focus on near real-time events and insights at different levels, for example, at the channel, product, account, service, sell, fulfillment, engagement, payment, and individual level. A data action can enable different types of event-driven integrations and orchestrations. - Orchestrate Salesforce CRM workflows with insights and data events from Data 360. - Integrate data actions in Mulesoft Anypoint by sharing aggregated event data with external partners based on criteria. - Integrate with SaaS applications with signals from Data 360. - Trigger serverless functions that work with a webhook based on insights in Data 360. - Connect multicloud workflows or services when useful events happen in Data 360. - Push unfiltered insights and engagements to your data lake for analysis and storage. When you publish an event to Salesforce Platform using a data action, Salesforce uses the standard event `DataObjectDataChgEvent` for publishing messages. If the event is published to the home org or a companion org, Data 360 doesn't enforce publishing limits or allocation limits, particularly when the event is consumed on the platform (for example, via Flows). However, Data 360 enforces delivery allocation limits when the event is being delivered outside of the platform to an external subscriber, such as Mulesoft and AWS Lambda. When you publish an event to Salesforce Platform Event through a Data Cloud-triggered flow, it uses the data action functionality. The data action record home page displays the published record as Flow Integration under the Managed By column. To use a data action, first create the data action target that receives the results. - **[Data Action Targets in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_action_target_in_customer_data_platform.htm&release=264.0.0&type=5)** The result of a data action is triggered in a data action target. The target receives the data action in near real time. You can send a data action to a target to drive event-based orchestration. - **[Enrich Data Actions in Data 360 with Data Graphs](https://help.salesforce.com/s/articleView?id=data.c360_a_data_actions_data_graph.htm&release=264.0.0&type=5)** You can enrich a data action in Data 360 with related data graph attributes by including the data graph as a related object. - **[Create a Data Action in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_create_a_data_action_in_customer_data_platform.htm&release=264.0.0&type=5)** Use a data action to send an alert or event to targets such as Salesforce Platform, Webhook, or Marketing Cloud Engagement, or Amazon Kinesis. Create the data action to focus on near real-time events and insights at different levels, including the channel, product, account, service, or individual. - **[Create a Vector Search Data Action in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_create_a_vector_search_data_action.htm&release=264.0.0&type=5)** Create a vector search data action to act on the unstructured data in near real time and send an alert or an event. - **[Create a Real-Time Data Action in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_create_a_real_time_data_action.htm&release=264.0.0&type=5)** Create a real-time data action to send an alert or an event and get responses in real time. Use ‌a real-time data action to focus on real-time events and insights at different levels, such as the channel, product, account, service, or individual level. - **[Integrating Data 360 Data Actions with Flow](https://help.salesforce.com/s/articleView?id=data.c360_a_integrate_salesforce_cdp_data_actions_with_salesforce_flow.htm&release=264.0.0&type=5)** Data 360 data actions can send streaming events and insights to Salesforce Flow to drive an orchestration. An orchestration uses stages, steps, and decisions to organize complex business processes. - **[Troubleshoot Data Action Errors](https://help.salesforce.com/s/articleView?id=data.c360_a_data_action_troubleshooting.htm&release=264.0.0&type=5)** Get tips for solving the most common data action and data action target errors. - **[Billing Considerations for Data Actions](https://help.salesforce.com/s/articleView?id=data.c360_a_billing_considerations_for_data_actions.htm&release=264.0.0&type=5)** Use of Data Actions impacts the consumption of credits in these usage types. #### See Also - [_Salesforce Help_: Platform Event Allocations](https://developer.salesforce.com/docs/atlas.en-us.248.0.platform_events.meta/platform_events/platform_event_limits.htm)