On this page: Learn how to use the Incremental query targeting activity to return only new records on each Orchestrated campaign run, excluding profiles already targeted in previous executions.
The Incremental query activity is a Targeting activity that runs a database query each time the Orchestrated campaign runs. The important part is that each run only outputs records whose date field value is later than the date of the previous execution. This way, you avoid re-targeting the same people or re-exporting the same rows.
Use it when the campaign can run multiple times, or example, when you schedule the campaign, e.g. weekly or when it is triggered by an external signal or API. Each run targets only records dated after the previous execution, so you avoid duplicates.
Typical uses:
- Messaging and audiences: Pull only new sign-ups, new purchasers, or other “new since last run” segments into the next step (e.g. email, mobile message).
- Ongoing exports: Send only new or updated rows to files for reporting or BI tools, without duplicating what you already exported.
Configure the Incremental query activity incremental-query-configuration
Set the targeting dimension, build your query, and choose how the activity decides which records to exclude from future runs.
-
Drop an Incremental query activity into your Orchestrated campaign.
-
In Audience, pick the Targeting dimension, e.g. recipients, subscribers, and click Continue. Learn more on Targeting dimensions.
-
Click Add condition to define the query. Learn how to use the rule builder.
-
Under Processed data, choose your Path to the date field. A date field is required, and the attribute must use the Date Time format. Each run returns only rows whose date is after the last execution.
note NOTE Eligibility depends only on the value of the date field, not on when the record was ingested. A record ingested after the previous execution is not returned if its date field value is older than the date of that execution.
Check the last execution date incremental-query-last-execution
Once the activity has run, the Last execution date field is displayed under Processed data, below the Path to the date field. It shows the date and time of the previous execution of the activity. This is the cutoff date used by the next run. This field is read-only.
Example incremental-query-example
The following example sends a welcome email to profiles who have just become gold members. The campaign can be scheduled to run weekly, every Monday. Each run targets only profiles that qualified for gold membership since the previous run, so each recipient receives the welcome email once.
- Incremental query: Selects gold members. First run: all current gold members. Later runs: only profiles that became gold members since the previous execution.
- Email delivery: Sends the welcome email to the profiles output by the query.
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to configure the Incremental query targeting activity in an Orchestrated campaign so that each run returns only records whose date field value is later than the previous execution.
Intents:
- Understand what the Incremental query activity does across repeated Orchestrated campaign runs.
- Configure the activity’s targeting dimension and query condition.
- Choose a date field under Processed data so that each run returns only rows dated after the last execution.
- Understand what happens to downstream activities when a run returns no rows.
- Build a “new since last run” audience for messaging or ongoing exports.
Glossary:
- Incremental query: a Targeting activity that runs a database query each time the Orchestrated campaign runs and outputs only records whose date field value is later than the previous execution (product-specific)
- Processed data: the configuration area where you choose how the activity excludes records from earlier runs, for example by using a date field (product-specific)
- Path to the date field: the attribute, in Date Time format, used under Processed data so each run returns only rows whose date is after the last execution (product-specific)
- Last execution date: the field displayed under Processed data, below the Path to the date field, once the activity has run; it shows the date and time of the previous execution and is the cutoff date used by the next run; the field is read-only (product-specific)
- Targeting dimension: the audience type selected for the activity, for example recipients or subscribers (product-specific)
Guardrails:
- When a run returns no rows, the Orchestrated campaign stops at the Incremental query; activities after it are not executed until there is data, when the campaign runs again.
- A date field is required under Processed data, and the attribute must use the Date Time format.
- Each run returns only rows whose date is after the last execution.
- Eligibility depends only on the value of the date field, not on when the record was ingested. A record ingested after the previous execution is not returned if its date field value is older than the date of that execution.
Terminology:
- Canonical name: Incremental query — variants: none
- Synonyms: none
- Do not confuse: “Incremental query” (a Targeting activity that excludes previously returned records) ≠ “Targeting dimension” (the audience type, e.g. recipients or subscribers, selected within the activity)
FAQ:
- Q: What does the Incremental query activity return on each run? — Only records whose date field value is later than the previous execution, regardless of when they were ingested.
- Q: When should I use the Incremental query activity? — When the campaign can run multiple times, for example when scheduled (e.g. weekly) or triggered by an external signal or API, so each run targets only records dated after the previous execution.
- Q: What is required under Processed data? — A Path to the date field, using the Date Time format; each run returns only rows whose date is after the last execution.
- Q: What happens if a run returns no rows? — The Orchestrated campaign stops at the Incremental query, and activities after it are not executed until there is data on a later run.
- Q: What are typical uses of the Incremental query? — Pulling “new since last run” segments (e.g. new sign-ups, new purchasers) into messaging, or sending only new or updated rows to files for reporting or BI tools.
Examples:
- Welcome email to new gold members: an Incremental query selects gold members (first run: all current gold members; later runs: only profiles that became gold members since the previous execution), followed by an Email delivery activity that sends the welcome email to the profiles output by the query. The campaign can be scheduled to run weekly, every Monday, so each recipient receives the welcome email once.
Related pages:
- To pick the audience type for the Incremental query: Targeting dimensions (orchestrated/target-dimension.md)
- To build the query condition for the Incremental query: Learn how to use the rule builder (orchestrated/orchestrated-rule-builder.md)
Personas:
- marketer: Can configure the Incremental query activity so each Orchestrated campaign run returns only records whose date field value is later than the previous execution. Can select the Targeting dimension, add a condition with the rule builder, and choose the Path to the date field under Processed data. The page states that a date field is required and the attribute must use the Date Time format. Where: “Configure the Incremental query activity”.
Onboarding:
- Level: Intermediate
- First minimal step: Drop an Incremental query activity into your Orchestrated campaign.
- Success check: Each run returns only rows whose date is after the last execution.
- Next: Selecting the Targeting dimension for the Incremental query activity: Create your Targeting dimension (orchestrated/target-dimension.md); Adding a condition to define the query in the Incremental query activity: Work with the rule builder (orchestrated/orchestrated-rule-builder.md)