Gated Content

What it is

Gated Content is a lead-capture gate. You place a Gated Content module on a page; instead of a direct download link, the visitor sees a short form. When they submit it, they get access to the file (or the content is revealed in place), and their details are captured as a lead.

Every submission is sent to Salesforce (a contact record), and — only when the visitor opts into a newsletter — subscribed in Campaign Monitor. This mapping is handled automatically by development; you don’t configure it.

Heads up — Salesforce connection being finalized: The final Salesforce fields for the lead connection are still being confirmed. This page will be updated with the finalized field details once that’s complete.

 

How to add a Gated Content module

1. Edit the page and add the Gated Content Block module to the Modules field (like any other module).
2. Give the block a Title (internal label).
3. Open the Gated Content field and configure the resource (see the options below).
4. Adjust spacing/width/background in Advanced options if needed (this is the standard module Advanced options panel).
5. Save and check the front end.

The standard form always collects First Name, Last Name, Email, and US State, plus the optional fields you enable below.

 

Per-resource form options (the Gated Content field)

Each Gated Content module is configured on its own — these settings are content and can be edited on the live site:

• Gated asset — the file released after a successful submission. Choose the asset to gate.
• Success behavior —
  • Swap form for a download button — after submitting, the form is replaced by a “Download now” button.
  • Reload to reveal content in place — the page reloads and the content is shown.
• Include “I’m a…” affiliation field — on/off. Adds the “I’m a…” dropdown (options come from the catalog — see below). Certain affiliations also reveal a school-district search.
• Required fields — which standard fields must be filled (First name / Last name / Email / US State). Required fields show a “*” and are validated.
• Include newsletter opt-in — on/off. Adds newsletter subscribe checkboxes.
• Newsletter lists — which lists from the catalog this resource offers as checkboxes.
• Newsletter heading — text shown above the newsletter checkboxes (supports the {site} token; leave blank to hide it).
• Extra CSS class — optional styling hook (advanced; usually leave blank).
• Success message — optional text/HTML shown above the download button on success.
• Error message — optional text/HTML shown if the submission fails (blank = plugin default).

 

The form catalog (affiliations & newsletter lists)

The “I’m a…” options and the newsletter lists you can offer come from a shared catalog, edited in the CP under the Gated Content section (its own item in the CP nav):

• Affiliation options — the “I’m a…” dropdown choices. Each has a Label (shown to the visitor), an Integration value (sent to Salesforce), and a Triggers hook checkbox (used for special routing such as the school-district lookup).
• Newsletter lists — the newsletter choices. Each has a Label and an Integration value, plus a Triggers hook flag for routing.

Add options to the catalog here first; then, on each module, use Newsletter lists to pick which of them that resource offers.

 

Where the lead goes

• Every valid submission creates/updates a Salesforce contact using the form fields (name, email, state, affiliation, etc.).
• Campaign Monitor subscription happens only when the visitor checks a newsletter opt-in. If they submit without opting in, the lead still goes to Salesforce — Salesforce only, no Campaign Monitor.

 

reCAPTCHA note (don’t “fix” this)

The form is protected by reCAPTCHA v3. The reCAPTCHA token is submitted under a deliberately non-obvious field name — this is intentional anti-bot behavior, not a bug. Bots that auto-fill the standard reCAPTCHA field then fail verification. Leave it as configured.

 

Notes

• This is the same feature on both the Chef Ann Foundation and The Lunch Box sites — the module, fields, and Salesforce/Campaign Monitor mapping are identical.
• The Gated Content field can be added to other entry types by development if you need to gate content elsewhere; the per-resource options above work the same wherever it appears.