DCT

4:25-cv-00002

Schoeneckers Inc v. Ita Group Inc

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 4:25-cv-00002, S.D. Iowa, 09/11/2025
  • Venue Allegations: Venue is based on Defendant ITA Group having a regular and established place of business in the district, combined with alleged acts of infringement. Venue over HTK is asserted on the basis that it is a foreign entity.
  • Core Dispute: Plaintiff alleges that Defendants’ customer loyalty and engagement platforms infringe a family of patents related to portable, embeddable "gamification" or incentive software for websites.
  • Technical Context: The technology involves software-as-a-service platforms that allow website operators to integrate user engagement features, such as points, leaderboards, and achievements, without needing to develop the underlying software architecture themselves.
  • Key Procedural History: The complaint notes that Plaintiff sent a letter to Defendant ITA Group on May 17, 2023, informing it of the patents-in-suit, and alleges that no response was received until after the initial complaint in the case was filed. The three patents-in-suit belong to a single family, with the '421 and '339 patents claiming priority back to the application that issued as the '764 patent.

Case Timeline

Date Event
2007-07-18 Priority Date for ’764, ’421, and ’339 Patents
in 2007 Bunchball (Plaintiff's predecessor) launches Nitro platform
2014-07-01 U.S. Patent No. 8,768,764 Issues
2017-10-03 U.S. Patent No. 9,779,421 Issues
in 2018 BI Worldwide acquires Bunchball
2022-11-15 U.S. Patent No. 11,501,339 Issues
2023-05-17 Plaintiff sends pre-suit notice letter to Defendant ITA Group
2025-09-08 ITA Group's acquisition of HTK publicly disclosed
2025-09-11 Plaintiff files First Amended Complaint

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

U.S. Patent No. 8,768,764 - “Method and System for Embedding a Portable and Customizable Incentive Application on a Website”

The Invention Explained

  • Problem Addressed: The patent’s background section identifies a two-fold problem with website incentive programs at the time: first, each website had to independently develop its own custom software, and second, these custom programs were written for a specific site and were not easily portable or customizable ('764 Patent, col. 1:26-44; Compl. ¶12).
  • The Patented Solution: The invention proposes a system where a "portable incentive application" is provided by a second, centralized website (the service provider) and embedded onto a first website (the client) ('764 Patent, Abstract). This centralized application receives data about user activity on the client website, processes it to award incentives like points or achievements, and displays those incentives to the user through a graphical interface on the client website ('764 Patent, col. 3:21-41; Fig. 20).
  • Technical Importance: This architecture enabled a platform-based approach, allowing any website to integrate sophisticated user engagement mechanics without the cost and time of bespoke software development (Compl. ¶12).

Key Claims at a Glance

  • The complaint asserts at least independent claim 10 (Compl. ¶19).
  • The essential elements of claim 10 include:
    • Providing an incentive application from a network site to be embedded in a first Web site and a second Web site.
    • Receiving and storing activity information from a first viewer on the first Web site.
    • Awarding incentive information to the first viewer based on that activity.
    • Providing the awarded incentive information back to the first viewer via the application on the first Web site.
    • Repeating the process of receiving, awarding, and providing for a second viewer on the second Web site.

U.S. Patent No. 9,779,421 - “Method and System for Embedding a Portable and Customizable Incentive Application on a Website”

The Invention Explained

  • Problem Addressed: As a continuation, the '421 Patent addresses the same problem of creating portable and customizable incentive applications to avoid the need for duplicative, site-specific software development ('421 Patent, col. 1:34-44).
  • The Patented Solution: The '421 Patent claims a system and method centered on a "network site" that communicates with multiple client websites. The network site receives activity information for a viewer on a first website "using an application programming interface (API)," awards incentive information based on that activity, and provides it to an "incentive application embedded in the first website." The process is repeated for other viewers on other websites, which are hosted on "different computer systems" ('421 Patent, col. 12:56-13:25 (Claim 12)). Figure 20 illustrates this architecture, showing a central "Second Site" (2018) providing logic and database services to a "First Site" (2005) via an API (2020) ('421 Patent, Fig. 20).
  • Technical Importance: The explicit claiming of an API-driven architecture for communication between separate computer systems reflects the maturation of the software-as-a-service model for delivering such website engagement tools (Compl. ¶12-14).

Key Claims at a Glance

  • The complaint asserts at least independent claim 12 (Compl. ¶35).
  • The essential elements of claim 12 include:
    • Receiving and storing, at a network site, a first viewer's activity information from a first website via an API.
    • Awarding first incentive information based on the first viewer's activity.
    • Providing the incentive information to a first incentive application embedded in the first website.
    • Repeating the receiving, awarding, and providing steps for a second viewer on a second website hosted on a different computer system.

U.S. Patent No. 11,501,339 - “Method and System for Embedding a Portable and Customizable Incentive Application on a Website”

Technology Synopsis

Continuing the patent family, the ’339 Patent claims a method for providing a portable incentive system. The claimed method involves embedding an incentive application on a first network site, sending that site user's activity information to a central incentive system for an award determination, and then generating an incentive screen on the first site that displays the awarded incentive. The claim requires this process to be repeated for a second, distinct network site (’339 Patent, col. 13:21-41 (Claim 21)).

Asserted Claims

At least independent claim 22 is asserted (Compl. ¶50).

Accused Features

The complaint accuses Defendants' Horizon platform of infringement by alleging it is embedded in client websites, sends user activity data to a central system for processing, and generates incentive displays for users on those client websites (Compl. ¶14, 50-59).

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are Defendants' "gamification platforms," specifically including the "Horizon customer loyalty and engagement platform" originally developed by HTK (Compl. ¶14).

Functionality and Market Context

The complaint alleges that the Horizon platform is "embedded in ITA Group's customer solutions" to "incentivize employees and/or customers to use their clients' websites" (Compl. ¶14). The platform is positioned as a direct competitor to the Plaintiff's Bunchball Nitro platform, which embodies the patented technology (Compl. ¶14). No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint references claim-chart exhibits that are not provided in the filed document; therefore, the infringement theories are summarized below in prose.

'764 Patent Infringement Allegations

  • Narrative Summary: The complaint alleges that Defendants' platform infringes at least claim 10 of the ’764 Patent by operating a central system (the "network site") that provides its Horizon platform (the "incentive application") to be embedded within its various customers' websites (the "first Web site" and "second Web site") (Compl. ¶19-28). It is alleged that this system receives user activity data from those customer websites, awards incentives, and delivers them back to the user via the embedded platform interface (Compl. ¶19-28).
  • Identified Points of Contention:
    • Scope Questions: A potential issue may be whether the Defendants' business model, which involves providing a platform to its distinct corporate customers, meets the claim requirement of a single "network site" providing an application to both a "first Web site" and a "second Web site."
    • Technical Questions: The complaint does not provide technical detail on how the Horizon platform is "embedded" or how it "receives" user data. A central question for the court will be whether the actual technical implementation of the accused platform matches the steps recited in claim 10.

'421 Patent Infringement Allegations

  • Narrative Summary: The infringement theory for claim 12 of the ’421 Patent is that Defendants' central server infrastructure acts as the claimed "network site" (Compl. ¶35-43). This network site allegedly receives user activity information from its customers' websites (which are hosted on "different computer systems") via an "application programming interface (API)" ('421 Patent, col. 12:59). The system then allegedly awards incentives and provides this information back to the "incentive application embedded" in the customer's website (Compl. ¶35-43).
  • Identified Points of Contention:
    • Scope Questions: The analysis may focus on whether the communication protocol between the Horizon platform and its client websites constitutes an "application programming interface (API)" as the term is used in the patent.
    • Technical Questions: What evidence does the complaint provide that the customer websites using the Horizon platform are in fact hosted on "different computer systems" as the claim requires? This factual element will be critical to proving infringement.

V. Key Claim Terms for Construction

  • The Term: "incentive application"

  • Context and Importance: This term is the core subject matter of the patents. Its construction will determine whether the accused Horizon platform is the type of technology covered by the claims. Practitioners may focus on this term because its scope—whether it is limited to the portable and customizable embodiments described in the specification or covers any embedded reward software—is central to the infringement case.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The specification describes the term broadly as a "software application that is written in any programmable software language" ('421 Patent, col. 4:3-4) and generates an "incentive screen" ('421 Patent, col. 3:45-47).
    • Evidence for a Narrower Interpretation: The Summary of the Invention and Background sections repeatedly emphasize that the invention is an "incentive application that is both portable and customizable" ('421 Patent, col. 1:45-47). A party could argue that these characteristics are definitional limitations, not merely features of a preferred embodiment.
  • The Term: "application programming interface (API)" (in the '421 Patent)

  • Context and Importance: This term defines the crucial communication link between the client website and the central incentive-awarding system in claim 12 of the '421 Patent. The infringement allegation rests on the accused platform using such an API.

  • Intrinsic Evidence for Interpretation:

    • Evidence for a Broader Interpretation: The specification provides a functional definition as "a set of routines, protocols and tools for obtaining the necessary data and functions from the second site" ('421 Patent, col. 3:51-54), which could encompass a wide variety of modern web service communication methods.
    • Evidence for a Narrower Interpretation: While the specification does not appear to provide explicit narrowing language, a party may argue that the context of the invention implies a more formal, structured interface than simple data transmissions, potentially looking to the understanding of one of ordinary skill in the art at the time of the invention.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement for all three patents. Inducement is based on allegations that Defendants "directly encourage their customers to use the platform in a way that results in infringement" (Compl. ¶29, 44, 61). Contributory infringement is based on the allegation that the accused platform "is not a staple article of commerce suitable for substantial non-infringing uses" (Compl. ¶29, 44, 61).
  • Willful Infringement: Willfulness is alleged based on both pre-suit and post-suit knowledge. The complaint alleges pre-suit knowledge based on a notice letter sent to ITA Group on May 17, 2023, and post-suit knowledge based on the filing of the lawsuit itself (Compl. ¶15, 30, 45, 62).

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

  • A core issue will be one of architectural mapping: Does the Defendants' Horizon platform, provided as a service to distinct corporate clients, practice the specific client-server architecture claimed in the patents? This analysis will likely turn on the construction of key terms like "incentive application," "network site," and "API" and whether the accused system's components and data flows map onto the claim elements.
  • A second central issue will be one of evidentiary proof: What technical evidence will be presented to demonstrate that the accused platform actually performs each step of the asserted method claims? The dispute may hinge on detailed evidence from source code, server logs, and network traffic analysis to prove that the Horizon platform "receives... activity information" and "awards incentive information" in the specific manner required by the claims.