A streaming insight is a type of insight that analyzes streaming data in real time and triggers actions based on predefined conditions. A data action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. By using a streaming insight paired with a data action, a consultant can accommodate Cumulus Financial's request to track the daily transaction volume of each customer and send out a notification when the volume is outside the normal range. A calculated insight is a type of insight that performs calculations on data in a data space and stores the results in a data extension. A streaming data transform is a type of data transform that applies transformations to streaming data in real time and stores the results in a data extension. A flow is a type of automation that executes a series of actions when triggered by an event, a schedule, or another flow. None of these options can achieve the same functionality as a streaming insight paired with a data action. References: Use Insights in Data Cloud Unit, Streaming Insights and Data Actions Use Cases, Streaming Insights and Data Actions Limits and Behaviors

To use a dataset for date and time-based operations in segmentation and calculated insights, the data stream category type should be assigned as Engagement . Here's why:
Understanding the Requirement
The goal is to perform date and time-based operations (e.g., filtering customers based on specific dates or times) in segmentation and calculated insights.
This requires a data stream category that captures customer interactions or activities over time.
Why Engagement?
Engagement Data Streams :
Engagement data streams are designed to capture customer interactions, such as website visits, email opens, purchases, or other time-based activities.
These streams inherently include timestamps, making them ideal for date and time-based operations.
Use in Segmentation and Calculated Insights :
Segmentation often involves filtering customers based on their engagement behavior (e.g., "customers who visited the website in the last 7 days").
Calculated insights leverage engagement data to derive metrics like recency, frequency, and trends over time.
Other Categories Are Less Suitable :
Individual : Focuses on demographic or static attributes (e.g., name, age) rather than time-based interactions.
Sales Order : Captures transactional data but is not optimized for general engagement-based operations.
Profile : Represents unified customer profiles and does not directly support date and time-based operations.
Steps to Implement This Solution
Step 1: Assign the Correct Category
When setting up the data stream, assign the Engagement category to ensure it is optimized for time-based operations.
Step 2: Map Date-Time Fields
Ensure that relevant fields (e.g., interaction timestamps) are mapped correctly during ingestion.
Step 3: Use in Segmentation and Insights
Leverage the ingested engagement data for segmentation (e.g., "customers who engaged in the last 24 hours") and calculated insights (e.g., "average time between interactions").
Conclusion
The Engagement category is specifically designed for capturing time-based interactions, making it the best choice for datasets used in date and time-based operations in segmentation and calculated insights.

Explanation
The app details page shows the status of the app, such as active, inactive, or error. The tenant specific endpoint is a unique URL that is generated for each app and used to send data to Data Cloud from the web or mobile SDK.
References:https://help.salesforce.com/s/articleView?id=sf.c360_a_web_mobile_app_connector.htm&type=5

One possible reason why a new custom field is not available in the data stream is that the Salesforce Integration User, which is used to connect to the CRM source, does not have "Read" permissions on that field2. To fix this issue, the administrator needs to grant the appropriate permissions to the Integration User profile or permission set.