jennpb commented 1 year ago

What?

Verifying WC domain for Meta (inc Facebook, Insta)

Why?

This change is necessary for brand safety. While the domain is unverified any advertiser would be able to run ads to the Wellcome Collection website. We would not be able to control the copy or content of the ad.
Verifying our domain allows us to use a whitelist, so that only approved partners can run ads to the Wellcome Collection website.
Additionally, if we choose to use remarketing at any point, verifying our domain will improve the accuracy of our tracking.

Request from Wellcome Collection Comms & Marketing, in coordination with 3rd party marketing company Ethix.

Actions required

There are three options for verifying the domain. All instructions are below, but only one option needs to be followed:

Copy this meta-tag: <meta name="facebook-domain-verification" content="gl52uu0zshpy3yqv1ohxo3zq39mb0w" />
Paste the meta-tag into the <head> ... <head> section of the website’s home page HTML source, and publish the page. -- Note: Verification will fail if the meta-tag code is outside the section or in a section loaded dynamically by JavaScript.
After you've published the home page, confirm that the meta-tag is visible by visiting http://wellcomecollection.org/ and viewing the HTML source.

Download the HTML verification file. Do not modify this file once you've downloaded it.
Upload the file to the root directory of this domain: http://wellcomecollection.org/
Your HTML verification file has uploaded successfully if you can see the verification code on your website: http://wellcomecollection.org/gl52uu0zshpy3yqv1ohxo3zq39mb0w.html

Go to your domain registrar, log in to your account and find the DNS records section.
Follow the instructions to add this TXT record in your DNS configuration: -- facebook-domain-verification=gl52uu0zshpy3yqv1ohxo3zq39mb0w -- Note: Some domain registrars require the @ symbol in the host field.
Use a DNS TXT lookup tool to confirm that the record has been updated across your servers.

alexwlchan commented 1 year ago

I think (2) is moderately fiddly with our architecture and more liable to break in future.

I don't have a strong opinion on which of (1) or (3) we should do; both would be pretty low-effort to implement.

alexwlchan commented 1 year ago

I've decided to put it in this repo; DNS records are managed elsewhere and it'd be a bit harder to find.

alexwlchan commented 1 year ago

Closing as done – we've added the meta tag, a test that we won't remove it, and Comms & Marketing are happy with the change.