Areas for Further Review
Where public evidence is limited
Every open question is stated explicitly — the review is more useful when its limits are visible.
Are consumer-specific historical information and live geofence status used in the same workflow?
Open- Why it matters
- This combination is central to the patent architecture.
- Current evidence
- Product descriptions of Proximity + Audience imply combined use.
- Missing evidence
- A worked technical example naming both inputs simultaneously.
- Next step
- Request a technical deep-dive session with Foursquare product engineering.
Can end users define their own geographic preferences?
Open- Why it matters
- Relates to elements of the patent covering user-side configuration.
- Current evidence
- Not confirmed in public product material.
- Missing evidence
- Documentation of a user-facing configuration surface.
- Next step
- Clarify with Foursquare product management.
Can users specify notification periods or time conditions?
Open- Why it matters
- Time conditions appear in the patent architecture.
- Current evidence
- Campaign-level timing rules are described.
- Missing evidence
- User-specific time windows.
- Next step
- Request implementation details from a customer deployment.
How does Audience data connect with Proximity activation in practice?
In Progress- Why it matters
- Confirms the end-to-end matching pipeline.
- Current evidence
- Product pages describe combined use.
- Missing evidence
- Reference architecture diagram.
- Next step
- Ask for a reference architecture from Foursquare solutions.
How are messages selected for individual users?
Open- Why it matters
- Selection logic is a central decision element in the patent.
- Current evidence
- General descriptions of relevance and targeting.
- Missing evidence
- Selection algorithm description or worked example.
- Next step
- Discuss with engineering.
Which component enables or disables communication?
Open- Why it matters
- The 'enable/disable' element is discussed in patent context.
- Current evidence
- Not clearly documented publicly.
- Missing evidence
- Component-level responsibility diagram.
- Next step
- Clarify during discussion.
Does campaign activation occur directly or through third-party platforms?
Open- Why it matters
- Affects who performs the 'delivery' element in the patent architecture.
- Current evidence
- Partner integrations are described publicly.
- Missing evidence
- Deployment-specific split of responsibilities.
- Next step
- Request a partner-integration overview.
How are device identifiers managed?
Open- Why it matters
- Identity model affects several patent elements.
- Current evidence
- General privacy statements.
- Missing evidence
- Technical documentation of the identifier lifecycle.
- Next step
- Discuss with privacy engineering.
Do retailer-entered demographic criteria control message delivery?
Open- Why it matters
- Retailer-side inputs feature in the patent architecture.
- Current evidence
- Marketer-facing tools are referenced.
- Missing evidence
- Configuration surfaces exposed to retailers.
- Next step
- Ask for retailer-facing screenshots or docs.
How do U.S. retail customers deploy the combined architecture?
Open- Why it matters
- Establishes practical adoption of the pattern.
- Current evidence
- Case studies exist but omit implementation detail.
- Missing evidence
- Reference implementations from named customers.
- Next step
- Request customer references under NDA.
Is direct consumer-retailer communication supported?
Open- Why it matters
- Relates to the communication step in the patent.
- Current evidence
- Partial — mostly via partner channels.
- Missing evidence
- Native first-party channel documentation.
- Next step
- Clarify capability roadmap.
Are purchasing, reservation or transaction workflows integrated?
Open- Why it matters
- Extends the commercial closure of the patented workflow.
- Current evidence
- Not the current product focus publicly.
- Missing evidence
- Roadmap statements from Foursquare.
- Next step
- Discuss during strategic session.