Daily campaign report — 2026-08-17, against 2026-08-16

Three of the four ad accounts delivered on 2026-08-17 and spent $702.70 between them against $708.97 the day before. B1 took $496.36, the two shared Nomad Node accounts $183.98 and KBM1 $22.36; HR1 was built and still did not deliver. The portfolio spent 0.9% less, bought a quarter fewer registrations, and sealed 30.3% more revenue inside the day. Definitions, the report clock and the three revenue measures are in the appendix.

1Overview

(i) The portfolio, both days.

2026-08-162026-08-17change
spend$708.97$702.70−0.9%
impressions101,49392,029−9.3%
CPM$6.99$7.64+9.3%
registrations (ours)1,3611,027−24.5%
cost per registration$0.521$0.684+31.3%
booked$1,869.11 (2.64)$1,860.31 (2.65)−0.5%
within-day$578.01 (0.82)$753.18 (1.07)+30.3%
cohort @ 24h$740.86 (1.04)$881.43 (1.25)+19.0%
booked payers133153+20
payer rate (d0)4.7%—
ARPU (d0)$0.5444—
ARPPU (d0)$11.58—

Cohort value — ARPU and ARPPU at d0, d3 and d7

Keyed on the INSTALL day and measured from each user's own install stamp: dN is their first (N+1) x 24 h. ARPU is Adjust's own series, the one the partner's dashboard reports; ARPPU is our payment ledger, because Adjust exposes no cumulative distinct-payer count. A horizon the window has not lived through yet is left empty rather than written as zero.

appARPU (d0)ARPU (d3)ARPU (d7)ARPPU (d0)ARPPU (d3)ARPPU (d7)installs
Vloom$0.9336$1.0565$1.5019$12.69$13.76$17.83938
Sinai AI$0.0831$0.1661$0.1661———36

(ii) Every account side by side, on one table. 2026-08-16 first, then 2026-08-17. This is the table the accounts are compared against each other on.

2026-08-16

accountspendshareimpressionsCPMregistrationscost/regbooked (bROAS)within-day (wROAS)cohort@24h (cROAS)payerspayer%ARPUARPPU
Portfolio$708.97100%101,493$6.991,361$0.521$1,869.11 (2.64)$578.01 (0.82)$740.86 (1.04)1339.8%$1.373$14.05
B1$484.5768%59,005$8.21825$0.587$1,316.94 (2.72)$261.02 (0.54)$277.13 (0.57)9111.0%$1.596$14.47
Nomad Node$190.5027%42,216$4.51529$0.360$552.17 (2.90)$316.99 (1.66)$463.74 (2.43)427.9%$1.044$13.15
KBM1$33.905%272$124.637$4.843$0.00 (0.00)$0.00 (0.00)$0.00 (0.00)00.0%$0.000—
HR1$0.000%0—0—$0.00$0.00$0.000———

2026-08-17

accountspendshareimpressionsCPMregistrationscost/regbooked (bROAS)within-day (wROAS)cohort@24h (cROAS)payerspayer%ARPUARPPU
Portfolio$702.70100%92,029$7.641,027$0.684$1,860.31 (2.65)$753.18 (1.07)$881.43 (1.25)15314.9%$1.811$12.16
B1$496.3671%57,136$8.69678$0.732$1,341.06 (2.70)$539.29 (1.09)$650.98 (1.31)11116.4%$1.978$12.08
Nomad Node$183.9826%34,639$5.31345$0.533$519.25 (2.82)$213.89 (1.16)$230.44 (1.25)4212.2%$1.505$12.36
KBM1$22.363%254$88.034$5.590$0.00 (0.00)$0.00 (0.00)$0.00 (0.00)00.0%$0.000—
HR1$0.000%0—0—$0.00$0.00$0.000———

(iii) The same table, once per account. Same rows, same columns, same two days.

B1

2026-08-162026-08-17change
spend$484.57$496.36+2.4%
impressions59,00557,136−3.2%
CPM$8.21$8.69+5.8%
registrations (ours)825678−17.8%
cost per registration$0.587$0.732+24.7%
booked$1,316.94 (2.72)$1,341.06 (2.70)+1.8%
within-day$261.02 (0.54)$539.29 (1.09)+106.6%
cohort @ 24h$277.13 (0.57)$650.98 (1.31)+134.9%
booked payers91111+20
payer rate11.0%16.4%+5.4 pts
ARPU$1.596$1.978+23.9%
ARPPU$14.47$12.08−16.5%

Nomad Node

2026-08-162026-08-17change
spend$190.50$183.98−3.4%
impressions42,21634,639−17.9%
CPM$4.51$5.31+17.7%
registrations (ours)529345−34.8%
cost per registration$0.360$0.533+48.1%
booked$552.17 (2.90)$519.25 (2.82)−6.0%
within-day$316.99 (1.66)$213.89 (1.16)−32.5%
cohort @ 24h$463.74 (2.43)$230.44 (1.25)−50.3%
booked payers4242+0
payer rate (d0)5.9%—
ARPU (d0)$0.8766—
ARPPU (d0)$14.96—

KBM1

2026-08-162026-08-17change
spend$33.90$22.36−34.0%
impressions272254−6.6%
CPM$124.63$88.03−29.4%
registrations (ours)74−42.9%
cost per registration$4.843$5.590+15.4%
booked$0.00 (0.00)$0.00 (0.00)—
within-day$0.00 (0.00)$0.00 (0.00)—
cohort @ 24h$0.00 (0.00)$0.00 (0.00)—
booked payers00+0
payer rate (d0)0.0%—
ARPU (d0)$0.0000—
ARPPU (d0)$0.00—

HR1

2026-08-162026-08-17change
spend$0.00$0.00—
impressions00—
CPM———
registrations (ours)00—
cost per registration———
booked$0.00$0.00—
within-day$0.00$0.00—
cohort @ 24h$0.00$0.00—
booked payers00+0
payer rate———
ARPU———
ARPPU———

Campaign spend split inside B1: Worldwide 100% on 08-16 and 08-17 alike. Sections 2 to 6 carry no campaign mix change.

A quarter of the registrations disappeared and revenue went up. Registrations −24.5% on 0.9% less money, within-day +30.3%, payer rate 9.8% → 14.9%, ARPU +31.9%.

The fall hits both delivering accounts. B1 825 → 678, the shared buy 529 → 345; Meta's install count fell 15.3% against our 17.8%.

B1 and the shared buy have converged. Within-day 1.09 and 1.16 against 0.54 and 1.66: yesterday's three-fold gap is inside what these payer counts resolve.

KBM1 has now gone two days without a payer. $22.36 on this UTC day against $33.90, four registrations against seven, $5.590 a registration, CPM $88.03.

2Hourly, 2026-08-17

(i) The portfolio, hour by hour. Every account placeable on the report clock, summed; delivery on the delivery hour, our columns on the hour the appendix names.

hrspendimpressionsCPMregistrationscost/regbookedbROASwithin-daywROAScohort@24hcROASbooked payers
00$20.712,823$7.3424$0.863$72.463.50$9.110.44$9.110.446
01$24.893,209$7.7632$0.778$39.911.60$40.751.64$40.751.644
02$27.303,688$7.4033$0.827$122.344.48$39.981.46$39.981.467
03$29.143,755$7.7632$0.911$88.023.02$74.542.56$74.542.567
04$28.204,120$6.8445$0.627$123.054.36$9.980.35$9.980.3513
05$32.235,179$6.2241$0.786$47.051.46$47.031.46$47.031.468
06$28.894,743$6.0938$0.760$62.352.16$17.290.60$17.290.609
07$36.544,850$7.5341$0.891$54.441.49$23.580.65$27.140.747
08$31.064,233$7.3448$0.647$54.571.76$15.360.49$15.360.4911
09$28.323,939$7.1950$0.566$67.772.39$27.110.96$27.110.966
10$28.004,272$6.5546$0.609$40.141.43$4.990.18$4.990.187
11$26.913,491$7.7138$0.708$48.461.80$5.740.21$5.740.214
12$26.503,573$7.4253$0.500$66.692.52$41.411.56$41.411.565
13$38.534,125$9.3440$0.963$118.133.07$64.611.68$64.611.688
14$27.852,304$12.0943$0.648$60.282.16$30.601.10$36.361.3111
15$29.503,943$7.4851$0.578$29.971.02$25.150.85$25.150.854
16$30.033,891$7.7251$0.589$59.841.99$16.500.55$16.500.5513
17$31.323,920$7.9949$0.639$106.943.41$44.311.41$114.303.6514
18$34.804,087$8.5157$0.611$87.012.50$17.230.49$44.921.2911
19$31.363,759$8.3450$0.627$101.433.23$9.890.32$9.890.3212
20$25.683,319$7.7436$0.713$66.862.60$54.962.14$54.962.147
21$27.853,278$8.5049$0.568$129.094.64$45.891.65$62.152.2311
22$22.533,415$6.6038$0.593$56.142.49$5.170.23$5.170.236
23$34.564,113$8.4042$0.823$157.364.55$82.002.37$86.992.529

Absent from the table above, by name: HR1. Left out only when it cannot be placed on the report clock; its money is still in every day-grain table.

(ii) The same 24 hours per account. B1's block is the wide one, because only its export carries clicks, CTR and Meta's installs; the others carry what every preset ships.

B1 — $496.36 on this day, and the only account whose hours can be read as a funnel

hrspendimpressionsCPMclicksCTRinstallsclick→installCPIregistrationscoveragebookedbROASwithin-daywROAScohort@24hcROASbooked payers
00$15.021,647$9.12774.68%1114.3%$1.36515100%$11.560.77$0.000.00$0.000.002
01$15.111,875$8.061035.49%1817.5%$0.83921100%$12.880.85$40.752.70$40.752.701
02$19.292,144$9.001205.60%1915.8%$1.01522100%$89.074.62$34.991.81$34.991.814
03$20.942,322$9.021144.91%1311.4%$1.61120100%$40.781.95$23.161.11$23.161.113
04$19.842,326$8.531195.12%1916.0%$1.04428100%$77.023.88$9.980.50$9.980.506
05$22.353,143$7.111665.28%2515.1%$0.89428100%$25.861.16$29.401.32$29.401.325
06$19.622,954$6.641434.84%139.1%$1.50924100%$48.602.48$17.290.88$17.290.886
07$24.893,029$8.221765.81%2313.1%$1.08226100%$15.020.60$5.740.23$9.300.373
08$22.172,598$8.531325.08%2216.7%$1.00832100%$38.191.72$15.360.69$15.360.698
09$19.822,373$8.351275.35%2318.1%$0.86227100%$32.431.64$27.111.37$27.111.374
10$20.122,767$7.271425.13%2014.1%$1.00627100%$31.401.56$4.990.25$4.990.255
11$18.102,157$8.391125.19%1816.1%$1.00625100%$42.752.36$5.740.32$5.740.323
12$17.792,252$7.901426.31%2517.6%$0.71238100%$66.693.75$41.412.33$41.412.335
13$25.152,679$9.391736.46%137.5%$1.93527100%$110.154.38$59.622.37$59.622.376
14$20.461,506$13.591218.03%1915.7%$1.07727100%$44.452.17$30.601.50$36.361.787
15$22.882,601$8.801555.96%2516.1%$0.91533100%$24.211.06$11.930.52$11.930.523
16$23.752,698$8.801515.60%2717.9%$0.88034100%$47.972.02$16.500.69$16.500.6910
17$23.852,762$8.641696.12%2514.8%$0.95432100%$84.403.54$40.751.71$110.744.649
18$24.842,689$9.241716.36%2715.8%$0.92037100%$83.833.37$11.470.46$20.420.8210
19$23.112,285$10.111617.05%2716.8%$0.85630100%$59.742.59$9.890.43$9.890.437
20$18.881,960$9.631045.31%1615.4%$1.18023100%$16.580.88$11.230.59$11.230.594
21$18.381,910$9.621095.71%1715.6%$1.08126100%$109.575.96$5.630.31$8.900.488
22$16.252,015$8.061286.35%118.6%$1.47721100%$31.841.96$5.170.32$5.170.324
23$23.752,444$9.721245.07%2116.9%$1.13128100%$133.595.62$77.013.24$82.003.455
ALL$496.3657,136$8.693,2395.67%47714.7%$1.041651100%$1278.602.58$535.731.08$632.241.27102

Delivery columns (CPM, CTR, click→install, CPI) are Meta's: numerator and denominator both from its instrument. Registrations, the payer count and every revenue column are ours. The two install counts are never crossed. booked sits on the payment hour; within-day and cohort@24h sit on the install hour.

⚠ The coverage column reads 100% on every hour. Every install on this day has lived a full 24 hours, so the cohort column is frozen end to end and no hour on it can rise further.

⚠ Payer counts per hour are single digits and every bucket sits under the 16-payer bar. An hourly ROAS on two payers is those two baskets. Read the ALL row for level and the hours for shape.

2026-08-18T18:23:07.509057 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 0 3 6 9 12 15 18 21 hour (UTC) 0 5 10 15 20 25 USD Spend by hour 0 3 6 9 12 15 18 21 hour (UTC) 1500 1750 2000 2250 2500 2750 3000 impressions Impressions and installs by hour impressions installs 12 14 16 18 20 22 24 26 installs (Meta Leads) The day's motion — whole account, 2026-08-17 (UTC)
The day's motion: spend by hour, and impressions against installs
2026-08-18T18:23:07.644049 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 0 4 8 12 16 20 hour (UTC) 5.0 5.5 6.0 6.5 7.0 7.5 8.0 CTR % CTR 0 4 8 12 16 20 hour (UTC) 7 8 9 10 11 12 13 USD per 1,000 impressions CPM 0 4 8 12 16 20 hour (UTC) 8 10 12 14 16 18 installs / clicks % Click → install 0 4 8 12 16 20 hour (UTC) 0.8 1.0 1.2 1.4 1.6 1.8 USD Cost per install Delivery by hour — whole account, 2026-08-17 (UTC)
CTR, CPM, click-to-install and CPI by hour, whole account

The other accounts, hour by hour.

Nomad Node — $183.98 on this day

hrspendimpressionsCPMregistrationscost/regbookedbROASwithin-daywROAScohort@24hcROASbooked payers
00$5.541,170$4.749$0.616$60.8910.99$9.111.64$9.111.644
01$8.141,316$6.199$0.904$21.332.62$0.000.00$0.000.002
02$6.711,526$4.4010$0.671$33.264.96$4.990.74$4.990.743
03$6.261,418$4.4113$0.482$47.237.55$51.388.21$51.388.214
04$8.131,786$4.5516$0.508$19.382.38$0.000.00$0.000.004
05$9.512,027$4.6913$0.732$21.182.23$17.631.85$17.631.853
06$9.071,785$5.0812$0.756$13.751.52$0.000.00$0.000.003
07$9.731,804$5.3914$0.695$39.424.05$17.841.83$17.841.834
08$8.151,630$5.0015$0.543$16.382.01$0.000.00$0.000.003
09$8.161,558$5.2421$0.389$35.344.33$0.000.00$0.000.002
10$6.951,490$4.6618$0.386$2.990.43$0.000.00$0.000.001
11$7.251,314$5.5213$0.558$0.000.00$0.000.00$0.000.000
12$7.481,306$5.7316$0.468$0.000.00$0.000.00$0.000.000
13$9.341,420$6.5812$0.778$7.980.85$4.990.53$4.990.532
14$7.03789$8.9114$0.502$15.832.25$0.000.00$0.000.004
15$6.381,335$4.7814$0.456$0.000.00$13.222.07$13.222.070
16$5.351,167$4.5816$0.334$11.872.22$0.000.00$0.000.003
17$7.471,158$6.4515$0.498$15.432.07$0.000.00$0.000.003
18$9.961,398$7.1215$0.664$3.180.32$5.760.58$9.320.941
19$8.251,474$5.6016$0.516$35.934.36$0.000.00$0.000.004
20$6.801,359$5.0013$0.523$50.287.39$43.736.43$43.736.433
21$9.471,368$6.9222$0.430$19.522.06$40.264.25$53.255.623
22$6.281,400$4.4915$0.419$24.303.87$0.000.00$0.000.002
23$6.571,641$4.0014$0.469$23.773.62$4.990.76$4.990.764

KBM1 — $22.36 on this day

hrspendimpressionsCPMregistrationscost/regbookedbROASwithin-daywROAScohort@24hcROASbooked payers
00$0.156$25.000—$0.000.00$0.000.00$0.000.000
01$1.6418$91.110—$0.000.00$0.000.00$0.000.000
02$1.3018$72.221$1.300$0.000.00$0.000.00$0.000.000
03$1.9415$129.330—$0.000.00$0.000.00$0.000.000
04$0.238$28.750—$0.000.00$0.000.00$0.000.000
05$0.379$41.110—$0.000.00$0.000.00$0.000.000
06$0.204$50.000—$0.000.00$0.000.00$0.000.000
07$1.9217$112.940—$0.000.00$0.000.00$0.000.000
08$0.745$148.001$0.740$0.000.00$0.000.00$0.000.000
09$0.348$42.500—$0.000.00$0.000.00$0.000.000
10$0.9315$62.001$0.930$0.000.00$0.000.00$0.000.000
11$1.5620$78.000—$0.000.00$0.000.00$0.000.000
12$1.2315$82.001$1.230$0.000.00$0.000.00$0.000.000
13$4.0426$155.380—$0.000.00$0.000.00$0.000.000
14$0.369$40.000—$0.000.00$0.000.00$0.000.000
15$0.247$34.290—$0.000.00$0.000.00$0.000.000
16$0.9326$35.770—$0.000.00$0.000.00$0.000.000
17$0.000—0—$0.00—$0.00—$0.00—0
18$0.000—0—$0.00—$0.00—$0.00—0
19$0.000—0—$0.00—$0.00—$0.00—0
20$0.000—0—$0.00—$0.00—$0.00—0
21$0.000—0—$0.00—$0.00—$0.00—0
22$0.000—0—$0.00—$0.00—$0.00—0
23$4.2428$151.430—$0.000.00$0.000.00$0.000.000

HR1 — no hourly block: it delivered nothing on this day. Its export returned No data available, a measured zero, and the zero row is in the day-grain tables.

Against the prior day, hour matched to hour

Hours both days delivered in, on the UTC clock: 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23. Only the shared hours are compared.

Counting which way each shared hour points, which needs no weighting and asks only for a direction:

metrichours 2026-08-17 ran higherhours it ran lowersign test
CPM19 of 245 of 24p = 0.007
CTR5 of 2419 of 24p = 0.007
click→install11 of 2413 of 24p = 0.839
CPI17 of 247 of 24p = 0.064

A sign test throws magnitude away and buys weight-free direction with it.

Both directional ratios are impression-side. CPM 19 of 24 higher, CTR 19 of 24 lower, p = 0.007; click→install 11 against 13, p = 0.839.

Paid more for a weaker impression, converted it the same. Unlike 08-16, the CTR loss is not bought back: installs 477 against 563, CPI +20.9%.

The full hour-by-hour pairing, 2026-08-16 → 2026-08-17

Every shared hour, 2026-08-16 → 2026-08-17. All columns are Meta's instrument on both sides of each ratio. Revenue is deliberately absent: per-hour payer counts run 0-3, so an hourly revenue column would be one person's basket read as a rate.

hrimpressionsCPMCTRclick→installCPI
001,375 → 1,6477.94 → 9.126.91% → 4.68%11.6% → 14.3%0.993 → 1.365
011,479 → 1,8758.58 → 8.065.61% → 5.49%15.7% → 17.5%0.976 → 0.839
021,128 → 2,1447.09 → 9.006.03% → 5.60%23.5% → 15.8%0.500 → 1.015
031,314 → 2,3228.94 → 9.027.53% → 4.91%13.1% → 11.4%0.904 → 1.611
041,519 → 2,3267.14 → 8.536.19% → 5.12%19.1% → 16.0%0.602 → 1.044
051,378 → 3,1436.39 → 7.115.88% → 5.28%14.8% → 15.1%0.734 → 0.894
062,288 → 2,9545.94 → 6.646.42% → 4.84%10.2% → 9.1%0.906 → 1.509
073,816 → 3,0296.82 → 8.226.00% → 5.81%17.0% → 13.1%0.667 → 1.082
083,008 → 2,5986.93 → 8.534.99% → 5.08%12.0% → 16.7%1.158 → 1.008
093,014 → 2,3738.12 → 8.356.24% → 5.35%11.7% → 18.1%1.112 → 0.862
103,282 → 2,7677.15 → 7.276.58% → 5.13%17.1% → 14.1%0.634 → 1.006
113,352 → 2,1577.05 → 8.396.00% → 5.19%13.9% → 16.1%0.844 → 1.006
123,268 → 2,2528.70 → 7.905.81% → 6.31%15.8% → 17.6%0.948 → 0.712
132,949 → 2,6798.09 → 9.395.76% → 6.46%16.5% → 7.5%0.852 → 1.935
141,464 → 1,50611.60 → 13.598.33% → 8.03%20.5% → 15.7%0.679 → 1.077
152,955 → 2,6018.80 → 8.806.23% → 5.96%16.3% → 16.1%0.866 → 0.915
163,060 → 2,6988.25 → 8.806.14% → 5.60%14.9% → 17.9%0.902 → 0.880
173,283 → 2,7628.50 → 8.646.94% → 6.12%12.7% → 14.8%0.962 → 0.954
182,983 → 2,6898.13 → 9.246.40% → 6.36%16.2% → 15.8%0.783 → 0.920
192,907 → 2,28511.39 → 10.116.16% → 7.05%12.3% → 16.8%1.505 → 0.856
202,579 → 1,9607.74 → 9.635.58% → 5.31%13.9% → 15.4%0.998 → 1.180
212,348 → 1,91010.01 → 9.626.18% → 5.71%20.0% → 15.6%0.811 → 1.081
222,380 → 2,0159.78 → 8.065.46% → 6.35%20.0% → 8.6%0.895 → 1.477
231,876 → 2,4449.07 → 9.725.97% → 5.07%20.5% → 16.9%0.740 → 1.131
2026-08-18T18:23:07.800684 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 0 5 10 15 20 hour (UTC) 4.5 5.0 5.5 6.0 6.5 7.0 7.5 8.0 8.5 CTR % CTR 2026-08-16 2026-08-17 0 5 10 15 20 hour (UTC) 6 7 8 9 10 11 12 13 USD per 1,000 impressions CPM 0 5 10 15 20 hour (UTC) 8 10 12 14 16 18 20 22 24 installs / clicks % Click → install 0 5 10 15 20 hour (UTC) 0.6 0.8 1.0 1.2 1.4 1.6 1.8 2.0 USD Cost per install Delivery by hour — 2026-08-17 against 2026-08-16, shared hours only (UTC)
The same four ratios with the prior day laid over the day, shared hours only

3Country, 2026-08-17

2026-08-23T12:43:22.184807 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ US IN MX TR GB ID PH MY IT CA AR FR 0 20 40 60 80 100 120 USD delivery raked onto the report clock against two measured margins; revenue is the report day Spend against within-day revenue by country — 2026-08-17 spend within-day revenue
Spend against within-day revenue, by country
2026-08-23T12:43:22.232846 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ −0.04 −0.02 0.00 0.02 0.04 USD per install Cost per install by country — 2026-08-17 (report clock)
Cost per install by country

(i) The portfolio by country, 2026-08-17. On the report clock. Meta serves no hour x country grid, so each country cut is raked from its own Meta day onto UTC; our own columns were already there.

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
US$108.3621.1%3,809$28.4569$1.570$117.901.0922
IN$91.9317.9%10,001$9.19228$0.403$121.231.3238
MX$20.834.1%4,540$4.5947$0.443$14.820.717
TR$20.564.0%817$25.1833$0.623$10.900.534
GB$20.474.0%1,359$15.0628$0.731$21.741.066
ID$17.663.4%2,932$6.0260$0.294$9.980.562
PH$14.992.9%8,020$1.8758$0.258$5.630.384
MY$13.362.6%2,625$5.0927$0.495$10.760.816
IT$10.832.1%717$15.1116$0.677$6.320.581
CA$10.302.0%676$15.2516$0.644$89.128.653
AR$9.101.8%1,124$8.1025$0.364$15.961.754
FR$8.641.7%721$11.9815$0.576$5.740.672

186 further countries are not listed, $165.93 between them (32.3% of this block).

Reconciliation, what is measured and what is fitted. Every per-country cell is an allocation across hours; every total is measured. B1 (UTC-7) $132.17 from Meta 2026-08-16 and $364.28 from Meta 2026-08-17, a measured UTC-day total of $496.45; KBM1 (UTC-7) $16.53 from Meta 2026-08-17, a measured UTC-day total of $16.53. Meta days this run did not pull were taken from the country archive at ad_ops/_data/country_archive/ — KBM1 Meta 2026-08-17 — because a UTC-7 day reaches back into the Meta day before it and the run window did not.

Absent from the table above, by name: HR1. Their spend is in every day-grain table; only their country split is missing.

(ii) The same cut per account, 2026-08-17.

B1

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
IN$91.9318.5%10,001$9.19167$0.550$103.961.1330
US$91.8318.5%3,633$25.2850$1.837$107.921.1817
MX$20.834.2%4,540$4.5930$0.694$5.710.275
TR$20.564.1%817$25.1818$1.142$5.890.292
GB$20.474.1%1,359$15.0625$0.819$21.741.066
ID$17.663.6%2,932$6.0229$0.609$9.980.562
PH$14.993.0%8,020$1.8739$0.384$5.630.384
MY$13.362.7%2,625$5.0922$0.607$10.760.814
IT$10.832.2%717$15.1113$0.833$6.320.581
CA$10.302.1%676$15.2511$0.937$71.316.922
AR$9.101.8%1,124$8.1015$0.607$10.971.202
FR$8.641.7%721$11.9810$0.864$5.740.672

184 further countries are not listed, $165.93 between them (33.4% of this block).

Nomad Node

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
AE$0.000.0%0—1$0.000$0.00—0
AR$0.000.0%0—10$0.000$4.99—2
AT$0.000.0%0—1$0.000$0.00—0
AU$0.000.0%0—0—$0.00—1
AZ$0.000.0%0—2$0.000$10.97—1
BE$0.000.0%0—3$0.000$6.32—1
BG$0.000.0%0—1$0.000$0.00—0
BO$0.000.0%0—1$0.000$0.00—0
BR$0.000.0%0—26$0.000$13.22—3
CA$0.000.0%0—5$0.000$17.82—1
CL$0.000.0%0—3$0.000$0.00—1
CO$0.000.0%0—6$0.000$0.00—0

58 further countries are not listed, $0.00 between them (0.0% of this block).

KBM1

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
US$16.53100.0%176$93.924$4.133$0.000.000

HR1 — no country block: it delivered nothing on this day, a measured zero.

The prior day, 2026-08-16, the same two tables.

(i) The portfolio by country, 2026-08-16. On the report clock. Meta serves no hour x country grid, so each country cut is raked from its own Meta day onto UTC; our own columns were already there.

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
US$83.7017.3%3,536$23.6776$1.101$91.881.1020
IN$80.9916.7%9,891$8.19245$0.331$155.051.9127
GB$24.215.0%1,476$16.4035$0.692$12.080.505
MX$21.074.3%4,345$4.8562$0.340$35.811.706
ID$17.683.6%3,536$5.00108$0.164$4.990.283
PH$15.053.1%7,364$2.0464$0.235$0.000.002
TR$14.172.9%876$16.1937$0.383$11.780.834
FR$11.332.3%833$13.6122$0.515$5.740.511
CA$10.912.3%575$18.9611$0.992$35.653.271
MY$10.552.2%2,424$4.3527$0.391$5.380.512
AR$9.201.9%1,158$7.9540$0.230$4.990.541
IT$9.141.9%662$13.809$1.015$0.000.003

185 further countries are not listed, $176.57 between them (36.4% of this block).

Reconciliation, what is measured and what is fitted. Every per-country cell is an allocation across hours; every total is measured. B1 (UTC-7) $76.60 from Meta 2026-08-15 and $407.97 from Meta 2026-08-16, a measured UTC-day total of $484.57.

Absent from the table above, by name: KBM1, HR1. Their spend is in every day-grain table; only their country split is missing.

(ii) The same cut per account, 2026-08-16.

B1

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
US$83.7017.3%3,536$23.6764$1.308$86.891.0418
IN$80.9916.7%9,891$8.19166$0.488$67.940.8415
GB$24.215.0%1,476$16.4027$0.897$0.000.003
MX$21.074.3%4,345$4.8534$0.620$14.820.705
ID$17.683.6%3,536$5.0044$0.402$0.000.002
PH$15.053.1%7,364$2.0450$0.301$0.000.002
TR$14.172.9%876$16.1922$0.644$5.890.421
FR$11.332.3%833$13.6117$0.667$5.740.511
CA$10.912.3%575$18.9610$1.091$0.000.000
MY$10.552.2%2,424$4.3518$0.586$5.380.511
AR$9.201.9%1,158$7.9525$0.368$0.000.000
IT$9.141.9%662$13.808$1.142$0.000.003

184 further countries are not listed, $176.57 between them (36.4% of this block).

Nomad Node

ccspendshareimpressionsCPMregistrations (ours)cost/regwithin-daywROASpayers
AE$0.000.0%0—6$0.000$0.00—0
AL$0.000.0%0—1$0.000$0.00—0
AM$0.000.0%0—0—$0.00—1
AR$0.000.0%0—15$0.000$4.99—1
AU$0.000.0%0—3$0.000$28.67—1
AZ$0.000.0%0—3$0.000$0.00—0
BA$0.000.0%0—1$0.000$0.00—0
BD$0.000.0%0—2$0.000$0.00—0
BG$0.000.0%0—1$0.000$5.74—1
BN$0.000.0%0—1$0.000$0.00—0
BO$0.000.0%0—3$0.000$0.00—0
BR$0.000.0%0—38$0.000$0.00—0

70 further countries are not listed, $0.00 between them (0.0% of this block).

KBM1 — no country block: it delivered nothing on this day, a measured zero.

HR1 — no country block: it delivered nothing on this day, a measured zero.

4Aggregate, both days

(i) The delivery funnel, 24 shared hours — B1's only, since only its preset carries CTR. Section 1 carries the portfolio's spend, impressions and CPM.

spendimpressionsCPMclicksCTRinstallsclick→installCPI
2026-08-16$484.5759,0058.213,6346.16%56315.49%$0.861
2026-08-17$496.3657,1368.693,2395.67%47714.73%$1.041

Pooling across hours is a mix comparison. It weights each hour by delivery, and agrees with the unweighted hourly read on CTR and CPM.

The three measures, portfolio, both days:

measure2026-08-162026-08-17moves?
booked$1,869.11 (2.64)$1,860.31 (2.65)settled
within-day$578.01 (0.82)$753.18 (1.07)never
cohort @ 24h$740.86 (1.04), 100% covered$881.43 (1.25), 100% coveredfrozen, both days
2026-08-18T18:23:08.029635 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ booked within-day cohort @ 24h 0 200 400 600 800 1000 1200 USD 2.65 0.54 0.57 2.58 1.08 1.27 the number above each bar is that measure's ROAS against the same day's spend The three revenue measures, 2026-08-16 against 2026-08-17 (UTC) 2026-08-16 2026-08-17
The three revenue measures on both days, ROAS above each bar

Booked revenue by the day its payer installed, B1, whose top row is the within-day figure:

installedbooked on 08-17share
2026-08-17$535.7341.9%
2026-08-16$37.833.0%
2026-08-15$206.8116.2%
2026-08-14$17.301.4%
2026-08-13$53.764.2%
2026-08-12$12.991.0%
2026-08-18T18:23:08.073148 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 2026-08-16 2026-08-17 0 200 400 600 800 1000 1200 USD the bottom segment IS the within-day figure: the same number seen twice Booked revenue by the day its payer installed (UTC) the day itself one day earlier two days earlier three days earlier four or more
Booked revenue by the day its payer installed

(ii) Each measure per account, both days.

2026-08-16

accountbookedbROASwithin-daywROAScohort@24hcROASpayerspayer%ARPUARPPU
Portfolio$1,869.112.64$578.010.82$740.861.041339.8%$1.373$14.05
B1$1,316.942.72$261.020.54$277.130.579111.0%$1.596$14.47
Nomad Node$552.172.90$316.991.66$463.742.43427.9%$1.044$13.15
KBM1$0.000.00$0.000.00$0.000.0000.0%$0.000—
HR1$0.00—$0.00—$0.00—0———

2026-08-17

accountbookedbROASwithin-daywROAScohort@24hcROASpayers (d0)payer% (d0)ARPU (d0)ARPPU (d0)
Portfolio$1,860.312.65$753.181.07$881.431.25686.6%$0.8583$12.96
B1$1,341.062.70$539.291.09$650.981.31497.2%$0.9602$13.29
Nomad Node$519.252.82$213.891.16$230.441.25195.5%$0.6679$12.13
KBM1$0.000.00$0.000.00$0.000.0000.0%$0.0000—
HR1$0.00—$0.00—$0.00—0———

Rank these rows on within-day or cohort@24h, never on booked. Today they agree: booked 2.82 against 2.70, within-day 1.16 against 1.09. Yesterday they disagreed.

The mix-neutral line. B1's CPM on 2026-08-16's mix is $8.69 against the $8.69 read: one campaign delivered, so the 5.8% is country mix, section 3.

5The campaigns, side by side

Delivery is Meta's instrument on both sides of every ratio; every revenue measure is ours. Cohort horizon H=24h. Rank on CPM, cost per click and CPI only — geography is the treatment here, which is what makes those comparable across campaigns, while revenue still needs 16 payers (DECISION_LOG.md #37, #48) and a campaign under that bar carries a direction only.

⚠ Spend here is each account's OWN day and our columns are the UTC day, the same seam section 3 carries and for the same reason: only B1's export has the Ad ID an hourly restitch needs. It bites on B1 and KBM1 at UTC-7 and not on the Nomad pair or HR1 at UTC+0.

(i) Every campaign the portfolio ran.

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
bailingxia_meituan_ww_cvr_260802B1$480.6867.6%56,535$8.50602$0.798$535.731.1193
0814_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$84.0711.8%19,899$4.22209$0.402$114.201.3624
0811_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$72.7610.2%11,758$6.19115$0.633$66.010.9114
bailingxia_srfhjyd_ww_cvr_260814KBM1$46.216.5%367$125.914$11.553$0.000.000
0814_vl_bailingxia_srfhjyd_maimaiNomad Node$27.153.8%2,982$9.1021$1.293$33.681.244
bailingxia_meituan_ww_cvr_260730B1$0.000.0%0—43$0.000$0.00—8
bailingxia_meituan_t3_cvr_260725B1$0.000.0%0—26$0.000$3.56—6
bailingxia_meituan_t3_cvr_260723B1$0.000.0%0—3$0.000$0.00—0
bailingxia_meituan_t2_cvr_260723B1$0.000.0%0—1$0.000$0.00—0
bailingxia_meituan_dach_cvr_260729B1$0.000.0%0—1$0.000$0.00—1
bailingxia_meituan_t1_cvr_260725B1$0.000.0%0—1$0.000$0.00—0
bailingxia_meituan_t2_cvr_260725B1$0.000.0%0—1$0.000$0.00—3

Four of five delivering campaigns are not ours to steer. The three Nomad Node buys took $183.98, $0.402 to $1.293 a registration against B1's $0.798.

0814_vl_bailingxia_srfhjyd-rain-chuva is the cheapest registration in the portfolio. It is not ours, and Nomad CPMs run $4.22 to $9.10 against B1's $8.50.

(ii) The same, per account. B1's own campaign row carries the funnel columns the others cannot.

B1, the funnel version

campaignspendshareimpressionsimpr shareCPMclicksCTRcost/clickinstallsCPIwithin-daywROASpayers
Worldwide$496.36100.0%57,136100.0%8.693,2395.67%$0.153477$1.041$535.731.0843

Booking with no delivery, and excluded from every rate above: German (DE/AT) 0 installs (Meta), 1 registration (ours), $0.00 within-day; Earner (retired 08-03) 0 installs (Meta), 43 registrations (ours), $0.00 within-day. Counting them would put installs into the CPI denominator against spend that never happened.

Account CPM $8.21 → $8.69 (5.8%). Held to 2026-08-16's campaign mix it is $8.69 (5.8%) — the gap between those two is the mix, and here it is nil.

This section carries no chart. One campaign delivered, so a spend-share or CPM-by-campaign chart would be a single flat line at 100%.

The other accounts' campaigns.

Nomad Node

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
0814_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$84.0745.7%19,899$4.22209$0.402$114.201.3624
0811_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$72.7639.5%11,758$6.19115$0.633$66.010.9114
0814_vl_bailingxia_srfhjyd_maimaiNomad Node$27.1514.8%2,982$9.1021$1.293$33.681.244

KBM1

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
bailingxia_srfhjyd_ww_cvr_260814KBM1$46.21100.0%367$125.914$11.553$0.000.000

HR1

nothing delivered or registered.

How the shared accounts get a campaign row. Their export has no Campaign name column; there the Ad set name is the campaign name.

6Every asset, and inside B1's worldwide campaign

(i) Every asset the portfolio ran. One row per ad, with the account it ran in named on it. Spend and impressions are each account's own day; registrations, payers and revenue are ours on the UTC day. The join is the ad NAME, which is allowed here only because the account is already fixed — by campaign_id on our side and by which export the row came from on Meta's — so the name separates assets inside one known account and never decides which account a row belongs to.

assetaccountspendimpressionsCPMregistrationscost/regwithin-daywROAScohort@24hpayers
vid_ww_pool5_15s_9x16_v1B1$480.6856,535$8.50529$0.909$516.391.07$607.1568
nomad-0811-03-rain-chuva-video-01Nomad Node$72.7611,758$6.19112$0.650$66.010.91$79.0013
nomad-0814-03-rain-chuva-video-01Nomad Node$58.4917,105$3.42161$0.363$109.191.87$112.7521
vid_ww_pool5_15s_9x16_v1KBM1$46.21367$125.914$11.553$0.000.00$0.000
nomad-0814-03-maimaiNomad Node$27.152,982$9.1021$1.293$33.681.24$33.684
nomad-0814-03-rain-chuva-video-02Nomad Node$25.582,794$9.1648$0.533$5.010.20$5.013
vid_ww_bodysuit_10s_9x16_v1B1$0.000—50$0.000$13.58—$13.5815
vid_ww_bikini_10s_9x16_v1B1$0.000—28$0.000$5.76—$5.766
vid_ww_spill_8s_9x16_v1 - CopyB1$0.000—19$0.000$0.00—$5.764
vid_ww_lounge_8s_9x16_v1B1$0.000—16$0.000$0.00—$0.008
vid_sasian_bodysuit_10s_9x16_v1B1$0.000—12$0.000$3.56—$18.742
vid_sasian_bikini_6s_9x16_v1B1$0.000—5$0.000$0.00—$0.001
vid_utility_6s_9x16_v1B1$0.000—3$0.000$0.00—$0.002
nomad-0811-03-rain-chuva-video-02Nomad Node$0.000—3$0.000$0.00—$0.001
vid_control_6s_9x16_v1B1$0.000—2$0.000$0.00—$0.000
vid_control_sexy_9x16_v1B1$0.000—2$0.000$0.00—$0.000
vid_utility_sexy_9x16_v1B1$0.000—2$0.000$0.00—$0.000
vid_ww_mugshot_15s_9x16_v1B1$0.000—2$0.000$0.00—$0.000
vid_sasian_spice5_15s_9x16_v1B1$0.000—2$0.000$0.00—$0.001
vid_sasian_bikini_10s_9x16_v1B1$0.000—1$0.000$0.00—$0.000
vid_ww_spill_8s_9x16_v1B1$0.000—1$0.000$0.00—$0.000
vid_ww_pool5_15s_9x16_v1 - CopyB1$0.000—1$0.000$0.00—$0.000
vid_utility_15s_9x16_v1B1$0.000—1$0.000$0.00—$0.000
vid_utility_10s_9x16_v1B1$0.000—1$0.000$0.00—$0.000
vid_sasian_fishnet_top_6s_9x16_v1B1$0.000—1$0.000$0.00—$0.000
vid_latina_es_bikini_10s_9x16_v1B1$0.000—0—$0.00—$0.003
vid_de_german_10s_9x16_v1B1$0.000—0—$0.00—$0.001

The two shared rain-chuva cuts buy registrations at half what ours does. nomad-0814-03-rain-chuva-video-01: $58.49, 161 registrations, $0.363 each, $3.42 CPM. vid_ww_pool5_15s_9x16_v1: $480.68, 529, $0.909, $8.50.

Within-day return orders them the same way: 1.87 and 0.91 against 1.07.

Every B1 row with zero spend still books revenue, and that is the retired tail paying today rather than any delivery on this day.

Every asset, per account.

B1

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
bailingxia_meituan_ww_cvr_260802B1$480.68100.0%56,535$8.50602$0.798$535.731.1193
bailingxia_meituan_ww_cvr_260730B1$0.000.0%0—43$0.000$0.00—8
bailingxia_meituan_t3_cvr_260725B1$0.000.0%0—26$0.000$3.56—6
bailingxia_meituan_t3_cvr_260723B1$0.000.0%0—3$0.000$0.00—0
bailingxia_meituan_t2_cvr_260725B1$0.000.0%0—1$0.000$0.00—3
bailingxia_meituan_t2_cvr_260723B1$0.000.0%0—1$0.000$0.00—0
bailingxia_meituan_dach_cvr_260729B1$0.000.0%0—1$0.000$0.00—1
bailingxia_meituan_t1_cvr_260725B1$0.000.0%0—1$0.000$0.00—0

Nomad Node

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
0814_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$84.0745.7%19,899$4.22209$0.402$114.201.3624
0811_vl_bailingxia_srfhjyd-rain-chuvaNomad Node$72.7639.5%11,758$6.19115$0.633$66.010.9114
0814_vl_bailingxia_srfhjyd_maimaiNomad Node$27.1514.8%2,982$9.1021$1.293$33.681.244

KBM1

campaignaccountspendshareimpressionsCPMregistrationscost/regwithin-daywROASpayers
bailingxia_srfhjyd_ww_cvr_260814KBM1$46.21100.0%367$125.914$11.553$0.000.000

HR1

nothing delivered or registered.

Inside B1's worldwide campaign

#### Structure on this day

One ad set delivered and one ad inside it: E2/pool5, the sixth day of the single-arm buy. The campaign holds six ad sets and seven ads; five ad sets and six ads spent nothing. The ad-set row is therefore the ad row on this day, an identity that belongs to the daily cut, and it is checked against the hourly export each time it is claimed.

#### A. Per asset — delivery

Meta's instrument on both sides of every ratio. Our registrations never enter this table.

assetspendimpressionsCPMclicksCTRinstallsclick→installCPI
E2/pool5$496.3657,1368.693,2395.67%47714.73%$1.041
earner/bodysuit$0.000—0—0——
earner/bikini$0.000—0—0——
earner/pool5$0.000—0—0——
E2/bikini$0.000—0—0——
E2/bodysuit$0.000—0—0——
E2/mugshot$0.000—0—0——
E2/spill$0.000—0—0——
E2/spill2$0.000—0—0——
E2/lounge$0.000—0—0——
DEww/pool5$0.000—0—0——

#### B. Per asset — the three revenue measures

Ours on every column. Meta can express only booked, so it rides bracketed beside that column and never as a row. Payers are distinct people, never transactions. Cohort horizon H=24h, 100% covered on this day. Report clock UTC.

assetbookedbROAS (Meta)within-daywROAScohort@HcROASpayers (d0)payer% (d0)ARPU (d0)ARPPU (d0)largest payer
E2/pool5$936.801.89 (2.32)$516.391.04$607.151.22448.4%1.15913.8010.6%
earner/bodysuit$28.49— (—)$0.00—$0.00—00.0%0.000——
earner/bikini$38.89— (—)$0.00—$0.00—00.0%0.000——
earner/pool5$6.32— (—)$0.00—$0.00—00.0%0.000——
E2/bikini$26.10— (—)$5.76—$5.76—14.2%0.2405.76100.0%
E2/bodysuit$98.13— (—)$13.58—$13.58—14.8%0.64713.58100.0%
E2/mugshot$0.00— (—)$0.00—$0.00—00.0%0.000——
E2/spill$0.00— (—)$0.00—$0.00—00.0%0.000——
E2/spill2$84.29— (—)$0.00—$5.76—15.3%0.3035.76—
E2/lounge$43.46— (—)$0.00—$0.00—00.0%0.000——
DEww/pool5$0.00— (—)$0.00—$0.00—00.0%0.000——

The 16-payer bar (#37): any row above whose payer count is under 16 is a direction and never a magnitude. E2/pool5 at 41 payers is the only row on this table that clears it.

Every retired asset still books revenue and none of it is delivery. E2/bodysuit $98.13, E2/spill2 $84.29 — the tail section 4's booked split shows.

#### C. Per asset — country mix

⚠ This table is cut on the META day, while every other table on this page is on the UTC clock. Meta serves no hour × country grid, so per-country delivery exists only on the ad account's own UTC-7 day and cannot be restitched. It is a seven-hour-offset window against tables A and B above; read it for mix, never for level against them.

The last column is the share of that asset's own within-day revenue that came from the United States: where it far exceeds the US spend share, the return is a property of the geography the asset bought.

assetspendIndia %US %other %US % of its revenue
E2/pool5$480.6819.8%17.6%62.6%20.9%

pool5 bought 17.6% United States and earned 20.9% there. The ratio is 1.19, against 1.93 on 08-16 and the 3.7 of 2026-08-04.

The US is paying roughly its own way, even at a $2.917 install.

2026-08-18T18:23:08.343026 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ E2/pool5 0 20 40 60 80 100 % of that asset's spend Where each asset bought — share of its own spend by region, 2026-08-17 (META day) IN US MX TR ID GB other
Where each asset bought: share of its own spend by region
2026-08-18T18:23:08.383203 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ E2/pool5 0.0 0.5 1.0 1.5 2.0 2.5 3.0 USD per install Cost per install by region — every asset, 2026-08-17 (META day) IN US MX TR ID GB
Cost per install by region, every asset
2026-08-18T18:23:08.424058 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ E2/pool5 0 20 40 60 80 100 USD Within-day revenue by region — every asset, 2026-08-17 (META day) IN US MX TR ID GB
Within-day revenue by region, every asset

#### The day across the run

2026-08-18T18:23:08.510174 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 08-14 08-15 08-16 08-17 day (UTC) 0.0 2.5 5.0 7.5 10.0 12.5 15.0 17.5 20.0 payers / installs % Payer rate by day — every asset (UTC) E2/pool5 earner/bodysuit E2/bikini E2/bodysuit E2/spill2 E2/lounge
Payer rate by day, one line per asset
2026-08-18T18:23:08.566026 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 08-14 08-15 08-16 08-17 day (UTC) 0.0 0.2 0.4 0.6 0.8 1.0 within-day USD per install ARPU by day — every asset (UTC) E2/pool5 earner/bodysuit E2/bikini E2/bodysuit E2/spill2 E2/lounge
ARPU by day, one line per asset
2026-08-18T18:23:08.615174 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 08-14 08-15 08-16 08-17 day (UTC) 0 2 4 6 8 10 12 14 within-day USD per payer ARPPU by day — every asset (UTC) E2/pool5 earner/bodysuit E2/bikini E2/bodysuit E2/lounge
ARPPU by day, one line per asset
2026-08-18T18:23:08.653800 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ 08-14 08-15 08-16 08-17 day (UTC) 0.5 0.6 0.7 0.8 0.9 1.0 revenue / spend Within-day ROAS by day — every asset (UTC) E2/pool5
Within-day ROAS by day, one line per asset
2026-08-18T18:23:08.762502 image/svg+xml Matplotlib v3.11.1, https://matplotlib.org/ CTR click→install CPI payer rate * ARPU * wROAS * 0.0 0.2 0.4 0.6 0.8 1.0 normalised across the day (1.0 = best of the pack) * axis sits under the 16-payer bar on most days: direction only, never a level. Assets under 20 installs on the day are not plotted. Composite — every asset across every measure, 2026-08-17 E2/pool5
Composite: every asset across every measure, normalised across the day

7Caveats

The cohort figure is frozen, at 100% coverage on both days. 08-17's last install passed its 24-hour horizon at 23:59 UTC on 08-18, and re-cutting the day against the 2026-08-22 payment data returns $881.43 to the cent. The figure this page carries is final and its comparison against 08-16 stands at +19.0%. It was first published on the 2026-08-18 18:54 UTC cut, which had reached 79% of the day's installs; that was a lower-coverage read of the same cohort, not a different number.

⚠ The instrument gate is still outside its band at 1.08, against 0.91 to 1.06, but it has more than halved its breach. 08-16 read 1.15. The 08-16 report attributed that to a lengthening repurchase tail: our records key a payment to the person who made it and never expire, while Meta's window is 7-day click, 1-day view, so the share of a day's revenue Meta structurally cannot attribute grows as the account ages. A day whose booked revenue leans more on its own fresh cohort should therefore read closer to Meta, and this one does: 41.9% of booked came from same-day installs against 20.4% on 08-16. That is consistent with the explanation and is not proof of it, and the band still needs recalibrating on a cohort-limited basis before either reading counts as a pass or a fail.

⚠ The registration fall is the largest single thing on this page and nothing here explains it. Down 24.5% portfolio-wide in one day, in two independent accounts at once, with no budget or campaign change on either, and the campaign activity history returns no rows for 2026-08-15 to 2026-08-18. On B1 the Meta-side install count fell 15.3% against our 17.8%, which rules out a registration-feed artefact there because two independent instruments agree. It is not ruled out on the shared accounts, whose export carries no install column to check against.

B1's 43 within-day payers clear the 16-payer bar, and the portfolio's 153 booked payers clear it. Nothing below the account level does: no country cell, and no per-asset row except E2/pool5 at 41.

⚠⚠ KBM1 AND HR1 BUY THE UNITED STATES ONLY, AND B1 AND THE SHARED PAIR BUY WORLDWIDE, SO NO BLENDED FIGURE IS COMPARABLE ACROSS THE ACCOUNT ROWS. Both new accounts read Inclusion: United States in their ad sets, and every one of their registrations resolves to a US IP, against 4% for B1 and 3% for the shared pair. B1's own US cell runs CPM $25.36 on this day against its account figure of $8.50, so the CPM and cost-per-registration columns in section 1 compare a US buy with a worldwide one wherever a new account sits beside an old one. The per-account rows are correct as figures and must not be ranked on those two columns; the like-for-like comparison is against B1's US cell, which the country export carries.

⚠ The United States targeting is deliberate, and it is what these two accounts exist to test. Inside B1's worldwide buy pool5 has repeatedly earned a share of revenue in the United States far above its share of spend there: 13.7% of spend against 50.5% of revenue on 2026-08-04, and 17.6% against 20.9% on this day, with B1's US cell returning a booked 3.80 against the account's 2.58. KBM1 and HR1 buy the United States directly, to find out whether that concentration survives when the country is bought on purpose rather than reached by an optimiser spending worldwide. Their ad sets read Inclusion: United States; B1's read Worldwide minus Singapore and Taiwan, the shape DECISION_LOG.md #45 fixes. They are a test arm against a control, and the ww the campaign names carry is wrong about that.

What the test returned on these two days: nothing. KBM1 spent $85.75 on United States traffic across 2026-08-16 and 2026-08-17 for 11 registrations and no payers at all, while B1's own US cell returned a within-day 0.89 and then 1.28 on comparable money. Two days is two days and this page does not read a verdict off them; the account is four days old and the reading that matters is the one it has after a run long enough to carry a payer count.

One operational note on changing it. Both campaigns are Advantage+ Sales, whose ad-set creation form exposes no Locations section, so the geography cannot be tuned the way B1's is. The live ad sets do render a Locations block with an Edit control, so a change is probably an edit. That is an affordance and not a proven write, and nothing here has been changed.

⚠ HR1 spent $0.00 on both days and its zero rows are measured. Its export pulled successfully and reads zero across the whole window. Both its ads published late on 08-17 and its first delivery falls outside this report.

The 08-16 figures on this page read one registration higher than the 08-16 report's own: 1,361 against 1,360 at portfolio level and 825 against 824 for B1. The difference is a single registration through a dormant B1 campaign that this run's account map now recognises. It moves no rate on either page.

Every account's clock is now read off the account itself, and one of them was wrong on the last cut of this page. B1 and KBM1 run at UTC-7, so a UTC day on either is stitched from two account days; the Nomad Node pair and HR1 run at UTC+0, where the reporting day is the UTC day. B1's seven hours are confirmed by correlating its hourly impressions against our registrations, which recovers k=7 at r = 0.878 against 0.702 and 0.697 either side. KBM1's and HR1's could not be recovered that way — the correlation needs an account's own volume and KBM1 has seven registrations on its best day — so they were read directly off each account's campaign objects, which Ads Manager stamps in the account's own zone: KBM1 2026-08-15T01:33:28-0700, HR1 2026-08-17T08:25:57+0000. An offset is a setting, and waiting for volume to correlate one is what kept KBM1 on its own reporting day inside a UTC portfolio total — worth $46.21 against the $22.36 that day actually holds.

⚠ Two instruments produce B1's figures and they count different populations on purpose, so read the label that says which. The per-account tables select on campaign_id and cover every B1 campaign; sections 2 to 6 select on Ad ID against the run config's asset map and cover only mapped ads. On this day that is 678 registrations against 651, and $1,341.06 of booked revenue against $1,278.60: the narrower instrument inside the wider one, in the direction the scope difference predicts. Neither is wrong and they must not be quoted against each other.

⚠ What a column preset actually costs, now that it has been measured. Only B1's account has Full View; the Nomad Node preset is not ours to change, and KBM1's popover offers Performance, Performance and clicks, Engagement and Delivery with no Full View to pick. That costs four columns — Ad ID, Link clicks, CTR, Leads — and so the click→install funnel, which is why every funnel table on this page says B1 on it. It costs nothing else: hour, country, campaign and asset are breakdowns, set on the export URL by whoever pulls it, and they were verified on a shared account at 24 of 24 hourly buckets and 3,146 country rows. Reading that preset as a limit on the GRAIN is what published sections 2 and 3 as B1-only for a week. Building the preset on KBM1 and HR1 is still worth doing — it is what gives those two a funnel.

The country, campaign and asset sections carry Meta's figures on each account's own day, seven hours offset from the UTC tables on B1 and KBM1 and identical on the Nomad pair and HR1. Meta serves no hour × country grid and no ad-level hourly without Ad ID, so those cuts cannot be restitched. They are read for mix, never for level.

The FX table is sixteen days old. Revenue in 33 currencies is converted at rates pulled on 2026-08-02. It is the only named candidate left in the instrument reconciliation that has never been tested.

37% of registrations never enter a revenue measure and that is true of every day in this series. Every "ours" figure from section 2 down means registrations attributable to a mapped Meta ad. It is internally consistent, because the payer rate divides our payers by that same population.

One draft sits unpublished on B1. The manage view reads Review and publish (1). Nothing on this page depends on it and it was not touched.

KBM1's only payer to date paid $4.99 on 08-15, three minutes after installing. The account is a deliberate US-only test of pool5, which earns disproportionately in the United States inside B1's worldwide buy.

Read KBM1's CPM against B1's own US cell at $25.36, not against B1's blended $8.69. It is the only figure on that account with a sample behind it. KBM1 is targeted United States only and B1 buys worldwide at 4% US: the two account figures suggest a premium of 10.1 times; like for like it is 3.5.

Click→install had no direction at all on this day, the first in this run where that rate did not move; CPM and CTR both did.

The shared accounts' campaign rows rest on a naming identity, not a column. Every Nomad row in our registration records has campaign_name equal to adset_name, and that stops holding the moment an ad set is split out of a campaign. KBM1 and HR1 have neither column and run one campaign each, so their single campaign row is their account row.

Nothing in the per-asset table is a controlled comparison — different accounts, different ad sets, different audiences, and Meta chose every allocation — so read it as where the money went and what came back (DECISION_LOG.md #48).

The standing chart set has no campaign block. report_charts.py emits nineteen figures across the hourly, country, aggregate and per-asset sections and none for section 5, so no report in this series has ever carried one. That is a gap between the format document and the generator.

8What would settle the open questions

Why a quarter of the registrations went missing across two independent accounts on one day. This is the first thing to answer and nothing on this page answers it. The cheap checks, in order: whether the registration feed dropped rows on 08-17, by comparing the sink's own count against the Telegram export for the same day; whether the cloaker's fire rate moved; and whether Meta's install column fell by the same proportion on the shared accounts as it did on B1. Only the third needs anything we do not already hold, and it needs a column their preset does not carry.

Whether the payer rate at 14.9% is the same buy converting better or a different buy. Registrations fell 24.5% and the payer rate rose by half. Those are consistent with one story, that the missing quarter were people who would never have paid, and with a second, that the day reached a different population. The country cut favours the first, since the US install got dearer and scarcer. Two more days at this budget separate them.

Whether the instrument band survives recalibration. Unchanged from 08-16: compute the ratio over payments from cohorts inside Meta's 7-day window only, across the whole series. If the band holds on that basis and drifts on the current one, the gate's definition is what needs fixing.

KBM1's figures here have moved since an earlier cut of this page, and what moved is the clock they are read on. That account runs on UTC-7 and its money was being read off its own reporting day while B1's was being stitched onto UTC — so a portfolio total was adding two different 24-hour windows. KBM1 now reads $22.36 on this UTC day against the $46.21 its own day shows, and the portfolio $702.70 against $726.36. Nothing about B1 or the shared pair moves: B1 was already stitched and the Nomad Node accounts sit at UTC+0, where the two days are the same day.

This day answers the question the 08-16 report handed forward. Portfolio within-day return has now printed 1.20, 0.82 and 1.07 across three days inside one unchanged regime, so 0.82 was the outlier. The day that replaced it differs from 08-15 in both directions: the volume is a quarter lower and the payer rate half again higher.

9What this hands to the next read

The 08-18 report inherits a single-arm buy in its seventh day, a portfolio within-day return that has printed 1.20, 0.82 and 1.07 across three days, and a registration count that fell a quarter in one day for no reason this page can name. The question it can answer that this one cannot is whether the registration volume comes back; if it does not, $0.684 a registration is the new level and every plan built on $0.521 is wrong.

It also inherits HR1's first delivering day, which falls on 08-18. That report is the first on which all four accounts carry a non-zero row, and the first that can price a cold US account on more than one day: HR1 buys the same United States KBM1 does, so the two are comparable to each other and to B1's US cell at $25.36, and none of them is comparable to B1's blended figure.

10Reproduce

Report clock UTC. Every account's export is stamped in its own account zone, so B1's and KBM1's delivery rows are restitched from two Meta days each and the Nomad Node pair's and HR1's are not — those two run at UTC+0, where the account day already is the UTC day. The country, campaign and asset tables cannot be restitched at all and are labelled where they appear.

run_runs/2026-08-18_2026-08-17_daily_auto/
the per-account breakdownpython -m ad_ops.portfolio_split --run <run> --day 2026-08-17 --prev 2026-08-16, block portfolio.md; the pull's own status in portfolio_pull.txt
payment cut2026-08-18 18:54 UTC, on the repaired join
Meta exportsB1 day and country×day 2026-07-01_2026-08-19 pulled 2026-08-18 18:47 UTC; hourly per day, all 24 buckets verified. KBM1, HR1, Nomad Node ×1 and ×2 each at three grains pulled 2026-08-19 00:1x UTC — day over the same range, country×day over 2026-08-16_2026-08-18, and hourly for 08-17 and 08-16
registrationsadjust_sink push, merged onto the previous run's ledger — 28,876 rows, 6,258 from this pull
paymentsin-app-purchase API, full history, joined onto the export base and repaired on the account UUID. 237 payments on 08-17, 85.7% carrying a payer before repair
FX_runs/2026-08-02_today_read/fx_rates.json
regimescampaign activity history re-read for 2026-08-15_2026-08-19; no rows in the window, so both days sat in one unchanged regime
python -m ad_ops.daily_pipeline --day 2026-08-17
python -m ad_ops.portfolio_split --run _runs/2026-08-18_2026-08-17_daily_auto \
    --day 2026-08-17 --prev 2026-08-16

The pipeline pulls B1's day, country×day and two hourly exports, then four exports per other account — day, country×day and hourly on each of the two days — then the payments and registrations, then runs measures, day_compare, cohort_arpu, asset_estimator, portfolio_split, report_tables and report_charts in the fixed order, on both the UTC and the META configs it writes. portfolio_split rebuilds each account's hourly archive by globbing every run directory, because a UTC day on a UTC-7 account needs the account day before it and a single night's pull holds only two. It chains the payment and registration ledgers forward from the previous run and repairs the payer on the account UUID after merging them.

11Appendix — definitions

The report clock is a UTC day. Adjust reports in UTC, so a UTC-bucketed report lines up with the attribution dashboard without anyone converting in their head. B1 is fixed at UTC-7, so a UTC day on that account is Meta day D−1 17:00 to 23:59 plus Meta day D 00:00 to 16:59. The two clocks are not close: on a measured day the same figures differed by 14.6% on spend and 40.7% on within-day revenue.

Three things the clock does not reach, each labelled where it appears. Table C's per-asset country mix cannot follow it: the rake is per ACCOUNT, against that account's own hourly margin, and an asset has no hourly margin of its own. The instrument check is invalid off the account's clock, because Meta's conversion value sits on its conversion hour and cannot honestly be restitched. And the estimator runs on Meta's clock deliberately, because its subject is delivery windows and a budget change is an instant on the account's own clock.

The three revenue measures, never one, never mixed, always labelled:

measurecountsmoves after the day closes?
bookedrevenue that arrived inside the day, whatever day its payer installedsettles about four hours after midnight, then fixed. Meta's own number is this basis
within-dayinstalled that day and paid before that day closednever. Sealed at midnight
cohort at Hthat day's installs, counted within H hours of each person's own install. House horizon H=24rises until every install has lived H hours, then frozen. Always state coverage

A day whose spend is falling reads high on booked and low on the other two, purely because yesterday's buyers are still paying. Use within-day for day-over-day, because it is immutable and needs no horizon. Use cohort at a fixed horizon to compare hours to each other, because within-day censors by hour of day. Booked is what Meta will quote at you, so it is reported to explain the gap and never to rank.

All three are read on our own payment records, and all three count only payments the record can tie to a person who installed through one of our mapped ads. That tie is made on the numeric user id where the payment carries one and on the account UUID where it does not.

Two install counts exist and they are never crossed. Meta's Leads and our own registrations disagree by 5 to 10%. Meta's is used for the delivery funnel, so CPI and click→install have both numerator and denominator on one instrument. Ours is used for payer rate and every revenue measure, so the payers and the installs they came from are the same population. The per-account tables print cost/reg for exactly this reason: they divide by our registrations, and the delivery tables divide by Meta's installs.

The four ad accounts, what each buys, and how each is identified. B1 and the shared Nomad Node pair buy worldwide; KBM1 and HR1 buy the United States only. That difference governs which figures may be set against each other at all, and it is not visible in the campaign names, which say ww on all four. Accounts are keyed on campaign_id and never on the campaign name: the cloaker requires the key bailingxia in every campaign name, so a name test returns B1 for all four. B1 is 1738541847343652; the shared Nomad Node pair is 835434076171203 and 3267486106793669, whose campaigns for this app are 0811_, 0814_ and 0818_ and whose greenvid and pixvoo campaigns are not ours to count; KBM1 is 1533358924738693; HR1 is 1598814841849780. Two campaigns inside B1's own account are excluded on purpose: youguqi_, agreed as tuition, and 0730_starfall_*, run for a third party.

A regime is a stretch over which the ad set's daily budget did not change. The budget is a decision and delivery is a response to it, so a comparison that crosses a budget change is comparing two different buys. Both days on this page sit in one regime: the campaign's own activity history returns no rows for 2026-08-15 to 2026-08-18.

Internal — noindex. Not for distribution outside the team.