The new Growth Marketing Lead is hired to "bring visibility to parts of the funnel we can't see well today" and rank channels by ROI. Today the funnel can't see its biggest entry point: all seven sign-up links on the homepage (and the Spanish homepage) send a=, with nothing after it. Elsewhere the same tag is written four different ways: /signup and /signup/, slashes encoded twice (%252F) on blog, RPC and Dapp Store pages, two different values on one Dapp Store page, and a separate utm_ scheme in the docs. Any report that groups sign-ups by source page is splitting the same pages into several rows and dropping the homepage.
First action
Search the site code for "signup?a=" and list every template that builds the link.
How to measure it
Sign-ups with a valid, single-encoded source
- Now
- –
- Target
- 99%
- By
- 30 days
Steps
Inventory the links
Every template and component that builds a dashboard sign-up URL, including docs and Dapp Store.
Senior Software Engineer, Developer Experience 1 day
Agree the spec
One path, one source value per page, "home" for the homepage, utm_ fields passed through.
Growth Marketing Lead 1 day
Build one helper
A shared function used by website, docs and Dapp Store.
Senior Software Engineer, Developer Experience 2 days
Add a build check
Fail when a sign-up link has an empty or double-encoded source.
Senior Software Engineer, Developer Experience 1 day
Map the history
Decode %252F, merge variants and label empty values in the warehouse.
Senior Data Engineer 2 days
Rebuild the report
Sign-ups and first paid workloads by source page and channel.
Growth Marketing Lead 2 days
Check weekly
An alert when untagged sign-ups rise above 1%.
Senior Data Engineer weekly
Why it works
Write one sign-up link helper for the whole site: a single path (/signup), a single source value per page (the page path, "home" for /), encoded once, plus the utm_ fields from the visitor's landing URL carried through. Use it in the website, docs and Dapp Store templates. Then map the old values in the warehouse (decode %252F, merge the dapps/ and alternatives/ variants, label empty values as homepage) so history stays comparable, and add a test that fails a build when a sign-up link has an empty or double-encoded source.
Sign-up attribution is the base of the channel ROI ranking the role is asked to defend each half. Fixing it is a few hours of front-end work and makes every later test in this playbook measurable.
Ready to use
ChecklistSign-up link spec
[ ] One path: dashboard.alchemy.com/signup (no trailing slash) [ ] a = page path, encoded once; "home" for / [ ] Same helper on website, docs and Dapp Store [ ] utm_source / utm_medium / utm_campaign carried from the landing URL [ ] Agentic sign-ups tagged a=agent-<client> [ ] Build check: no empty or %252F values [ ] Warehouse mapping for old values
Risks and how to handle them
Old dashboards break when values change
Keep a mapping table so old and new values report together.
Agent sign-ups have no page at all
Give the agentic sign-up flow its own source value (see idea 7).
Evidence
- HiringGrowth Marketing Lead (San Francisco, posted September 28, 2026, $180K-$220K): owns "paid search, paid social, SEO, AEO, a lifecycle program we're just getting off the ground, and our website"; must "Own full-funnel visibility for Alchemy's growth motion, from self-serve signup through the enterprise sales flow, including the quality of leads reaching the sales team" and "bring visibility to parts of the funnel we can't see well today". Also: "Evaluate and evolve the existing tool stack and agencies: keep, renegotiate, or replace", with "an AI-powered SEO/AEO system already in production".Source
- Your websiteSign-up links checked twice on October 22, 2026: all seven "Get started" links on the homepage (and on the Spanish homepage) point to dashboard.alchemy.com/signup?a= with an empty source value; pricing mixes /signup?a=pricing and /signup/?a=pricing; blog, RPC and Dapp Store pages encode the slash twice (a=blog%252Fsolana-on-alchemy), one Dapp Store page uses both a=alternatives%252Fre and a=dapps%252Falternatives%252Fre, and the Alchemy vs QuickNode page uses both %252F and %2F; docs links use a different scheme (utm_source=docs with an empty utm_content) plus one untagged link.Source
- HiringProduct Lead, Developer Experience (posted August 26, 2026): "Self-serve is how Alchemy grows." The role owns "signup, app creation, first key, first call, usage and CU visibility, upgrade paths", aims to "Reduce time to first successful call, then time to first paid workload", and runs "pricing, packaging, and onboarding tests". "A growing share of developers now reach Alchemy through an AI coding agent rather than a browser tab"; the role owns how the MCP server, agent skills and machine-readable docs "perform inside Claude Code, Cursor, and whatever comes next".Source
- Your websiteSitemaps (checked October 22, 2026): 7,586 URLs in the main sitemaps plus about 14,900 Dapp Store pages; 1,070 pages in each of six languages (es, ja, ko, pt-BR, zh-Hans, zh-Hant); 330 overviews including Alchemy vs QuickNode (updated September 9, 2026), Infura, Chainstack, Ankr and Moralis, but no comparison with Helius despite more than 20 Solana blog posts; about 55 case studies filtered by chains, DeFi, gaming, NFTs, rollups and wallets, with no payments or fintech filter although Cash App, Slash, Pana and Allscale stories exist; 155 per-chain RPC pages and 28 chain-ranking pages.Source