Repository navigation
v1.3.1 — Fix broken AC sync, add registration backfill
v1.3.1 — Fixes a broken Sync Attendees, and makes it do what it was supposed to
Fixed: Sync Attendees was pulling the wrong contacts
The check-in sync used an incorrect ActiveCampaign API parameter (filters[tagid]) that AC silently ignored — instead of filtering to contacts holding the check-in tag, it was returning a large, effectively unfiltered slice of the account's contacts. This could mark attendees as checked-in who were never actually tagged in AC. Fixed to use AC's documented tagid parameter, verified against AC's API docs and an end-to-end mocked test before release.
If you ran Sync Attendees on v1.3.0, some attendees may show an incorrect "Checked In" status. Re-running Sync now that this is fixed will correct it automatically, as long as none of those attendees were legitimately checked in (via QR scan or manual Check In) before you ran the old, broken sync — if some were, check those individually rather than re-running sync blindly.
Sync Attendees now also backfills missing registrations
Previously Sync only reconciled check-in status for attendees that already existed locally. Now it also pulls contacts by the event's registration tag and creates any missing local attendee record for them first (matched by email — never overwrites or duplicates existing records), before reconciling check-in status. This closes the gap on sites whose local attendee data has fallen behind ActiveCampaign — e.g. a staging site that's a snapshot of production, while real registrations keep landing in AC via the live site.
Upgrade notes
No database changes. If you use Sync Attendees, re-run it once after updating to correct any bad data from the v1.3.0 bug.