You are here:
Queries in Clean Rooms
Run queries in a clean room to compare your data with a collaborator's data and gain insights, without exposing raw records.
Required Editions
| Available in: Enterprise Editions |
Query results vary based on the use case of the collaboration.
How Queries Work in a Collaboration
A collaboration is based on a use case. When a use case includes more than one query, every query in the use case is available in the collaboration, and you select which query to run. A query compares a consumer segment with the provider's data and returns a result that meets the privacy rules that the template defines.
Run a query in two ways.
- Manual run
- Run the query ad hoc and get a result for the segment that you select.
- Scheduled run based on segment publish
- Schedule the query to run each time its consumer segment publishes. The query follows the segment's existing publish schedule, so the result refreshes on the same cadence as the segment.
To schedule a query on segment publish, the consumer segment needs a publish schedule. If the segment doesn't have a publish schedule, an associated query runs ad hoc only.
When a use case includes more than one query, schedule each query to run on the segment publish schedule. The queries share the same publish trigger but produce separate results. Data 360 prevents a duplicate schedule for the same combination of query, segment, and parameter values, so you can't create the same schedule twice.
Scheduling a query doesn't remove the ad hoc option. Run a scheduled query manually on demand — a manual run doesn't change the schedule.
A marketing team (consumer) collaborates with a publisher (provider) on a use case that includes two queries: an audience overlap query and a reach summary query. Because the use case has multiple queries, both are available in the collaboration, and the team chooses which one to run.
The team schedules the overlap query to run on segment publish for their Loyalty Members segment, which publishes every week. Each time the segment publishes, the query reruns automatically, so the team always has a current overlap count without running the query by hand.
Midweek, the team starts a promotion and needs current numbers before the next scheduled run. They run the overlap query for the same segment. The manual run returns an immediate result and doesn't change the weekly schedule. Later, they run the reach summary query to check the performance of the promotion.
Next Steps
Continue with these related tasks.
- To run a query now or schedule one, see Collaborate in a Clean Room.
- To stop a run that's in progress, see Cancel a Query Run.
- To find query output and reports, see View Clean Room Query Results.
- To review or delete your scheduled queries, see Manage Scheduled Queries.
