Branch a research question by source context — what should the operator record?
One question can produce useful but incompatible tables across source contexts. A video response and a discussion response may carry different identifiers, timestamp precision and coverage notes. Branch the local query ledger before combining records so the merge does not erase where each returned item actually came from.
Keep platform-specific question branches separate until their scopes and coverage are reconciled.
Use query_branch video and query_branch discussion beneath one brief reference; attach the actual question sent for each authorized response. A branch reference can share a brief_key while retaining its own exact_text; this preserves common purpose without falsely asserting the same request was sent.
Publish a combined view only with branch identifiers intact and a note that branch row counts are returned records, not platform population estimates. Before unioning, check that native identifier strings include source context and object type so unrelated rows cannot collide on a bare numeric-looking key.Create branch labels
Use query_branch video and query_branch discussion beneath one brief reference; attach the actual question sent for each authorized response. A branch reference can share a brief_key while retaining its own exact_text; this preserves common purpose without falsely asserting the same request was sent.
Record source constraints
Write which context each branch requested and preserve any narrower returned coverage rather than describing the two branches as equally complete. If a branch returns only titles while another includes excerpts, record that difference in the branch manifest instead of borrowing missing text across records.
Map shared columns
Build a union schema using source_context, native_key and returned_at, while keeping context-specific columns outside the shared identity field. Use a column such as content_kind to keep a discussion thread distinct from a video, even when both mention the same product name.
Review branch differences
Check whether a missing field means not applicable, not returned or failed. Never populate discussion metrics from an unrelated video record. A null duration for a discussion row can be not-applicable, whereas a missing publication time may mean unknown; these states need different handling.
Authorize the union
Publish a combined view only with branch identifiers intact and a note that branch row counts are returned records, not platform population estimates. Before unioning, check that native identifier strings include source context and object type so unrelated rows cannot collide on a bare numeric-looking key.
Keep the boundaries clear.
- Keep platform-specific question branches separate until their scopes and coverage are reconciled.
- Operational record: Create branch labels. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.