Campaign pairs (per-post rows)

One row per video pair — a creator's post, or the 1–3 cross-posted videos that share a single payout — for the given cycles. This is the layer underneath GET /campaign/summary and GET /campaign/tags: per-pair totalSpend and views sum to the campaign figures those endpoints report for the same cycles. Each row carries the creator, the pair's tag ids, its money (basePay + cpmBonus = totalSpend), and a videos array with the platform, post URL, posted-at, and engagement of every video in the pair.

Engagement comes from the latest snapshot inside the cycle window — the same rows the campaign totals count. A video with no in-cycle snapshot has snapshotDate: null and zeroed metrics, and is not counted by any campaign endpoint; countedVideos is how many of the pair's videos did count.

tagIds filters which pairs come back (pair tags carry the money); each returned pair still reports all of its own videos.

groupIds filters by the pair's creator instead — the creator groups from GET /groups. Filters compose as an AND (groupIds plus tagIds means both), while ids within one filter are ANY. Every row also carries creator.groupIds, so one unfiltered pass can be bucketed by group client-side.

Results are ordered by (updatedAt, pairId) ascending and paged with the opaque nextCursor. Pass updatedSince with the largest updatedAt you have already stored to pull only what changed since — updatedAt moves whenever the pair is re-paired, re-assigned, or its payout is recalculated (which is what a view refresh triggers).