---
schema_version: "1"
id: 26d030975d8bd9e1a33bd9d75272eb1130741c0835a2ffc9db46e58109f5bc14
title: Create a Web or Mobile App Data Stream
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/guides/c360-a-mobile-web-datastream.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-mobile-web-datastream.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 77b4074f58a23e28c47b0294c1991eb1cb7c13f8a2427472366dbbf6dbdbda7d
products:
  - Data 360 Integration Guide
  - Data 360 Developer Documentation
---
# Create a Web or Mobile App Data Stream

Create a data stream to begin the flow of data from a website or mobile app. Data 360 ingests engagement data every 15 minutes and profile data every hour from the website and mobile apps.

| Edition Table                                                                                                                                                               |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Available in: **All Editions** supported by Data 360. See [Data 360 edition availability](https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&type=5). |

| User Permissions Needed                    |                      |
| ------------------------------------------ | -------------------- |
| To create a web or mobile app data stream: | Data Cloud Architect |

In Data 360, navigate to the Data Streams tab.

1. Click **New**.
2. Select either a mobile app or website data source.

   **note:** If you don’t see the data source that you want, confirm that your Data Cloud architect uploaded the JSON schema for that application.

3. Click **Next**.
4. If you have more than one mobile app or website data source, use the **Mobile App or Website** dropdown menu to select the data source for this data stream.
5. Select the events to include in the data stream and click **Next**. The events are pulled from the JSON schema uploaded in Setup.

   **note:** Select events that are categorized as "Profile", "Engagement", or "Other". Data 360 displays an error message for events categorized differently.

6. Review the list of selected events, their associated fields, and how the data source objects are mapped to the data model objects.
7. Click **Next**.

   **note:** A separate data stream is created for each event with `category = "Profile"` or `category = "Other"`. A single data stream is created for all events with `category = "Engagement"`.

   Data streams in the Engagement category that use append mode provide at-least-once delivery. Data 360 stores every ingested event at least once. In rare cases, such as when a client retries after a network timeout or Data 360 reprocesses events during service recovery, Data 360 can store the same event more than once.

   Append mode retains all records without deduplication by primary key. As a result, the data lake object can occasionally contain multiple records with the same primary key, such as `eventId`. If your use case requires exact counts, deduplicate records in your queries or downstream processing. Engagement data streams that use upsert mode merge records by primary key to prevent duplicate records.

8. If you have more than one data space, select the data space for this data stream using the **Data Space** dropdown menu.
9. Choose the refresh mode for each profile event data stream using the **Refresh Mode** dropdown menu. You can set each profile event data stream to refresh data either incrementally or partially.

   **note:** In incremental mode, when the data stream receives updated field values, the data stream updates the new fields and values, and it populates unchanged fields with blank values. In partial mode, when the data stream receives updated field values, the data stream updates the new fields and values, and unchanged field values remain the same. Also by default in partial mode, changes apply only to user profile events received with the same device ID.

10. To create the data stream, click **Deploy**.