How can I set up a recurring campaign (e.g., weekly) for users imported via CSV, using a single journey for aggregated stats?

To send recurring messages to a segment you refresh regularly (for example a weekly CSV import) while keeping a single Customer Journey for continuous operation and aggregated statistics, use a 'control tag' pattern:

1. Create a control tag:

   • Go to the Tags section of the Control Panel and create a tag dedicated to gating entry into this campaign. A Boolean tag is recommended (e.g. is_weekly_target); an Integer tag also works.

2. Prepare the CSV and update the tag values:

   • The first column must be named HWID and contain hardware IDs of the target devices; other columns must be named exactly as the tags in your account. Only tags that already exist can be updated via CSV.
   • Add a column for your control tag and set it to true (Boolean) or 1 (Integer) for every user who should receive the campaign in this cycle.
   • Go to Import CSV → Update Tag values, select the project, press Upload CSV, choose the columns to import and press Start import.
   • Rows whose HWID is not registered for the selected project are skipped — the import report shows processed and skipped counts.

3. Configure the journey:

   • Start the journey with an Audience-based entry element and pick (or create) the segment in Audience Source.
   • Add a filter condition on your control tag: is true (Boolean) or is 1 (Integer).
   • In the same element open Entry schedule, choose Recurring entry and set the cadence — Periodically (e.g. weekly on a given day and time) or On specific dates.
   • Add the message element(s) you need (Push, Email, In-app, SMS, …).
   • Important: after the message element(s) add an Update user profile flow control and configure it to set the control tag back to false (or 0).

4. Launch the journey.

How it works: on every scheduled run only users whose control tag is true (or 1) enter. After the message is sent, Update user profile resets the tag, so those users will not re-enter on the next run unless a later import sets the tag again. Each import cycle therefore delivers the message once, while a single long-running journey keeps all statistics aggregated in one place.