portaly-analytics
Portaly Analytics Integration
Use this skill to help a Portaly creator install Google Analytics 4 on their website and connect it to Portaly. Keep answers operational: prefer step lists, code snippets, and copy-ready examples over long architecture explanations.
Quick Start
- First, ask the human user what they want to accomplish:
- Install GA4 on my website → Part A (steps 1–5)
- Connect GA to Portaly dashboard → Part B (step 6)
- Both → Part A + Part B (steps 1–6)
- Confirm what the human user is trying to build. Ask about their tech stack (Next.js / React / vanilla HTML) and whether they have an existing GA4 Property.
- Guide through GA4 setup and event tracking installation.
- If the user wants to see analytics in Portaly, guide through the Portaly authorization flow.
- Start with
references/ga4-setup-guide.mdfor installation instructions. - Return implementation-ready output. Prefer numbered steps, code samples, and copy-ready configuration.
More from portaly-ai/portaly-skills
portaly-user
Help users sync and manage their application users in Portaly Vibe, including initial migration, incremental sync, and dashboard viewing. Trigger when the user mentions Portaly user sync, user management, user synchronization, member sync, or wants to push user data to Portaly.
60portaly-payment
Help users integrate Portaly Vibe hosted payment checkout, including merchant setup, subscription plans, checkout sessions, and callback verification. Trigger when the user mentions Portaly Vibe payment, creator subscription, or wants to add subscription-based checkout to their application.
54portaly-sentry
Run a security and reliability health check on a Portaly Vibe payment integration before deployment. Trigger when the user mentions Portaly health check, payment security audit, pre-deploy check, sentry scan, callback verification audit, integration safety check, or wants to verify their Portaly payment integration is safe to go live.
49portaly-email
Help Portaly creators run follower-email campaigns end-to-end — create a draft, save and iterate on subject + HTML body, send it via Vibe MCP, read post-send analytics — and wire up where the invitation email's CTA redirects (Portaly-hosted waitlist, self-hosted /waitlist/[slug], or directly into the creator's existing register flow). Trigger when the user mentions invitation emails, follower outreach campaigns, sending an email blast to followers, drafting an email campaign, waitlist signup landing page, app base URL, embedding a waitlist CTA, skipping the waitlist when a member system already exists, or asks how the registration email link works / where it lands.
45