v1.54.1 - the tenant behind the report, and its domains

The id in the failing request named the tenant - transcend-cdn.com/cm/8aaeb48f-.../airgap.js is GoFundMe - and their own loadOptions names every host their engine will write a cookie for:

sites: "gofundme.com gfm-test01.com gfm-dev.com gfm-dev01.com classy.org classy-test.org skilljar.com gfm-lab.com"

So the named-sites line in filters/transcend.txt now covers their production hosts, and the list says where to find anyone else's: a tenant's own airgap.js, at the id in its url.

airtable.com,classy.org,costco.ca,costco.com,gofundme.com,indiegogo.com,mayoclinic.org,skilljar.com,transcend.io##+js(transcend-reject)

Their purposes are the ones in the fifth tcm sample that came in with the report - Analytics, BrowserCookies, Advertising, AdvertisingSaleOfInfo, Functional, SaleOfInfo - which settles what that sample showed: BrowserCookies is the purpose their tenant declares not configurable, so their own writer will not move it, and Functional sat at their tri-state "Auto" because the regime that request resolved to shows a notice rather than a choice.

Run against their real file, the resource is untouched until their prelude loads, then writes their five configurable purposes to both stores:

[consent-rr] transcend-reject 1.4.0 refused=Analytics,Advertising,AdvertisingSaleOfInfo,Functional,SaleOfInfo via=cookie+storage, no engine

with BrowserCookies left alone, which is what their own engine does with it.

Filters, docs and one test pin - no resource change. 1024 tests.