Granted United States Patent · US12039568B2

United States Deployment Analysis

Purpose of United States Deployment Analysis

This analysis examines publicly disclosed Woosmap deployments and integration architectures for evidence of combined functionality corresponding with the limitations of the granted claims of US12039568B2.

The independent-claim analysis identifies multiple areas of technical correspondence within Woosmap’s publicly disclosed technology. This section examines whether publicly disclosed customer deployments and integration architectures provide additional evidence concerning the combined operation of those functions.

Particular attention is given to implementations capable of connecting location and historical user context with customer information, targeting logic, temporal conditions and automated consumer communications.

U.S. deployment evidence — not yet established

Integration file — Salesforce

Salesforce Marketing Cloud

Platform

Salesforce Marketing Cloud

Woosmap data / event supplied

  • woos_geofence_entered_event / woos_geofence_exited_event
  • woos_POI_event
  • woos_Visit_event (date, arrivalDate, departureDate, id, latitude, longitude)
  • woos_zoi_classified_entered_event / woos_zoi_classified_exited_event
  • Event properties: id, latitude, longitude, radius, name, idStore, city, zipCode, country_code, address, tags, types, user_properties.[field_name]

Downstream capability

The Woosmap documentation describes configuring an SFMC connector with a contact key and per-event EventDefinitionKey, so that a Woosmap event is passed to Marketing Cloud as an Entry Event.

Relevant granted claim element

Claim 1 elements B, C, F, I

Claim 1 · Claim 10 · Claim 19

Evidentiary status

INTEGRATION CAPABILITYTECHNICAL INTEGRATION AVAILABLE FOR U.S. DEPLOYMENT

The documentation establishes the data path and the identity binding through contactKey. It does not identify any customer using it, and the page does not name the MobilePush module.

Documented data path

  1. 01Woosmap geofence / visit / ZOI event
  2. 02User / event properties
  3. 03Customer-engagement platform
  4. 04Journey / segmentation / automation
  5. 05Consumer communication

This diagram describes a publicly documented technical data path. It is not a statement that any third-party platform, or any customer of any platform, performs or is responsible for any act under the granted patent. Those are matters for patent counsel.