We're migrating from Fivetran's legacy StackAdapt (REST) connector to the stackadapt-graphql connector. The REST connector gave us us_state_options on the campaign object; the GraphQL connector has no geographic field at all (note campaign.state is lifecycle — PAUSED/DRAFT/ENDED — not geography). We report media spend by state for PA/NY/NJ, so this is blocking as we resume spend.

We've had exactly the data we need from you before, via manual export from StackAdapt reporting:

Date Campaign ID State Spend Impressions
2024-01-11 576731 NY $291.05 21,984
2024-01-11 576731 PA $509.19 40,553
We reviewed the full connector schema. The only geographic field anywhere is city, on insight_campaign_city and insight_campaign_group_city — no region, state, country or DMA on any table. Those two tables also appear to have no date/time column (no granularity_time equivalent, unlike campaign_delivery), so even city data looks like a lifetime rollup rather than a daily series.

Questions:

-Can your reporting/insights API return campaign delivery by US state?
-If state isn't available but city is, does the city response include a parent region/state field?
-Does the GraphQL API expose campaign geo targeting — the REST us_state_options equivalent — as a fallback?
-Any date-range or retention limits on geo reporting? We'd want to backfill from 2023-12-21.