From 61d5b9e6bb7cd95337bc40b70261fc91b94a6955 Mon Sep 17 00:00:00 2001
From: kenneth <kenneth@nym.sh>
Date: Sun, 8 Mar 2026 02:40:09 +0000
Subject: [PATCH] fix(waitlist): use segments instead of audienceId

Co-authored-by: Ona <no-reply@ona.com>
---
 apps/waitlist-website/app/routes/home.tsx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/apps/waitlist-website/app/routes/home.tsx b/apps/waitlist-website/app/routes/home.tsx
index 86e94b4..024bd2e 100644
--- a/apps/waitlist-website/app/routes/home.tsx
+++ b/apps/waitlist-website/app/routes/home.tsx
@@ -62,10 +62,10 @@ export async function action({ request }: Route.ActionArgs) {
 
 	const resend = new Resend(process.env.RESEND_API_KEY)
 
-	const audienceId = process.env.RESEND_AUDIENCE_ID!
+	const segmentId = "b80fb036-74a1-4f7d-bca5-2c035b696071"
 
 	const dup = await resend.contacts.get({
-		audienceId,
+		segmentId,
 		email,
 	})
 	if (dup.data) {
@@ -73,8 +73,8 @@ export async function action({ request }: Route.ActionArgs) {
 	}
 
 	const res = await resend.contacts.create({
-		audienceId,
 		email,
+		segments: [{ id: segmentId }],
 	})
 
 	if (res.error) {