Customer.io adds polygon geofences to its stable iOS SDK

Customer.io moves beyond circular venue boundaries

Customer.io's stable iOS SDK 4.9.0 changelog, dated September 25, says geofences drawn as polygons are now supported. Entry and exit events can follow the exact drawn shape of a venue rather than a surrounding circle. Customer.io says existing circular geofences continue to behave as before, no code changes are required for them and cached definitions from earlier versions keep working after upgrade.

The operator value is straightforward. Campuses, shopping areas, event venues and service zones are rarely perfect circles. A more faithful boundary can reduce events generated in irrelevant neighboring space. It also creates a more specific production definition that Marketing Operations, mobile engineering and privacy owners need to version and test together.

Sources: Customer.io iOS SDK changelog

Geometry precision is not business precision

A polygon can describe a venue more accurately while the event still remains uncertain. Location permission, device settings, coordinate quality, operating-system behavior, movement near an edge and offline delivery all influence when an entry or exit appears. The business should treat the signal as an observation under known conditions, not proof of a customer's intent.

Write the eligible use case before drawing the shape. A venue-entry event may be appropriate for a service reminder or an on-site information journey. It should not silently become evidence of purchase, account health or customer consent. Derived commercial claims need their own authoritative events.

Version the polygon like an event schema

Store a stable geofence ID, geometry version, coordinate reference, deployment time, SDK version and accountable owner. Every entry or exit should carry its own event ID, observed-at time and received-at time. When the venue shape changes, keep the prior definition so an operator can determine which boundary evaluated a historical event.

Do not overwrite entry and exit into one current flag if downstream timing matters. Preserve both observations and their ordering. A delayed entry that arrives after an exit can otherwise make a journey appear current when the device has already left. Define whether eligibility uses observed time, received time or a bounded combination.

Compatibility needs a mixed-version test

Customer.io says circular geofences behave as before and earlier cached geofences keep working after the upgrade. That is helpful continuity, but a real mobile population rarely upgrades at once. Operators should test devices on the earlier and new SDK behavior, confirm how the workspace distributes definitions and decide how long mixed geometry can remain active.

Use named test devices and controlled paths: enter one edge, move along the boundary, exit through another edge, disable and restore location, go offline, reconnect and repeat after a definition change. Record the event IDs and device conditions. The purpose is to understand operational behavior, not to infer a universal accuracy rate from a small test.

Recheck consent and current eligibility before action

Location permission on the device does not automatically authorize every downstream marketing use. Keep the legal and preference basis for the intended channel explicit. At decision time, check current subscription, suppression, account relationship and campaign eligibility rather than assuming the state captured when the geofence was configured is still valid.

A location event can arrive after a customer unsubscribes, changes region, loses an entitlement or closes an account. High-impact journeys should evaluate those current facts immediately before communication. Preserve the eligibility decision and version so a reviewer can distinguish a valid trigger from a later-invalid action.

Monitor entry and exit as an operating pair

Track event volume, unique devices, entry-to-exit balance, repeat events near boundaries, delayed arrivals and journey enrollments by geometry and SDK version. Sudden changes can indicate a boundary deployment issue, mobile release mix or source outage. These are internal control measures; the vendor changelog does not publish a benchmark for expected rates.

Set a pause rule before launch. Unexpected event growth, missing exits, a spike in duplicates, stale geometry or an eligibility-system failure should stop new customer actions while evidence is reviewed. Keep the event stream even when messaging pauses so the team can separate trigger health from journey execution.

A safe rollout starts with reconstruction

Choose one venue, one bounded audience and one low-risk journey. For a sample of events, reconstruct the polygon version, device and SDK context, observed and received times, customer identity, current preference, journey decision and message disposition. Include events that correctly did not produce a message.

Expand only when another operator can follow that chain without using a screenshot or a mutable email address as the key. Customer.io's polygon support improves the trigger surface. RevOps turns that capability into trustworthy lifecycle operations by governing geometry, clocks, eligibility, monitoring and recovery as one release.

Document the handoff between mobile engineering and lifecycle operations. Engineering owns SDK rollout and device-level diagnostics; the lifecycle owner owns eligibility, channel use and customer action. Both should use the same geofence version and event IDs so a boundary defect does not become an unexplained campaign exception.