Granted Claim 10 · Method step E
Sending notifications according to retailer specifications regarding consumer demographics
Partial — integration dependent
Granted claim language
Verbatim · US12039568B2 · Claim 10send 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 method requires retailer-entered specifications concerning consumer demographics, and requires the sending operation to be governed by those specifications. Two things must be established: the existence of a configuration surface by which the retailer expresses preferred recipient characteristics, and the use of that configuration to condition sending.
Publicly disclosed Woosmap functionality
Woosmap's own documentation addresses location context rather than demographic segmentation, but its integration documentation establishes a transport mechanism for user-associated attributes. The Salesforce Marketing Cloud event data specification includes a user_properties.[field_name] field, alongside a contactKey uniquely identifying the subscriber or contact, and the events are documented as triggering an Entry Event within Marketing Cloud. Braze and Batch integrations are documented as receiving Woosmap events as custom events with associated properties.
- Event properties transmitted with location events
- user_properties.[field_name]
- contactKey identifying the subscriber / contact
- Entry Event capability in Marketing Cloud
- Custom events with properties in Braze and Batch
Documented property transport
- 01Woosmap event
- 02Event properties + user properties
- 03Contact key
- 04Customer-engagement platform
- 05Audience / journey selection
Attribution of the claimed method step
Only where the public evidence permitsWoosmap Geofencing SDK
Publicly documentedDocumented as assembling and transmitting the event payload, including user properties, to the engagement platform.
Customer-engagement platform
Publicly documentedDocumented as receiving the events and contact identifiers and hosting the journey / audience logic.
Retailer demographic configuration surface
Not establishedNo public Woosmap document identifies the retailer-entered demographic specifications contemplated by the claim.
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 (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 documented integration establishes a mechanism for transmitting user-associated properties alongside Woosmap location events into a customer-engagement platform. Public evidence of the exact retailer-entered demographic specifications used in a particular implementation remains required. The position is materially stronger than an absence of evidence: the transport layer and the recipient-selection environment are both publicly documented, and the open question is confined to the configuration applied within them.
Publicly established
- — Woosmap location events
- — User-associated event properties
- — Marketing Cloud integration
- — Entry-event capability
Not yet established
- — Exact retailer demographic criteria
- — Exact consumer-segment definition
- — Exact preferred-recipient configuration
Evidence of United States performance
Matters for further reviewIs there public evidence of retailer-entered demographic or segment specifications governing Woosmap-triggered communications in a United States deployment?
United States deployment evidence
Technical correspondence