Connect YouTube
Subscribe to your channel — read back over Google OAuth where scope allows.
What this step actually checks.
Hard verify
Hard where Google permits it. When the OAuth scope allows reading subscription state, a subscribe step is proven on connect. Where Google policy blocks the read-back, the step degrades honestly to a best-effort attestation — and is labelled as soft, never relabelled as a hard verify after the fact.
Find your channel ID
- 1
Sign in to YouTube and open Settings → Advanced settings. Your channel ID is listed there as a string starting with UC.
- 2
Copy that UC… value. That is the stable ID — prefer it over a custom @handle, which can change.
- 3
Paste it into the builder. GateCrate builds the subscribe link with the confirmation prompt baked in, so fans get the one-tap subscribe dialog.
Heads up — A handle URL (youtube.com/@yourname) works for fans clicking through, but the UC channel ID is what makes verification reliable — use the ID.
The action it runs.
In the builder you choose which YouTube action this step asks for — subscribe. Each one maps to the same move a fan would make by hand on YouTube, and the step clears the way the API confirms it.
What the fan sees.
- 1
The fan taps Subscribe on YouTube and is taken to your channel with the subscribe confirmation already open.
- 2
They subscribe, then connect Google so GateCrate can read it back — in a popup isolated from your account.
- 3
If the scope allows, the step verifies as proven. If Google blocks the read, it falls back to an honest attested step rather than pretending it was checked.
Whatever the fan connects to clear this step stays walled off from your artist login — their YouTube session never touches yours, and yours never touches theirs.
Add the YouTube step to your gate.
Toggle it on, paste your ID, and ship. Email capture works alongside it from the first unlock — owned from day one.