The intel layer behind
Fruition's client work.
MKT.fru.io is the internal platform our strategists and marketers use to assess digital presence, track AI visibility, manage portfolios, and ship content audits — built by Fruition.
Extracted from FCP
The four marketing tools used to live inside FCP. Pulled out so client-services has its own surface, faster iteration, and a domain marketers recognize.
Same database as FCP
Shares the fru_retool Postgres (Neon). One source of truth for sites, launches, audits, and AVA runs across the company.
For Fruition, by Fruition
Not a product. Internal leverage on the work the team already does — strategy, audits, AI visibility — so insights compound across clients.
What lives here
Four marketing surfaces — Assessments, AI Visibility (AVA), Portfolio, and Content Audit — plus the integrations that feed them: GA4, Search Console, PageSpeed, Semrush, and direct queries against Claude, ChatGPT, Gemini, Perplexity, and Grok.
How it fits with FCP
FCP remains the integration hub and source of truth. MKT.fru.io owns the marketing frontend and its API surface, but reads and writes the same database, and calls into FCP services (Puppeteer, etc.) when it needs to. Same login, same data, different workspace.
Who can sign in
Fruition staff (@fruition.net) via Auth0 SSO, plus approved guest accounts. If you think you should have access and don't, ping the team in Slack.