Advanced Transactions LLC v. Eyebuydirect Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Advanced Transactions, LLC (Georgia)
  • Defendant: EyeBuyDirect, Inc. (Texas)
  • Plaintiff's Counsel: Daignault Iyer LLP
• Case Identification: 1:26-cv-01352, W.D. Tex., 05/21/2026
• Venue Allegations: Venue is alleged to be proper in the Western District of Texas because the Defendant is incorporated under the laws of Texas and maintains its principal place of business in Austin, which is within the district.
• Core Dispute: Plaintiff alleges that Defendant's personalized email marketing system infringes a patent related to a method and system for generating and tracking email campaigns.
• Technical Context: The lawsuit concerns the technical architecture of scalable, personalized email marketing systems, a foundational technology for e-commerce and digital customer engagement.
• Key Procedural History: The complaint notes that the asserted patent's term was adjusted by 696 days, resulting in an expiration date no earlier than March 22, 2023. The complaint also cites Berkheimer v. HP Inc., suggesting an anticipation of a defense based on patent ineligibility under 35 U.S.C. § 101 and asserting that the conventionality of the claimed elements is a question of fact.

Case Timeline

Date	Event
2000-04-25	'555 Patent Priority Date
2001-04-25	'555 Patent Application Filing Date
2006-06-20	'555 Patent Issue Date
2014-03-03	Defendant authorized to do business in Texas
2022-11-11	Earliest date of accused system operation shown via web archive
2023-03-22	'555 Patent Expiration Date (earliest)
2026-05-21	Complaint Filing Date

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

U.S. Patent No. 7,065,555 - "System and Method Related to Generating and Tracking an Email Campaign"

• Patent Identification: U.S. Patent No. 7,065,555 ("System and Method Related to Generating and Tracking an Email Campaign"), issued June 20, 2006 (the "'555 Patent").

The Invention Explained

• Problem Addressed: The patent's background section describes the challenges of early email marketing, including the difficulty of tailoring a large number of emails to individual recipients and the lack of effective methods for tracking campaign success, such as determining receipt and gathering feedback Compl. ¶¶16-17 '555 Patent, col. 1:26-41
• The Patented Solution: The invention proposes a specific software architecture to solve these problems. The system generates an "email campaign template" that is composed of two distinct parts: a "message template" containing the invariant email content and a separate "configuration file" containing variant, per-recipient data (e.g., name, custom URL) that is insertable into the message template Compl. ¶¶18-19 '555 Patent, abstract '555 Patent, FIG. 3A This separation enables scalable personalization and subsequent tracking of the customized emails sent to each recipient '555 Patent, abstract
• Technical Importance: The complaint alleges this architecture provided a more "efficient way to create and track a[n] email campaign" at a time when such techniques were not well-understood, routine, or conventional Compl. ¶21 '555 Patent, col. 1:43-45

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 6, 9, 10, and 11 Compl. ¶29
• The essential elements of independent claim 1 are:
  • receiving an email target database;
  • generating an email campaign template related to at least one email target, which comprises the sub-steps of:
    • generating a message template, and
    • generating a configuration file to contain data related to the email target, where the data is insertable in the message template;
  • sending a corresponding custom email to the email target, formed from the email campaign template; and
  • tracking the sent custom email.

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is the "EyeBuyDirect Email Campaign System," which powers the "EyeBuyDirect Email Campaign Products and Services" Compl. ¶¶11-12

Functionality and Market Context

• The complaint alleges that Defendant operates an online retail business selling eyewear and uses its Email Campaign System to send personalized marketing communications to customers and prospective customers Compl. ¶6 Compl. ¶11 The system collects customer data, including email addresses, through online account creation and a loyalty program Compl. ¶30 It then allegedly sends marketing emails with a consistent layout but containing recipient-specific information and individualized tracking links, generated by merging the recipient data with a common template Compl. ¶32 Compl. ¶34 The complaint provides a screenshot of a "Create account" webpage as evidence of how the system collects user data to form an "email target database" Compl. p. 13

IV. Analysis of Infringement Allegations

Claim Chart Summary

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
(1) receiving an email target database;	The system receives a database of customer email addresses collected via the website's loyalty program registration and online account creation processes.	¶30	col. 8:36-39
(2) generating an email campaign template... wherein step (2) comprises: (a) generating a message template, and	The system generates a message template, as evidenced by marketing emails that follow a consistent layout with branded headers, promotional areas, and designated fields for personalization.	¶32	col. 5:15-20
(b) generating a configuration file to contain data related to each of the at least one email target, wherein the data is insertable in the generated message template;	The system generates per-target configuration data containing recipient-specific information (e.g., name, individualized tracking URLs) which is then inserted into the message template to create the customized emails.	¶33	col. 5:30-34
(3) sending to each of the at least one email target a corresponding custom email, wherein the custom email is formed from the email campaign template;	The system sends marketing emails from its servers to registered customers, with each email containing individualized content (e.g., personalized links) that has been merged into the common template.	¶34	col. 7:1-5
(4) tracking the custom email sent to each of the at least one email target.	The system tracks recipient engagement using embedded mechanisms like tracking pixels (transparent images with unique identifiers loaded upon email opening) and uniquely-coded hyperlinks. The complaint includes email source code showing a tracking pixel URL.	¶35; ¶20	col. 7:22-26

Identified Points of Contention

• Scope Questions: The infringement analysis may turn on the construction of "configuration file." The patent's specification and figures describe generating a distinct "message template" and a "configuration file" (e.g., .cfg file) as outputs of a generator '555 Patent, FIG. 3A The case raises the question of whether a modern, database-driven system, which may populate a template with recipient data "on the fly" without creating a discrete, static "configuration file," falls within the scope of this claim term.
• Technical Questions: A factual question will be how the accused system technically generates and uses tracking URLs. The complaint alleges infringement of claim 6, which requires generating a custom URL and inserting it into the configuration file. It provides an email source code snippet showing a long, parameterized URL for a tracking pixel Compl. p. 19 However, the complaint does not detail the specific method of URL generation, which will likely be a focus of discovery to determine if it aligns with the method described in the patent.

V. Key Claim Terms for Construction

• The Term: "configuration file"
• Context and Importance: This term is at the heart of the patent's described architecture, representing the separation of variable, per-recipient data from the static message template. Practitioners may focus on this term because its scope will determine whether the patent can read on modern email marketing systems that use dynamic database queries rather than the static file-based architecture seemingly contemplated by the patent.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself describes the file functionally as a file "to contain data related to each of the at least one email target" that is "insertable in the generated message template" Compl. ¶24 This functional language could support an argument that any data structure, regardless of its format (e.g., a database record, an XML object), that serves this purpose is a "configuration file."
  • Evidence for a Narrower Interpretation: The patent's detailed description and figures may support a narrower construction. Figure 3A explicitly labels a ".cfg File" (330) as a distinct output of the "Email Campaign Generator" (210), separate from the "Text Message" file (320) '555 Patent, FIG. 3A This suggests the inventor contemplated a discrete, generated file, which could be used to argue that a transient data object from a database query does not meet the limitation.

VI. Other Allegations

• Indirect Infringement: The complaint does not plead specific counts for indirect or contributory infringement. It alleges that Defendant operated the accused system "itself and/or through agents, contractors, and email-marketing service providers acting at EyeBuyDirect's direction and control" Compl. ¶13, which primarily supports a theory of direct infringement but could form a basis for indirect claims later.
• Willful Infringement: The complaint does not explicitly allege willful infringement or pre-suit knowledge of the '555 Patent. However, the prayer for relief requests "enhanced damages" Compl. ¶45, which is contingent on a finding of willful or egregious infringement.

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

• A core issue will be one of definitional scope: can the term "configuration file," which the '555 Patent depicts as a discrete file generated alongside a message template, be construed to cover the data structures used in a modern, database-driven email marketing system where personalization data is dynamically merged with templates at or near the time of sending?
• A key evidentiary question will be one of architectural mapping: does the operational sequence of the accused system-from data collection to email personalization and tracking-align with the specific, ordered steps of the asserted claims? The dispute may focus on whether the accused system's integrated processes can be fairly dissected into the discrete "generating," "inserting," and "forming" steps required by the patent's claims.