Schoeneckers Inc v. Kobie Marketing Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Schoeneckers, Inc. d/b/a BI Worldwide (Minnesota)
  • Defendant: Kobie Marketing, Inc. (Delaware)
  • Plaintiff's Counsel: Richards, Layton & Finger, P.A. and CARLSON CASPERS VANDENBURGH & LINDQUIST PA
• Case Identification: 1:25-cv-01263, D. Del., 10/15/2025
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is a Delaware corporation and is therefore deemed to reside in the judicial district.
• Core Dispute: Plaintiff alleges that Defendant's gamification and loyalty platform infringes three patents related to portable and customizable incentive applications for websites.
• Technical Context: The technology at issue involves "gamification" platforms that provide embeddable, customizable incentive and reward features to increase user engagement on third-party websites.
• Key Procedural History: The complaint notes pre-suit correspondence, beginning with a letter from Plaintiff to Defendant on May 17, 2023, regarding the alleged infringement. After a follow-up in May 2024, Defendant responded on September 25, 2025, stating it did not believe it was infringing but provided no explanation.

Case Timeline

Date	Event
2007-07-18	Priority Date for '764, '421, and '339 Patents
2007-01-01	Plaintiff's predecessor Bunchball launches its Nitro platform
2014-07-01	U.S. Patent No. 8,768,764 issues
2017-10-03	U.S. Patent No. 9,779,421 issues
2018-01-01	BI Worldwide acquires Bunchball
2022-11-15	U.S. Patent No. 11,501,339 issues
2023-05-17	Plaintiff first contacts Defendant regarding alleged infringement
2024-05-01	Plaintiff sends follow-up correspondence to Defendant
2025-09-25	Defendant responds to Plaintiff, denying infringement
2025-10-15	Complaint filed

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"

• Patent Identification: U.S. Patent No. 8,768,764, "Method and System for Embedding a Portable and Customizable Incentive Application on a Website," issued July 1, 2014. Compl. ¶13 '764 Patent, cover

The Invention Explained

• Problem Addressed: The patent's background section describes that, at the time of the invention, incentive software programs for websites had to be independently developed for each site and, once written, were not easily customizable. '764 Patent, col. 1:26-38 Compl. ¶8
• The Patented Solution: The patent discloses a system where a "portable incentive application" is provided from a central "second site" (the service provider) and embedded into a "first site" (the client's website). '764 Patent, col. 3:3-9 '764 Patent, FIG. 1 This application generates incentives for visitors of the first site, such as points or leaderboards, based on their activity, with the underlying logic and database managed by the second site. '764 Patent, abstract '764 Patent, FIG. 20
• Technical Importance: This architecture aimed to create a universally portable and customizable incentive application, allowing website owners to easily add gamification features without bespoke development. '764 Patent, col. 1:39-43

Key Claims at a Glance

• The complaint asserts at least independent method claim 10. Compl. ¶14
• The essential elements of Claim 10 include:
  • providing an incentive application from a network site to a first and second Web site to be embedded;
  • receiving and storing activity information of a first viewer on the first Web site;
  • awarding incentive information to the first viewer based on that activity;
  • providing the awarded incentive information to the first viewer upon their return to the first Web site to incentivize further activity;
  • performing the same steps of receiving, awarding, and providing for a second viewer on the second Web site.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

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

• Patent Identification: U.S. Patent No. 9,779,421, "Method and System for Embedding a Portable and Customizable Incentive Application on a Website," issued October 3, 2017. Compl. ¶29 '421 Patent, cover

The Invention Explained

• Problem Addressed: As a continuation of the '764 patent, the '421 Patent addresses the same problem of site-specific, non-portable website incentive programs. '421 Patent, col. 1:35-45
• The Patented Solution: The '421 Patent refines the invention by focusing on the use of an Application Programming Interface (API). The system involves a network site receiving activity information from a viewer on a first website via an API, awarding incentives, and then providing that incentive information back to an application embedded on the first website. '421 Patent, claim 12 The architecture, illustrated in FIG. 20, shows an API as the communication layer between the "First Site" and the "Incentive Application Logic/Engine." '421 Patent, FIG. 20
• Technical Importance: This API-centric approach standardized the integration method, allowing for more flexible and robust communication between a client website and the back-end incentive platform. '421 Patent, col. 3:51-4:6

Key Claims at a Glance

• The complaint asserts at least independent method claim 12. Compl. ¶30
• The essential elements of Claim 12 include:
  • receiving and storing, at a network site, a first viewer's activity information from a first website using an API;
  • awarding first incentive information to the viewer based on that activity;
  • providing the incentive information to an incentive application embedded in the first website, which is then displayed to the viewer;
  • performing the same steps for a second viewer on a second website.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

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

• Patent Identification: U.S. Patent No. 11,501,339, "Method and System for Embedding a Portable and Customizable Incentive Application on a Website," issued November 15, 2022. Compl. ¶44
• Technology Synopsis: As a further continuation, this patent claims a method performed by an "incentive application system" (including a server, processor, and memory) that embeds an application on a network site. The system receives activity information from the site, awards incentives, and generates an "incentive screen" on the site to display the awarded information. '339 Patent, abstract '339 Patent, claim 21
• Asserted Claims: The complaint asserts at least independent method claim 21. Compl. ¶45
• Accused Features: The complaint alleges that Defendant's gamification platform, which includes a server, processor, and application logic, infringes by being embedded on client network sites, processing user activity, and generating incentive displays. (Compl. ¶10, Compl. ¶45; Compl. ¶46; Compl. ¶47; Compl. ¶48; Compl. ¶49; Compl. ¶50; Compl. ¶51; Compl. ¶52).

III. The Accused Instrumentality

• Product Identification: The accused instrumentality is Defendant's "gamification platform," identified as the "Kobie Alchemy Loyalty Cloud" ("KALC"). Compl. ¶10 Compl. Ex. I, p. 160
• Functionality and Market Context: The complaint alleges that KALC is a "cloud-native platform" that allows clients to create and manage data-driven, personalized loyalty programs. Compl. Ex. I, p. 167 It is advertised as enabling "seamless digital integration" that allows clients to "[e]mbed loyalty features into mobile apps, self-service portals, and customer support" systems. Compl. Ex. N, p. 209 The platform allegedly uses "3rd-party integrations, partner-ready modules, and APIs" to connect to client websites and "enables frictionless data flow" to collect user data and deliver personalized rewards. Compl. Ex. I, p. 167 The complaint alleges that this platform directly competes with Plaintiff's Bunchball Nitro platform. Compl. ¶10

IV. Analysis of Infringement Allegations

A screenshot from Defendant's website, included in the complaint, describes "Seamless digital integration" and explicitly states the platform can "Embed loyalty features into mobile apps, self-service portals, and customer support." Compl. Ex. N, p. 209 Another screenshot highlights the platform's "Extensibility that unlocks personalization," noting its use of "3rd-party integrations, partner-ready modules, and APIs." Compl. Ex. I, p. 167

8,768,764 Infringement Allegations

Claim Element (from Independent Claim 10)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
providing an incentive application from a network site over a data network to a first Web site and a second Web site...the incentive application to be embedded in the first Web site and the second Web site, respectively;	Kobie's platform provides its incentive application from its network site to be embedded in its clients' websites, which operate on different computer systems.	¶15	col. 3:3-9
receiving and storing, at the network site, activity information of a first viewer from a provider of the first Web site, the activity information of the first viewer indicating the first viewer's involvement with the first Web site;	Kobie's platform allegedly receives and stores activity information from viewers on its clients' websites, including transactional and behavioral data.	¶16	col. 7:60-8:0
awarding, by the computing system, incentive information to the first viewer based on the activity information of the first viewer;	Kobie's platform allegedly includes a computing system that awards incentives to viewers based on their website activity, using configurable rules to orchestrate tiers and currency.	¶17	col. 4:26-34
providing, using the incentive application at the first Web site, the first incentive information awarded to the first viewer when the first viewer returns to visit the first Web site...to incentivize additional activity...	Kobie's platform allegedly provides incentive information to viewers upon their return visits to client websites to incentivize further activity.	¶18	col. 4:1-9
[receiving, awarding, and providing incentive information for a second viewer on a second Web site]	The complaint alleges Kobie's platform performs the same functions for multiple viewers across multiple client websites.	¶¶19-22	col. 4:1-9

9,779,421 Infringement Allegations

Claim Element (from Independent Claim 12)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving and storing, at a network site, activity information of a first viewer from a first website...using an application programming interface (API) operable at the network site;	Kobie's platform allegedly receives and stores viewer activity information from client websites using an API, advertising over 600 APIs for this purpose.	¶32	col. 3:51-55
awarding, by the network site, first incentive information to the first viewer based on the activity information of the first viewer;	The network site allegedly awards incentive information to viewers based on their activity, using its toolset to determine when a marketing action should occur.	¶33	col. 4:26-34
providing the first incentive information to a first incentive application embedded in the first website...the first incentive information to be displayed to the first viewer by the first website using the first incentive application;	Kobie's platform allegedly provides an incentive application for embedding in client websites that displays the viewer's awarded incentive information.	¶34	col. 4:1-9
[receiving, awarding, and providing incentive information for a second viewer on a second website]	The complaint alleges Kobie's platform performs the same functions for multiple viewers and can scale across different client websites.	¶¶35-37	col. 4:1-9

• Identified Points of Contention:
  • Scope Questions: A central question may be whether the term "incentive application", as described in the patents from 2007, can be read to encompass a modern, distributed, cloud-native service like Kobie's Alchemy Loyalty Cloud, which is composed of APIs, modules, and a back-end platform.
  • Technical Questions: A point of contention may arise over the definition of "embedded". The analysis will question whether using APIs to integrate features from a remote server, as Kobie's platform is alleged to do, meets the "embedding" limitation, particularly given the patents' reference to both API and "OBJECT/EMBED" tag implementations.

V. Key Claim Terms for Construction

• The Term: "incentive application"

• Context and Importance: This term is the central subject of the asserted claims. Its construction will be critical in determining whether Defendant's multi-component "Kobie Alchemy Loyalty Cloud" platform, with its APIs and modules, constitutes the claimed "incentive application".

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification describes the "incentive application" as comprising numerous distinct "incentive components" such as points, levels, leaderboards, achievements, and virtual rooms, which may be selected by a user, suggesting a modular and flexible nature. '764 Patent, col. 4:29-34
  • Evidence for a Narrower Interpretation: The specification also describes the "incentive application" as a "software application that is written in any programmable software language such as Java, C, C++, Visual Basic, Adobe Flash or the like," which could be argued to connote a more self-contained software program rather than a distributed cloud service. '764 Patent, col. 3:56-61

• The Term: "embedded in the...Web site"

• Context and Importance: This term defines the fundamental act of integration between the client's website (the "first site") and the incentive platform. The infringement case may hinge on whether calling features from a remote platform via an API, as Kobie allegedly does, qualifies as "embedding."

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification explicitly contemplates an API-based embodiment where "the second site 45 provides an application program interface (API) (in lieu of a portable incentive application)" and the first site "uses the API to retrieve the needed information from the second site 45." '764 Patent, col. 3:41-52 This language may support a finding that API integration falls within the scope of the claims.
  • Evidence for a Narrower Interpretation: The specification also provides a specific example of embedding using "OBJECT\EMBED tags, as are known in the art," which a party could argue implies a more direct inclusion of code within the host website's structure. '764 Patent, col. 7:16-18

VI. Other Allegations

• Indirect Infringement: For all three patents, the complaint alleges induced and contributory infringement. The inducement allegations are based on Defendant allegedly encouraging its customers to use the KALC platform in an infringing manner. Compl. ¶¶24, 39, 54 The basis for contributory infringement is the allegation that the platform is not a "staple article of commerce suitable for substantial non-infringing uses." Compl. ¶¶24, 39, 54
• Willful Infringement: The complaint alleges willful infringement for all three patents, asserting that Defendant had knowledge of the patents "since before this complaint was filed." Compl. ¶¶24, 39, 54 This allegation is supported by pre-suit correspondence initiated by Plaintiff on May 17, 2023. Compl. ¶11

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

• A core issue will be one of architectural equivalence: does Defendant's modern, cloud-native loyalty platform, which utilizes APIs and "partner-ready modules," constitute the "incentive application...embedded" in a client's website, as that system is described in a patent family with a 2007 priority date?
• A key evidentiary question will be one of definitional scope: can the term "embedded", which the patent specification discusses in the context of both API calls and literal "OBJECT/EMBED" tags, be construed broadly enough to read on the integration method of Defendant's accused platform, especially given Defendant's own marketing materials use the word "embed"?
• The analysis will likely focus on a temporal-technological translation: how will the court interpret claim terms drafted in the era of Flash applications and direct code embedding when applied to today's distributed, API-first, cloud-based service architectures?