2026 Redistricting¶
Some states have adopted new electoral districts — the maps that take effect with the term beginning January 1, 2027, after the November 2026 election. Until then, ActionKit knows both each affected user’s current district and their new electoral district, so you can start targeting the new maps now.
How the data is stored¶
For users with zip-or-better precision in an affected state, the future
district is written to core_usergeofield under one of these names:
us_district_redistrict2026— future US Congressional districtus_state_district_redistrict2026— future state house districtus_state_senate_redistrict2026— future state senate district
The user’s current district remains in core_location and is
returned by the normal location lookups until the cutover.
After January 1, 2027 the new maps move into core_location and the
*_redistrict2026 fields are removed after a grace period.
States with 2026 data loaded¶
State |
US Congress |
State House |
State Senate |
|---|---|---|---|
CA |
Loaded (AB604) |
||
FL |
Loaded (EOGPCRP2026) |
||
MI |
Already loaded in 2024 (Motown Sound FC E1, unchanged for 2026) |
Loaded (Crane A1) |
|
MO |
Loaded (HB1) |
||
NC |
Loaded (CCM-2) |
||
OH |
Loaded (Adopted 2025-10-31) |
||
TN |
Loaded (SB 7004) |
||
TX |
Loaded (Plan C2333) |
||
UT |
Loaded (2026 court-ordered) |
||
WI |
Already loaded in 2024 (2024 court-ordered maps, unchanged for 2026) |
Already loaded in 2024 (2024 court-ordered maps, unchanged for 2026) |
If your state isn’t in the list yet and you expect new maps for 2026, file a support request and we’ll prioritize loading it.
Targeting future districts in the query builder¶
The US Legislative District filter on the Users, Actions, Donations, Mailings, and Texting query builders has a checkbox labeled Use electoral districts (2026). When checked, the filter uses each user’s new electoral district where there is one, and their current district everywhere else. This works the same way for the U.S. House, State Senate, and State House variations.
The checkbox appears while the new districts are pending and for about three months after they take effect, so you can target them throughout the transition; then it disappears on its own. Hover the label to see which states’ new maps it covers.
Targeting future districts in the mailer¶
The mailing Target screen (and automation enrollment targeting) has the same option. When you add Congressional Districts or State House/Senate to an include or exclude set, a checkbox labeled Use electoral districts (2026) appears beneath the district fields. When checked, the districts you enter are matched against each user’s new electoral district where there is one, and their current district everywhere else. Hover the label to see which states’ new maps it covers.
As in the query builder, the checkbox disappears on its own about three months after the new districts take effect; saved targeting that still has it checked simply goes back to matching current districts.
Targeting future districts in raw SQL¶
If you need a query the query builder can’t express, you can read
core_usergeofield directly:
SELECT user_id FROM core_usergeofield
WHERE name = 'us_district_redistrict2026'
AND value IN ('MO_02', 'MO_03');
To show the future district inside a mailing or other template context, use:
{{ user.geofield.us_district_redistrict2026 }}
After the cutover, rewrite any reports or mailing targeting that
references *_redistrict2026 fields to use the standard
core_location columns (us_district, us_state_district,
us_state_senate); the geofield rows will be cleaned up after a
grace period.