> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Gated content

> The worked example: put an asset behind a form, deliver it the instant someone converts, and follow up on their clock.

You have something worth a form fill: a research report, a benchmark, a playbook. A gated content motion puts it behind a short form, drives traffic to it, delivers it the instant someone converts, then follows up while it is still fresh.

What makes it its own type: **there is no date.** Every touch is timed from one person's own conversion, so the gate keeps working for months after the launch push ends.

## What you provide

One thing: the asset. A PDF you upload, a [file already in your library](https://docs.allgoodhq.com/mk/content/hosted-files.md), or a link to something you host yourself. Brand guidelines if you have them. Everything else is generated.

## What gets built

An agent builds the motion's assets from your asset and your [brand guidelines](https://docs.allgoodhq.com/mk/content/brand-guidelines.md), in one session, and saves each one to your library as it finishes.

| Asset | What it is |
| - | - |
| **Form** | A capture form, email and first name by default |
| **Landing page** | Pitches the asset behind the form. Or point at a page you already run |
| **Delivery email** | Carries the asset the moment someone converts |
| **Follow-up email** | The first touch of the arc, related content, 48 hours later by default |

The motion itself is the fifth asset. It names the others and holds the settings. Everything it builds goes through the same drafts, versions and approvals as any other [content](https://docs.allgoodhq.com/mk/content/approvals.md).

![The motion's assets, with how many are built and published](https://mintcdn.com/allgoodtechnologyinc/gM338x6qoqz24WkO/images/mk/motions/gated-content-assets.png?fit=max\&auto=format\&n=gM338x6qoqz24WkO\&q=85\&s=42bfbabbac90efb720cc6978b6e5acf2)

The motion's assets, with how many are built and published.

## What happens when it runs

Change nothing and you get this:

| # | What happens | When |
| - | - | - |
| 1 | The landing page pitches the asset behind the form | Live at launch |
| 2 | Someone converts. The asset appears on the thank-you page and arrives by email | Immediately |
| 3 | First follow-up, related content | 48 hours after *their* conversion |
| 4 | Further follow-ups, if you authored them | Spaced from their conversion |
| 5 | The motion stops touching them | End of the arc |

And at the edges, without anyone configuring it:

* **Converting stops the promotion.** Once someone has the asset, they are not invited to download it again.
* **Sales engagement stops the follow-up.** A booked meeting or an open conversation ends marketing touches.&#x20;
* **Nobody gets the same touch twice**, even if they re-enter.
* **The motion never ends.** People enter whenever they arrive and each gets the full arc from their own moment zero.

## Settings

| Setting | Default |
| - | - |
| Gate mode: hard gate, email only, ungated with capture | Hard gate |
| Form fields | Email and first name |
| Delivery: thank-you page, email or both | Both |
| Page and email design | Your page and email templates |
| First follow-up delay | 48 hours |
| Subject lines and copy | Written from the asset |
| What ends it: hand-off signals, unsubscribe | Meeting booked, sales engaged, unsubscribe |

Page and email design come from the [templates](https://docs.allgoodhq.com/mk/content/templates.md) in your library. Everything else is set on the motion itself.

## Common variations

* **Ungate it.** No form; whoever identifies themselves enters the arc. Because it is a setting, the same motion can be gated at launch and ungated later without a rebuild.
* **Email-only gate.** One field, for mid-value assets where a long form would kill conversion.
* **The analyst report treatment.** Hard gate, longer form, short arc, fast hand-off.
* **The community asset.** Ungated or email only, longer arc, no hand-off at all.
* **Reuse an asset already gated.** Point a second motion at the same library file so one report backs several motions without splitting its download numbers.
* **A/B or localise a touch.** Swap any email or page for a set of variants behind a [content router](https://docs.allgoodhq.com/mk/content/copy-and-variants.md). The flow does not change.

## Good to know

* **Launching publishes everything at once.** The form registers, the page goes live at its address, the emails become sendable, and the plan starts. See [Launching](https://docs.allgoodhq.com/mk/motions/launching.md).
* **The Status page shows the funnel in the motion's own terms**: page views, form fills, deliveries, follow-ups sent.
* **Hub pages and asset refreshes are on the roadmap.** One motion carrying several assets, and swapping v1 for v2 without re-sending delivery, are designed but not built.

> [!NOTE]
>
> Questions? Reach out to [support@allgoodhq.com](mailto:support@allgoodhq.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.