Direct Response to George Roumain (Soul Syndicate)

Appended 2026-05-27 ~15:30 PDT in response to his iMessage thread questions on M1.

George's questions, answered with data

Answer 1: are you seeing any sales from George's 66 clicks?

No conversions are attributable to Soul Syndicate / Everflow traffic in the last 22 days. The Supabase affiliate_postbacks table shows three rows total in its entire history, all dated 2026-05-05:

UTC timestamp	Subid (sent to Everflow as transaction_id)	Order	Amount	Upstream	Verdict
2026-05-05 02:32:05	{transaction_id}	085e7272…	$39.20	HTTP 204	Literal placeholder — unmatchable in Everflow
2026-05-05 02:46:52	{transaction_id}	875b2ff9…	$39.20	HTTP 204	Literal placeholder — unmatchable in Everflow
2026-05-05 03:09:18	5d34e49eae6d4d658c375eb4fb4fa55f	be0c382e… (georgeroumain@gmail.com, $49 Reishi to Thousand Oaks)	$49.00	HTTP 200 SUCCESS	Genuine conversion — George's own QA self-test

The one successful, properly-matched conversion (row 3) was George's own self-test order on 2026-05-06. The other two rows on 2026-05-05 morning were real customer purchases where Everflow's tracking template failed to substitute the click's {transaction_id} macro — the user landed on Frequency with the literal string {transaction_id} in the URL, Frequency captured it as-is into the ss_subid cookie, and the postback fired with that literal string. Everflow accepted (HTTP 204) but could not bind the conversion to any click in its database, so those two orders are orphaned on the Everflow side. Frequency-side audit trail is complete; recovery is possible if you have the underlying click times.

Answer 2: can we map sales to IP addresses?

Currently: no. Frequency’s order attribution payload does not capture client IP server-side. Inspection of store_orders.attribution_payload on a recent order shows only these keys:

{
  "fbp": "fb.1.1779924272374.780044347",
  "referrer": "https://www.google.com/",
  "updatedAt": "2026-05-27T23:24:32.373Z",
  "firstSeenAt": "2026-05-27T23:24:32.373Z",
  "landingPath": "/?srsltid=AfmBOoq2A5SD8gXpOX74hI5NBAFCKq7XGLvA07XwGDjXoVb1cxPOFpcq"
}

No ip field is being persisted. This is true for every recent order, not just affiliate traffic. The attribution_context column is also null on recent orders, and PayPal’s payload doesn’t include the client IP for Authorize.Net flows. So IP-based click…sale matching is not currently possible with what we capture.

Last 48 hours — order-level data with empty IP confirmation

To make the gap visible: every order in the reporting period has a null IP across all three JSON sources.

Created (UTC)	Customer	City / State	Amount	attr_ip	ctx_ip	paypal_ip	UTM source
2026-05-28 05:20	Kim Sherman	Huntington Beach, CA	$121.00	null	null	null	(none)
2026-05-28 04:54	Stella Shahangian	Los Angeles, CA	$126.00	null	null	null	(none)
2026-05-27 23:31	Gregg Barcan	Hopewell, NJ	$233.00	null	null	null	(none)
2026-05-27 11:32	Josef Nemec	Tega Cay, SC	$288.00	null	null	null	(none)
2026-05-26 23:37	Rebecca Fallon	Davidson, NC	$301.50	null	null	null	(none)
2026-05-26 01:04	Eirika Edwardsen	Chicago, IL	$191.00	null	null	null	klaviyo
2026-05-26 00:02	Alan Safdiah	Bal Harbour, FL	$126.00	null	null	null	(none)
2026-05-25 23:54	Brooke Whitford	Lake Worth, FL	$209.00	null	null	null	(none)
2026-05-25 00:57	Crystal Boultinghouse	La Cañada Flintridge, CA	$612.00	null	null	null	(none)

Query: SELECT id, created_at, payer_email, attribution_payload->>'ip' AS attr_ip, attribution_context->>'ip' AS ctx_ip, paypal_payload->>'ip' AS paypal_ip, … FROM store_orders WHERE created_at > NOW() - INTERVAL '48 hours' — Supabase MCP, 2026-05-27 ~15:30 PDT.

Answer 3: George’s 66 clicks — where are they?

The 66 clicks happened on George’s side (Everflow click counter). Frequency’s SoulSyndicateTracker only fires on a Frequency page-load, so a click counted in Everflow but not landing on a Frequency URL never reaches us. Three explanations are likely, in order:

1. Tracking template substitution is broken on at least some links. The two literal {transaction_id} rows above are direct evidence: at least some Everflow click links sent users to Frequency with un-substituted macros. Those users did land on Frequency, the tracker did capture them — but as the literal string, not as a real click ID. We have no way to tell which of George’s 66 clicks reached us if the click ID never substituted.
2. Some clicks may bounce before any page tracker runs. Pre-rendered redirects, ad blockers on the click hop, or JavaScript-disabled landings would never trigger the cookie write.
3. Some clicks may convert via different attribution paths. If a user clicked George’s link, bounced, then came back later via a Klaviyo email or organic Google search, the conversion would attribute to the second source. With no IP capture, we can’t cross-reference.

Recommended next steps

Owner	Action	Why
George	Click one of his own current Everflow links in a clean browser. Screenshot the final landing URL.	If it shows ?subid={transaction_id} as a literal, his tracking template substitution is still broken — that’s where the 66 clicks are being lost.
George	Confirm the destination URL pattern he's distributing matches the canonical product matrix in docs/SOUL-SYNDICATE-EVERFLOW-ATTRIBUTION.md (e.g. frequencycaps.com/store/calm-dose?utm_source=soulsyndicate&utm_medium=affiliate&utm_campaign=everflow&subid={transaction_id}).	Zero of last 30 days of Frequency orders carry utm_source=soulsyndicate or utm_campaign=everflow. Either no real traffic is landing, or his links don’t include the canonical UTMs.
Frequency	Add server-side IP capture into attribution_payload.ip on order creation. One line in the order-creation server route; reads x-forwarded-for / x-real-ip from request headers.	Closes the gap George flagged. Without this, IP-based click…conversion matching is impossible regardless of which affiliate is asking.
Frequency	Retroactively credit George in Everflow for the two orphaned 2026-05-05 conversions (orders 085e7272… and 875b2ff9…, both $39.20), if he confirms they were his traffic.	Frequency has full audit-trail evidence those conversions came through the Soul Syndicate cookie path; Everflow just couldn’t match them due to the template substitution bug. Manual credit is justified.
Frequency	Confirm SOUL_SYNDICATE_EVERFLOW_POSTBACK_URL in Vercel production env points at the correct Everflow tracking domain. Live end-to-end test on 2026-05-27 15:29 PDT returned {"status":"sent","upstream_status":204}, so the URL works — just confirm the domain matches what George expects.	Defensive: the env var was set 23 days ago and hasn’t been touched since; worth a sanity check.

Provenance — what was checked, with timestamps

• Live end-to-end synthetic postback test on https://frequencycaps.com/api/tracking/soul-syndicate/postback — 2026-05-27 15:29 PDT — response {"status":"sent","dedup_key":"probe-1779920955","upstream_status":204}.
• Supabase affiliate_postbacks table, all rows for network='soul_syndicate' — 3 rows, all 2026-05-05.
• Supabase store_orders, 30-day attribution scan — 0 rows with utm_source='soulsyndicate', utm_campaign='everflow', tapfiliate_click_id, or affiliate_id.
• Supabase store_orders.attribution_payload JSONB inspection — no ip key on any of the 9 orders from reporting period.
• M1 (Mathieu's MacBook) ~/Library/Messages/chat.db — iMessage thread with +18057320209 queried via sqlite3; the three quoted messages above are verbatim.
• ShipStation shipment record analysis/session-artifacts/2026-05-18/3-machine-sync/markm4-unique/analysis/session-artifacts/2026-05-17/raw/03-ship-recipient-George.json — confirms George Roumain ships to 1434 CALLE COLINA, Thousand Oaks, CA 91360 (in 805 area code), email georgeroumain@gmail.com.