Files
QR-master/src/lib/metaConversions.ts
Timo Knuth 53ef4b3b91 Serve the app on app.qrmaster.net, marketing on www
Splits the two hostnames across one deployment. No files move: the Next app still
serves every route on both hosts, and the middleware decides per host which paths it
owns and 301s the rest. /login and /signup stay on www - all 82 marketing CTAs point
at /signup, which carries a hard canonical to www plus ad traffic.

src/lib/hosts.ts is the single source of truth for the boundary (APP_PATH_PREFIXES,
isAppPath, wwwUrl, appUrl, urlForPath). The middleware and every absolute-URL builder
read from it so they cannot drift apart.

- Split the overloaded NEXT_PUBLIC_APP_URL into a www and an app origin. It previously
  fed both public URLs and in-app URLs, so any single value was wrong somewhere. Most
  important: QRCodeCard encodes this origin into the QR code the user downloads and
  prints, so it must stay on www.
- Route Stripe return URLs, email links and OAuth redirects per path rather than
  against one origin, so /dashboard lands on app and /pricing on www.
- Cross the host boundary once, after a successful login: the router cannot push across
  origins, so that jump needs a full load. The user arrives signed in because the
  session cookie is scoped to COOKIE_DOMAIN.
- Keep the app host out of search indexes: X-Robots-Tag on every response plus a
  Disallow-all robots.txt via rewrite, and /sitemap.xml redirects to www.
- Point the TikTok callback fallback at www explicitly. It used to read
  NEXT_PUBLIC_APP_URL, whose meaning changed here, and only the apex domain is
  verified with TikTok.

Host splitting is inert while both origins are equal, so development is unaffected.

Verified: tsc clean, production build succeeds including the Edge middleware bundle,
and the path-to-host mapping is unit-checked (prefix traps like /created and
/settings-guide stay on www, query strings do not break matching).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 19:44:08 +02:00

71 lines
2.2 KiB
TypeScript

import * as crypto from 'crypto';
import { getWwwOrigin } from '@/lib/hosts';
const BASE_URL = 'https://graph.facebook.com/v21.0';
const PIXEL_ID = process.env.META_PIXEL_ID;
const ACCESS_TOKEN = process.env.META_ACCESS_TOKEN;
function hashValue(value: string): string {
return crypto.createHash('sha256').update(value.trim().toLowerCase()).digest('hex');
}
interface UserData {
email?: string;
ip?: string;
userAgent?: string;
fbc?: string;
fbp?: string;
}
interface ConversionEvent {
eventName: 'CompleteRegistration' | 'Purchase' | 'ViewContent' | 'Lead' | 'InitiateCheckout';
eventTime?: number;
eventSourceUrl?: string;
userData: UserData;
customData?: Record<string, unknown>;
}
export async function sendConversionEvent(event: ConversionEvent): Promise<void> {
if (!PIXEL_ID || !ACCESS_TOKEN) {
return;
}
const hashedUserData: Record<string, string> = {};
if (event.userData.email) hashedUserData.em = hashValue(event.userData.email);
if (event.userData.ip) hashedUserData.client_ip_address = event.userData.ip;
if (event.userData.userAgent) hashedUserData.client_user_agent = event.userData.userAgent;
if (event.userData.fbc) hashedUserData.fbc = event.userData.fbc;
if (event.userData.fbp) hashedUserData.fbp = event.userData.fbp;
const payload = {
data: [
{
event_name: event.eventName,
event_time: event.eventTime ?? Math.floor(Date.now() / 1000),
// Ad attribution happens on the public site, so the fallback is the marketing host.
event_source_url: event.eventSourceUrl ?? getWwwOrigin(),
action_source: 'website',
user_data: hashedUserData,
custom_data: event.customData ?? {},
},
],
};
try {
const res = await fetch(`${BASE_URL}/${PIXEL_ID}/events?access_token=${ACCESS_TOKEN}`, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify(payload),
});
if (!res.ok) {
const err = await res.json();
console.error('[Meta CAPI] Error:', err);
}
} catch (error) {
console.error('[Meta CAPI] Network error:', error);
}
}
export { hashValue };