Skip to main content
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, 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, in one session, and saves each one to your library as it finishes. 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.
The motion's assets, with how many are built and published

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

What happens when it runs

Change nothing and you get this: 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.
  • 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

Page and email design come from the templates 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. 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.
  • 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.
Questions? Reach out to support@allgoodhq.com.