queke

Thanks for checking. I can't be the only one with this issue.

Here is a breakdown from chatgpt:

• Since May 18, counting only CB revshare_signup-referral rows with attempt: 1, excluding sales and the test postback:

Date signup rows unique signups duplicate sends duplicate send rate
May 18 32 30 2 6.3%
May 19 34 30 4 11.8%
May 20 21 20 1 4.8%
May 21 25 20 5 20.0%
May 22 32 25 7 21.9%
May 23* 12 9 3 25.0%

Total:

156 signup postbacks
134 unique signup events after exact de-dupe
22 duplicate first-attempt sends
14.1% duplicate-send rate

All of those duplicates are exact x2 sends with the same user_uid, same id/checksum, and still attempt: 1. May 23 is partial through 07:30 AM in the pasted log.

Also missing country codes:

• I’m keeping the same scope as the last breakdown: May 18 onward, signup-referral JSON rows only, attempt: 1, excluding sales and the test postback. I’ll separate raw postbacks
from exact de-duped signup events so the duplicate sends do not hide the real missing-code count.

• Using country_code: "" as missing, since May 18:

Date signup rows missing country rows unique missing signups missing duplicate sends
May 18 32 3 2 1
May 19 34 10 9 1
May 20 21 8 7 1
May 21 25 6 5 1
May 22 32 2 2 0
May 23* 12 1 1 0

Totals since May 18:

156 signup postbacks
30 signup postbacks had missing country_code
26 unique signups had missing country_code
4 of the missing-country rows were duplicate sends

Missing-country rate:

Raw postback rate: 30 / 156 = 19.2%
Unique signup rate: 26 / 134 = 19.4%

May 23 is partial through 07:30 AM in the pasted log.

I have had duplicate postbacks in the past but they would always say Attempt 2, 3, etc. I get there can be issues with postbacks but also counting 1 signup as 2 on the stats page? That seems really bad.