Added AudienceView domains

[ninoabbate]

• Description of Organization

• Reason for PSL Inclusion

• DNS verification via dig

• Run Syntax Checker (make test)

• Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration.

Description of Organization

Organization Website: https://www.audienceview.com
AudienceView is a company in the ticketing market that provides solutions to manage live events through all-in-one ticketing, marketing and fundraising platforms.

Reason for PSL Inclusion

Facebook has now expanded AEM support to all domains included in the Public Suffix List, in line with Apple's recent Private Click Measurement update. This ebales businesses to verify their eTLD+1 domains, if the hosting domain (eTLD) is registered in the Public Suffix List.
We run clients under our domains and they need that our domains are in the Public Suffix List in order to make tracing working on Facebook Pixel.

DNS Verification via dig

dig +short TXT _psl.ovationtix.com
"https://github.com/publicsuffix/list/pull/1269"

dig +short TXT _psl.electrostub.com
"https://github.com/publicsuffix/list/pull/1269"

dig +short TXT _psl.laughstub.com
"https://github.com/publicsuffix/list/pull/1269"

dig +short TXT _psl.tunestub.com
"https://github.com/publicsuffix/list/pull/1269"

make test

Extra info

I'm representing AudienceView as part of their TechOps team.

[dnsguru]

See #1245

[dnsguru]

privacycg/private-click-measurement#78

[bedfordsean]

Hi @ninoabbate,

The guidance from Facebook (clarified last week in the help centre article) is that this process is intended for large platform partners (like Shopify) to allow businesses that they host on behalf of to successfully validate their domain as if it were an eTLD+1.

The Public Suffix List is not useful, nor intended to be used as a means to gain additional subdomain events reporting.

I did a Google for "electrostub.com", "tunestub.com", and do see various merchants hosted as subdomains so it is possible that you may meet this criteria. However I don't see many hosted subdomains for "ovationtix.com" or "laughstub.com", with almost all search results pointing to the subdomain "www".

To clarify; do you wish for and intend for total cookie separation of each of those domains where subdomain owners can individually register through Facebook AEM and be treated as their own eTLD+1s?

Effectively beyond owning these domains, you'll not have much control for content on those root domains themselves. For example, I note you have a /login page on that domain. This may not work as it does today if you proceeded with a PSL addition.