Contact
Confirmed directly against the live form at herradura.com/en-us/contact/.
Fields
First name, last name, email, verify email (confirmation field), zip/postal code, country, category (picklist, brand-configurable options), message. No DOB/country-of-birth duplication; relies on the Age Gate having already run; see Web Forms & Salesforce for the full field comparison across all three forms.
Direct Salesforce evidence
Stronger than what we found on jackdaniels.com:
Contact form select field: name="00N1300000B80zB" (required, "Category" picklist)00N is Salesforce’s own ID prefix for a custom field on a Lead (or similar) object.
This is a genuine Salesforce Web-to-Lead field, not an inferred string like the “SCRM”
hint we found on Jack Daniel’s. See
Salesforce Integration for how this
gets proxied server-side.
Also confirmed on the live form: OneTrust category checkboxes
(ot-group-id-C0002/C0003/C0004) embedded directly in the markup, and, on the CSS
class names throughout, a bfwpf- prefix (bfwpf-form-control-container,
bfwpf-xola-button; see Book a Tour). That’s Brown-Forman’s
own existing shared WordPress plugin, almost certainly “Brown-Forman WordPress Forms.”
This is a good precedent for our own plan, not just a coincidence: Brown-Forman
already builds and shares one plugin across brand WordPress sites for exactly the
concerns we’re packaging separately for P1 (age gate, forms, tour booking). The
@brown-forman/p1-* package family is the same strategy, ported to the new stack.
Client-side component
ContactFormBlock: matches Herradura’s actual field set (see above). Renders its
OneTrust category checkboxes dynamically from the same config the
cookie consent package already has: one
source of truth for category IDs/labels, not copy-pasted between the consent banner
and every form.