Granted Claim 19 · Software element E
Instructions applying retailer-entered specifications regarding consumer demographics
Partial — deployment dependent
Granted claim language
Verbatim · US12039568B2 · Claim 19send notifications to the one or more secondary user devices according to one or more specifications entered by the retailer regarding one or more demographics of the one or more consumers to which one or more notifications are preferred to be sent, wherein the one or more notifications are sent:
Claim requirement
Technical interpretation — not claim languageThe limitation requires instructions that condition the sending operation on retailer-entered specifications concerning consumer demographics. Two software properties are required: an input mechanism by which the retailer enters those specifications, and evaluation of them at or before the point of sending.
Publicly disclosed Woosmap functionality
Woosmap documents an event payload carrying user-associated properties into customer-engagement platforms. The Marketing Cloud integration documents contact-key association and event data fields including user_properties.[field_name]; Braze and Batch integrations document custom events with associated properties. Audience, segmentation and journey configuration reside in the engagement platform and in the retailer's own application configuration.
- Woosmap event properties
- user_properties.[field_name]
- Contact key association
- Retailer application configuration
- Platform segmentation and journey inputs
Publicly documented targeting pathway
- 01Retailer / customer data
- 02Woosmap event
- 03User property
- 04Engagement platform
- 05Communication logic
Execution environment and component attribution
- Woosmap SDK
Connector instructions transmit events with user-associated properties.
- Customer-engagement platform
Audience, segmentation and journey logic are documented platform capabilities.
- Retailer application
Which property values are populated is determined by the retailer's own integration code.
- NOT ESTABLISHED FROM PUBLIC EVIDENCE
No public material establishes retailer-entered demographic specifications of the kind recited.
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 ↗Technical correspondence
A software pathway exists by which retailer-controlled, user-associated attributes travel alongside location events into systems that decide what is communicated. The distinction to preserve is between the documented transport mechanism and the claimed demographic specification: the former is publicly established, the latter is not.
Evidentiary status and matters for further review
Claim-element correspondence
Deployment confirmation required
Matters for further review
What specifications does a retailer actually enter in a relevant United States deployment, and are they demographic specifications governing which consumers are preferred to receive notifications?
Publicly established / requires deployment evidence
Publicly established: a software pathway for events and user-associated properties. Requires deployment evidence: the exact retailer-entered demographic criteria required by the granted claim.