--- schema_version: "1" id: def6175193137b4c43bda44fd0572f907b5d7bf9b2b747525664b547c1f35580 title: Data Extension Entry Source collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_jb_data_extension.md canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_data_extension.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 4e87f98b4c7fb77bab19095824766012c5446ac24027c5447a8e799bd7fa8230 description: The data extension entry source lets you choose a sendable data extension, then admit contacts in that data extension into a journey in a batch. You can configure a filter to control which contacts enter or admit all contacts in the data extension. You can also use Automation Studio to create and refresh the data extension, or you can use an SMS list created in MobileConnect. products: - Marketing - Marketing Cloud Engagement release: "264" --- # Data Extension Entry Source The data extension entry source lets you choose a sendable data extension, then admit contacts in that data extension into a journey in a batch. You can configure a filter to control which contacts enter or admit all contacts in the data extension. You can also use Automation Studio to create and refresh the data extension, or you can use an SMS list created in MobileConnect. After a data extension entry source is configured, you can set a schedule to determine when Journey Builder admits contacts from the data extension. The schedule also controls whether the data extension is used one time or reevaluated to admit more contacts. Scheduling options include Run Once, Recurring, and Automation. The Record Count on the Data Extension entry source tile represents the number of records currently present in the data extension. If the number of records in the data extension changes after the journey is scheduled, this count doesn’t equal the number of records evaluated for injection. To view the number of records that were evaluated and entered the Journey in the last 30 days, click **View Event Results**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_note.png) Note Automation is available when the automation built-in Automation Studio modifies the selected data extension. - Use **Run Once** to admit contacts to the journey one time. Contacts are admitted when you activate the journey or on the date and time you specify. - Use **Recurring** to admit contacts as often as you specify. Choose whether to evaluate all records in the data extension each time the schedule recurs,or to evaluate only new records. Evaluating only new records generally results in better performance. - Use **Automation** to admit contacts based on the schedule of the automation in Automation Studio. The automation must contain an import, filter, or query activity that directly modifies the data extension used for entry. Contacts are evaluated for entry according to the automation's schedule. Choose whether to evaluate all records in the data extension each time the schedule recurs or only new records. Evaluating only new records generally results in better performance. Use the Audience entry source to admit MobileConnect lists. Create an Audience entry source to modify the entry filter or schedule for a MobileConnect Audience. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_note.png) Note The subscriber relationship in a data extension is tied to the Subscriber ID or it can be set by you. When the contact enters a journey, the system creates a contact with the Subscriber ID as the Contact Key. - **[Data Extension Entry Source Use Cases](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_de_entry_source_use_cases.htm&release=264.0.0&type=5)** Read about how Northern Trail Outfitters (NTO) used the data extension entry source to hold a raffle, sell winter accessories, and support disaster relief. - **[Selecting a Data Extension for Entry](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_select_data_extension_for_entry.htm&release=264.0.0&type=5)** Consider these recommendations when you select a sendable data extension as an entry source. - **[Configure the Data Extension Entry Source](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_configure_the_data_extension_entry_source.htm&release=264.0.0&type=5)** To admit Marketing Cloud Engagement contacts from a sendable data extension in Journey Builder, use the data extension entry source. - **[Schedule a Data Extension Entry Source](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_schedule_a_data_extension_entry_source.htm&release=264.0.0&type=5)** To define how often Marketing Cloud Engagement Journey Builder admits contacts from a data extension entry source, set a schedule. You can schedule how often you want to check the data extension for updates, from hourly to yearly. You can also select how long you want the entry source schedule to run for some entry events. After you configure a data extension entry source, a schedule tile appears. - **[Choose How to Process Entry Source Data](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_manage_audience_data.htm&release=264.0.0&type=5)** Configure your Journey Builder entry source so that it promotes efficient processing. When an entry source includes a repeating schedule, choosing a processing option is necessary. Processing options tell Journey Builder how to evaluate contacts in a data extension or list. - **[Configure the Data Extension Entry Source with Data 360](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_configure_data_extension_entry_source_with_cdp.htm&release=264.0.0&type=5)** For new Journeys, use Data Extensions in the new activation folders. #### See Also - [Configure a Path Optimizer Test Activity](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_path_optimizer_test_activity.htm&release=264.0.0&type=5 "Follow these steps to configure the Path Optimizer Test activity in Journey Builder.")