Granted Claim 19 · Software element C
Instructions matching notifications for relevance by a matching engine
Partial — integration dependent
Granted claim language
Verbatim · US12039568B2 · Claim 19wherein the notifications sent to the secondary user device 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; and further wherein:
Claim requirement
Technical interpretation — not claim languageThe limitation requires instructions constituting, or invoking, a matching engine which analyses the previously collected data and selects a notification relevant to that particular user. Two software properties must be present: an analysis operation over the prior data, and a selection operation whose output is the notification subsequently sent.
Publicly disclosed Woosmap functionality
Woosmap documents integration instructions that transmit SDK-derived context into customer-engagement platforms. The Salesforce Marketing Cloud integration documents transmission of events from four context types — Geofences, POI, Visits and ZOI — to trigger an Entry Event, with connector initialisation using event definition keys such as woos_geofence_entered_event, woos_POI_event, woos_Visit_event and woos_zoi_classified_entered_event, and event data fields including user_properties.[field_name]. Comparable custom-event transmission is documented for Braze and for Batch, where events are expressly usable as Custom Event triggers in the Automation and Journey composers.
- Named event definition keys
- Contact key association
- user_properties.[field_name] transmitted with events
- Entry Event triggering in Marketing Cloud
- Custom-event triggers in Braze and Batch
Granted claim architecture
- 01Previously collected data
- 02Matching engine
- 03Relevance determination
- 04Selected notification
Publicly documented Woosmap pathway
- 01Visits / ZOI / user context
- 02Event + user properties
- 03Customer-engagement platform
- 04Journey / communication logic
Execution environment and component attribution
- Woosmap SDK
Connector instructions within the SDK are documented as emitting the events and associated properties.
- Customer-engagement platform
Event ingestion and journey entry are documented platform-side operations.
- NOT ESTABLISHED FROM PUBLIC EVIDENCE
No public material establishes instructions performing the complete claimed matching operation over previously collected data.
Public evidence
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 (developers.woosmap.com)
Woosmap Geofencing SDK — Braze integration
Transmission of Woosmap Geofencing SDK events from Geofences, POI, Visits and ZOI contexts to Braze as custom events with associated properties, tied back to push messaging campaigns.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Batch integration
Transmission of Woosmap Geofencing SDK events from Geofences, POI, Visits and ZOI contexts to Batch as custom events, expressly usable as a Custom Event trigger in the Automation and Journey composers.
View original source ↗Technical correspondence
Public documentation establishes a software pathway by which Woosmap-derived user and location context can be transmitted into software capable of determining subsequent customer-engagement actions. The complete claimed matching operation remains integration and deployment dependent. Salesforce Marketing Cloud, Braze and Batch are not characterised here as the claimed matching engine; the public record establishes the transport of context, not the selection logic applied to it.
Evidentiary status and matters for further review
Claim-element correspondence
Integration evidence required
Matters for further review
In a given deployment, which software component analyses previously collected data regarding the particular user, and does its output determine which notification is sent?