DCT

1:26-cv-02783

Outleads Inc v. Salesforce Inc

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: Outleads Inc. v. Salesforce, Inc., 1:26-cv-02783, E.D. Va., 08/26/2026
  • Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Virginia because Defendant Salesforce, Inc. conducts business in the district, including through offices in McLean and Herndon, operates data centers in Northern Virginia, and derives substantial revenue from infringing products and services provided in the district.
  • Core Dispute: Plaintiff alleges that Defendant's customer relationship management (CRM) services, specifically its Web-to-Lead and Web-to-Case features, infringe seven U.S. patents related to systems and methods for associating offline data records with online user activity.
  • Technical Context: The technology at issue addresses the challenge of creating a unified customer profile by linking a user's anonymous online activities (e.g., website visits) with their subsequent offline interactions (e.g., CRM updates, phone calls) in the marketing and sales analytics domain.
  • Key Procedural History: The complaint alleges a history of interaction between the parties, noting that Plaintiff applied to Salesforce's ISV program in 2014, explicitly referencing its "patent-pending technology." It further alleges that a Salesforce Vice President judged Plaintiff's technology at a competition in October 2015. The complaint also references the prosecution history of the '547 and '061 patents, noting that amendments were made to overcome prior art, which may be relevant to future claim construction arguments.

Case Timeline

Date Event
2013-10-25 Earliest Priority Date for all Asserted Patents
2014-01-01 Outleads Inc. founded
2014-01-01 Outleads applies to Salesforce ISV program, referencing "patent-pending technology"
2015-10-01 A Salesforce VP judges Outleads's technology at the &THEN Hot Zone competition
2016-05-17 U.S. Patent No. 9,342,843 ('843 Patent) issues
2016-11-08 U.S. Patent No. 9,491,249 ('249 Patent) issues
2019-12-31 U.S. Patent No. 10,523,627 ('627 Patent) issues
2020-10-06 U.S. Patent No. 10,798,046 ('046 Patent) issues
2023-06-06 U.S. Patent No. 11,671,397 ('397 Patent) issues
2025-03-12 USPTO issues Notice of Allowance for the '061 Patent
2025-04-23 '547 Patent amendment filed during prosecution
2025-05-15 USPTO issues Notice of Allowance for the '547 Patent
2025-07-15 U.S. Patent No. 12,363,061 ('061 Patent) issues
2025-09-09 U.S. Patent No. 12,413,547 ('547 Patent) issues
2026-08-26 Complaint filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 12,413,547 - "System for Associating Offline Data with Online Activity", Issued September 9, 2025

The Invention Explained

  • Problem Addressed: The patent addresses shortcomings in network architectures that treated user interactions across mobile devices, desktops, and landlines as isolated, "orphaned network events" (Compl. ¶41). Prior systems allegedly suffered from data collision, matching failures, and privacy issues by requiring user logins or passing insecure personally identifiable information (PII) (Compl. ¶41; Compl. ¶42).
  • The Patented Solution: The invention introduces a network architecture that programmatically links offline data (e.g., a CRM update) to an anonymous user-level identifier from a web session, creating a unified digital record without relying on intermediate PII hashing or large pools of proxy phone numbers (Compl. ¶43). The system uses a tracking server to merge fragmented offline records into a cohesive digital architecture, pushing offline activities back to a web analytics server as discrete digital events (Compl. ¶43; Compl. ¶44).
  • Technical Importance: This architecture aimed to solve the "offline-to-online identity gap" in a way that improved data integrity and computational efficiency over batch-upload systems while enhancing user privacy (Compl. ¶43; Compl. ¶45).

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 (Compl. ¶52).
  • The complaint references an external claim chart (Exhibit M) that is not provided, and does not break down the claim elements in the body of the complaint. Based on the complaint's description, the essential elements of claim 1 appear to involve a system comprising a tracker server that:
    • Utilizes an offline event (like a CRM update) as a trigger.
    • Programmatically binds stateful offline data to an anonymous user-level identifier associated with a web session.
    • Merges fragmented offline records to create a cohesive digital architecture.
    • Enriches data using information from a source other than the website visit's own tracking cookie (Compl. ¶43; Compl. ¶44; Compl. ¶48).
  • The complaint notes the existence of dependent claims that further describe a specific centralized system architecture (Compl. ¶47).

U.S. Patent No. 12,363,061 - "System for Associating Offline Data with Online Activity", Issued July 15, 2025

The Invention Explained

  • Problem Addressed: The patent addresses the same fundamental problem as the '547 Patent: network architectures that treat user interactions from various devices and CRM systems as "isolated, orphaned network events" (Compl. ¶64). These systems required insecure PII transmissions or used inefficient brute-force hardware scaling, leading to data loss and network bottlenecks (Compl. ¶64; Compl. ¶65).
  • The Patented Solution: The '061 Patent claims a network architecture with a tracking server that, upon notice of a website visit, obtains a user-level identifier and creates a user activity record (Compl. ¶66). This system then uses subsequent offline activity (e.g., a CRM update) to bind stateful offline data directly to the anonymous identifier, leveraging "truly external offline data" not derived from the website's own tracking cookie for enrichment (Compl. ¶66). This process programmatically pushes the matched data back to a receiving system as discrete digital events (Compl. ¶67).
  • Technical Importance: This approach provided a real-time, computationally efficient method for creating a unified customer view, avoiding the latency and data integrity issues of prior art batch-upload systems (Compl. ¶68).

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 (Compl. ¶75).
  • The complaint references an external claim chart (Exhibit N) that is not provided. The essential elements of claim 1 appear to be similar to those of the '547 Patent, involving a system with a tracking server that:
    • Obtains a user-level identifier upon a website visit.
    • Creates a user activity record.
    • Uses an offline source to programmatically bind offline data to the user-level identifier.
    • Leverages data from an "additional source" that is not a cookie from the website visit (Compl. ¶66).
  • The complaint notes dependent claims (e.g., 4, 6, and 8) that further describe specific architectural mechanisms, such as integrating agent-entered data and creating a feedback loop with advertising platforms (Compl. ¶¶69-70).

U.S. Patent No. 11,671,397 - "System for Associating Offline Data with Online Activity", Issued June 6, 2023

  • Technology Synopsis: The '397 Patent is a divisional of the '046 Patent and addresses the "broken identity" problem in web analytics (Compl. ¶87). It claims a "cookie-less" system using a server-generated user ID and a unified tracking system to link data from all channels, collecting additional information from a source other than the visited website and appending it to the user's activity record (Compl. ¶87).
  • Asserted Claims: At least claim 1 (Compl. ¶93).
  • Accused Features: Salesforce's Web-to-Lead and Web-to-Case services (Compl. ¶93).

U.S. Patent No. 10,798,046 - "System for Integrating Offsite Data Records with Online Data Records", Issued October 6, 2020

  • Technology Synopsis: The '046 Patent, a parent of the '397 Patent, establishes a distributed, multi-node network architecture to synchronize interactions across distinct computer systems (Compl. ¶105). It describes a topology with a first system for identity tracking, a second for lead management, and an external system for website hosting, using a unique identifier to associate the distributed data sets (Compl. ¶105).
  • Asserted Claims: At least claim 1 (Compl. ¶110).
  • Accused Features: Salesforce's Web-to-Lead and Web-to-Case services (Compl. ¶110).

U.S. Patent No. 10,523,627 - "Integrating Offsite Data Records with Online Data Records", Issued December 31, 2019

  • Technology Synopsis: The '627 Patent claims a multi-node network system for tracking and integrating user data from online "native form" submissions (Compl. ¶122; '627 Patent, Claim 1). When a user submits a form, a unique tracking identifier is passed with the form data to a second computer system (like a CRM); subsequent offline ancillary data is then routed back to the user's online profile using the retained identifier (Compl. ¶122).
  • Asserted Claims: At least claim 1 (Compl. ¶126).
  • Accused Features: Salesforce's Web-to-Lead and Web-to-Case services (Compl. ¶126).

U.S. Patent No. 9,491,249 - "Integrating Offsite Activities Related to Chat and Text Messaging with Online Data Records", Issued November 8, 2016

  • Technology Synopsis: The '249 Patent claims methods for integrating offline, offsite, and online data records in the context of chat and text messaging (Compl. ¶138). The system appends a system-generated identifier to a text or chat message link, which persists as the communication moves offsite to create a unified data record (Compl. ¶138).
  • Asserted Claims: At least claim 1 (Compl. ¶142).
  • Accused Features: Salesforce's Web-to-Lead and Web-to-Case services (Compl. ¶142).

U.S. Patent No. 9,342,843 - "Integration of Offline Activity Records and Online Data Records", Issued May 17, 2016

  • Technology Synopsis: This foundational patent introduces a distributed, multi-node network architecture that enables an online tracking identifier to be invisibly appended to a submitted digital form (Compl. ¶154). The identifier is then passed through a sequence of disparate databases and human-operated endpoints to maintain an unbroken data chain from an initial web session to subsequent offline events (Compl. ¶154).
  • Asserted Claims: At least claim 1 (Compl. ¶158).
  • Accused Features: Salesforce's Web-to-Lead and Web-to-Case services (Compl. ¶158).

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are Salesforce's "Web-to-Lead" and "Web-to-Case" technologies and the broader Salesforce platform and services that leverage the data they generate (Compl. ¶37).

Functionality and Market Context

  • The complaint alleges that in Salesforce's system, web analytics data is linked to CRM data using a user-level identifier, such as a Client ID from Google Analytics or a UUID from Salesforce Experience Cloud (Compl. ¶36).
  • When a user fills out a "Web-to-Lead" or "Web-to-Case" form on a website, this unique identifier is allegedly captured and stored within that customer's record in the Salesforce CRM (Compl. ¶36).
  • Salesforce is alleged to use this identifier to "integrate and enrich CRM data pertaining to customers" and to communicate Salesforce data to external systems like Google Analytics (Compl. ¶36). The complaint positions Salesforce as the "#1 AI CRM," indicating significant market presence (Compl. ¶35).

IV. Analysis of Infringement Allegations

The complaint references external claim chart exhibits (Exhibits M and N) for the '547 and '061 patents, but these exhibits are not provided. The complaint alleges that Salesforce's Web-to-Lead and Web-to-Case services practice at least claim 1 of each patent (Compl. ¶52; Compl. ¶75). The core of the infringement theory is that by capturing a user-level identifier (e.g., a Google Analytics Client ID) when a web form is submitted and storing it in the corresponding CRM record, Salesforce's system performs the patented method of associating online activity with offline data records (Compl. ¶36). This process allegedly creates the claimed "singular, cohesive digital architecture" by programmatically binding an offline event (the form submission) to an online session identifier (Compl. ¶44; Compl. ¶67). A screenshot from a Salesforce help article shows instructions for customers to generate and test Web-to-Case forms, which the plaintiff may use as evidence of the accused functionality (Compl. p. 19).

Identified Points of Contention

  • Scope Questions: A central question will be whether capturing an identifier generated by a third-party analytics script (e.g., Google Analytics) at the moment of a form submission qualifies as leveraging an "offline source" or "additional source... not... from cookie-based web tracking" as the patent claims allegedly require (Compl. ¶43; Compl. ¶48; Compl. ¶66). The court may need to determine if the identifier is part of the "online activity" itself or a distinct, external source as contemplated by the patents.
  • Technical Questions: A key technical question will be whether the data flow in Salesforce's system matches the specific architectural steps recited in the claims. This may involve examining whether Salesforce's system "programmatically push[es]" the data in the specific manner claimed, or if there is a fundamental mismatch in the operational sequence compared to the patented method of creating a "singular, cohesive digital architecture" (Compl. ¶44; Compl. ¶67).

V. Key Claim Terms for Construction

The Term

"additional information" (from a source "other than the website visit")

Context and Importance

The complaint emphasizes that during the prosecution of the '547 Patent, claims were amended to "reinforce that the data enrichment of 'additional information' involves a source other than the website visit (i.e., not from cookie-based web tracking)" (Compl. ¶48). The construction of this term appears central to distinguishing the invention from prior art that used cookies for tracking and will be critical for determining infringement by Salesforce's system, which allegedly uses identifiers from third-party analytics scripts (Compl. ¶36).

Intrinsic Evidence for Interpretation

  • Evidence for a Broader Interpretation: The patents' general description of solving the "offline-to-online identity gap" and creating a "cohesive digital architecture" could support a reading where any data not generated by the website's primary server-including data from a third-party script like Google Analytics-qualifies as "additional information" (Compl. ¶43; Compl. ¶44).
  • Evidence for a Narrower Interpretation: The specification's use of examples like an "inbound telephonic trigger or CRM update acting as an offline source" could suggest a narrower construction limited to data generated from events that are temporally and architecturally separate from the web session itself (Compl. ¶43; Compl. ¶66). The explicit carve-out of "cookie-based web tracking" (Compl. ¶48) may be argued to exclude identifiers that, while not first-party cookies, are still fundamentally part of the web tracking session.

VI. Other Allegations

Indirect Infringement

The complaint alleges that Salesforce knowingly induces infringement by providing customers with the Accused Products and publishing materials, such as user guides, that instruct customers on how to use the infringing Web-to-Lead and Web-to-Case services (Compl. ¶54; Compl. ¶77). The complaint includes a screenshot of a Salesforce help document titled "Generate and Test Your Web-to-Case Form" as a non-limiting example of such materials (Compl. p. 19).

Willful Infringement

The complaint alleges willful infringement based on Salesforce's alleged pre-suit knowledge of the patent portfolio, dating back to a 2014 application by Plaintiff to Salesforce's ISV program and a 2015 conference where a Salesforce executive allegedly judged Plaintiff's technology (Compl. ¶¶29-32). The complaint alleges that Salesforce continued its infringing activities despite an objectively high likelihood of infringement, constituting willful and deliberate conduct (Compl. ¶57; Compl. ¶80).

VII. Analyst's Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can the patents' concept of linking "offline data" from an "additional source" be construed to cover identifiers (e.g., a Google Analytics Client ID) that are generated by a third-party script during the user's online web session, or is it limited to data from events that are truly separate from the web visit, such as a subsequent phone call or manual CRM entry?
  • A key evidentiary question will be factual and technical: does the specific architecture and data-flow process of Salesforce's Web-to-Lead and Web-to-Case products perform the same sequence of steps-such as creating and merging records on a "tracking server"-in the same way as required by the asserted claims, or is there a fundamental operational mismatch?
  • A central question of knowledge for willfulness and indirect infringement will be what Salesforce knew about the patent-pending technology and when, based on the alleged 2014 ISV program application and 2015 technology competition, and whether that knowledge is sufficient to meet the legal standards for intent.