Granted Claim 10 · Method step C
Matching notifications to the user according to analysis of previously collected data
Partial to strong — integration / deployment dependent
Granted claim language
Verbatim · US12039568B2 · Claim 10wherein the notifications sent to the secondary user devices are matched, by a matching engine, to the user of the secondary user device according to analysis of the previously collected data regarding the user of the secondary user device such that the notifications sent to the secondary user device are relevant to the user of the secondary user device;
Claim requirement
Technical interpretation · not claim languageThe claim requires a matching engine that analyses the previously collected data and selects, for the individual user, a notification that is relevant to that user. Three requirements are cumulative: an analysis operation over the stored data, a matching operation performed by an identifiable engine, and a relevance outcome attaching to the notification actually sent.
Publicly disclosed Woosmap functionality
Woosmap documents the derivation of Zones of Interest from recurrent locations and from geographical and temporal patterns in stored visit data, and publishes consumer examples in which that contextual information determines a subsequent action: suggesting an order as a user commutes back home, notifying a user to place a click & collect order when leaving the office for lunch, and notifying a user to book a ride when leaving the office. These are published examples of historical and recurrent-location information being used to determine context for a notification.
- Zones of Interest from recurrent locations
- Geographical patterns
- Temporal patterns
- Historical visits
- Published contextual notification examples
- Home / office inference from cluster time distribution
Claimed matching operation
- 01Previous user data
- 02Analysis
- 03Matching
- 04Relevant notification
Customer-engagement integration layer
Woosmap publicly documents an integration with Salesforce Marketing Cloud. The official developer documentation states that Woosmap Geofencing SDK events can be sent to Salesforce Marketing Cloud from four context types — Geofences, POI, Visits and ZOI — to trigger an Entry Event, and the documented event data specification includes a user_properties.[field_name] field.
- Geofence events
- POI events
- Visit events
- Zone of Interest events
- user_properties.[field_name]
- Entry Event into a customer journey
Evidentiary limitation
The publicly documented integration demonstrates a technical pathway by which Woosmap location and behavioural events, together with user-property data, can enter a customer-engagement environment capable of determining subsequent communication actions. Whether a particular deployment performs the complete claimed matching operation requires deployment-level analysis. Salesforce Marketing Cloud is not, on this evidence, established as the claimed matching engine.
Documented integration pathway
- 01Woosmap location / visit / ZOI event
- 02User properties
- 03Salesforce Marketing Cloud
- 04Entry event / customer journey
- 05Targeted communication
Attribution of the claimed method step
Only where the public evidence permitsWoosmap Geofencing SDK
Publicly documentedDocumented as producing the contextual and behavioural signals (visits, ZOI, recurrence) on which relevance may be assessed.
Customer-engagement platform
Publicly documentedWoosmap documents transmission of location, visit and ZOI events with associated properties into Salesforce Marketing Cloud, Braze and Batch, where journey and automation logic determines subsequent communication.
The claimed matching engine
Not establishedNo public Woosmap document identifies a component performing the complete claimed matching operation. The performing component is deployment-specific and is not established by the public record.
Public evidence
Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Visits and Zone of Interest
Detection of when and where a user has spent time (visits) without explicit monitoring; assessment of time spent on each visit; definition of Zones of Interest as places where a user recurrently spends time; and the express statement that, when the Zones of Interest feature is activated, the SDK stores and clusters historical location data on the device for each user, identifying approximate home and office locations from the time distribution of clusters. Also publishes consumer context examples including commuting home and leaving the office for a click & collect order.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Salesforce Marketing Cloud integration
Transmission of Woosmap Geofencing SDK events to Salesforce Marketing Cloud from four context types — Geofences, POI, Visits and ZOI — to trigger an Entry Event; connector initialisation with EventDefinitionKeys for woos_geofence_entered_event, woos_geofence_exited_event, woos_POI_event, woos_Visit_event, woos_zoi_classified_entered_event and woos_zoi_classified_exited_event; and event data fields including user_properties.[field_name].
View original source ↗Woosmap (woosmap.com)
Woosmap Geofencing — commercial use case page
Commercial description of geofencing triggering events on device entry or exit of a monitored region; contextualisation of push notifications at the right time and in the right place; support for distance-based, time-based, ETA/isochrone and recurrent geofences; and retail, geomarketing and offer-targeting use cases including tailoring by where users live or work.
View original source ↗Technical correspondence
The public record establishes both halves of a plausible matching pathway: behavioural data derived from previously collected location information, and a documented mechanism for delivering that data, with user properties attached, into a platform whose function is to determine which communication a given contact receives. The claim's requirement is nevertheless specific — matching by a matching engine according to analysis of the previously collected data — and the public documentation does not identify the analysis actually applied in any given implementation.
Evidence of United States performance
Matters for further reviewIs there public evidence that a United States deployment analyses Woosmap-derived historical data to select the notification sent to an individual consumer?
United States deployment evidence
Technical correspondence
Evidentiary limitation
The documented integration is a pathway, not an established matching engine.