Where this fits
Atlasemoji Geofencing is designed around operational programs, not just individual circles on a map. A program answers five connected questions: what job are we doing, where does it apply, who or what are we evaluating, what spatial or business condition matters, and what should happen when that condition is met.
Zones define WHERE a program operates. Atlas Locations is the canonical place layer for stores, distribution centers, warehouses, yards, docks, terminals, campuses, jobsites, event venues, service territories, and other real-world operating locations. A Location is not the same thing as a geofence: the Location describes the place, while reusable point-radius or polygon geometry defines the spatial test around or within that place. A retailer with 300 stores can load or connect one 300-row location list instead of manually building 300 separate geofence forms.
Subjects define WHO or WHAT is evaluated against those zones. A Retail Loyalty program may use CRM customers or loyalty members with consented mobile positions. A Fleet or Shipment program may use shipment, vehicle, or carrier telemetry from an integration workflow. Yard and distribution programs may evaluate trailers, vehicles, or assets. Warehouse programs may combine inventory, item identity, and telemetry. Field Operations can combine jobsites with employees, contractors, mobile participants, or other operational records.
Zones and Subjects each have their own data source. Teams can use existing Atlas master tables, import CSV or spreadsheet data, or connect sources such as Google Sheets, Airtable, APIs, webhooks, SFTP, CRM, ERP, or other DataSynch connectors. Imported records can be normalized into Atlas Locations, CRM, Items, Inventory, or Telemetry when teams want a durable place to inspect records, review exceptions, map data, and reuse it across workflows.
Rules & Actions combine the spatial event with business context. A rule can say WHEN a loyalty member enters a participating store, AT an eligible location, FOR an opted-in customer, IF campaign conditions are satisfied, THEN create a geofence event and dispatch the appropriate notification or connected workflow. The same structure can support truck arrival, yard dwell, wrong-site exceptions, asset movement, field check-in, service coverage, and other location-aware operations.