Context gets lost
Campaign IDs, project ownership and conversion definitions drift when every tool carries its own model.
Shared growth infrastructure
Platform foundation live · product capabilities varySee the journey. Keep every growth tool in context.
MarkenGroup Cloud gives email, first-party attribution and future social publishing one shared project context—so teams can connect touchpoints to outcomes without rebuilding identity and permissions for every tool.
01Acquisition→02Visit→03Session→04Lead→05Engagement→06Return visit→07Conversion→08Revenue
The cost of disconnected tools
Your tools see channels. Your business needs the journey.
A click dashboard, an email sender and a social scheduler can each look healthy while nobody can explain which touchpoint produced a signup, purchase or return visit.
Control gets duplicated
Separate accounts, team access and credentials create more places for permissions and secrets to go wrong.
Activity replaces outcomes
Clicks, opens and reach become the answer because the journey to conversion was never connected.
Three focused layers
One control layer. Three distinct jobs.
Choose the product that solves the immediate problem. Keep the same organization and project when the journey spans more than one channel.
Preview
Email activation
Move from message intent to trustworthy delivery and outcome evidence without exposing email secrets in the browser.
First-party attribution
Mirror authorized Ads hierarchies without duplicate campaign setup, then explain outcomes with guarded CTR, CPC, CPM, ROAS and CAC.
Planned
Attributed social publishing
Carry a post's campaign context from publication to session, conversion and revenue.
The mechanism
Activation creates the touchpoint. Attribution explains the outcome.
TrackMailer is the email activation layer. TrackAny.Click is the first-party data and attribution layer. TrackPost is the planned social activation layer. The shared Cloud context keeps the boundaries explicit.
Read documentation ↗Email activation
Prepare recipients, sender identity and message intent. Customer delivery and delivery events are not active yet.
First-party attribution
Preserve campaign, session, event and outcome context. The collector and Ads mirror are prepared locally but not deployed or provider-accepted.
Social activation
Planned publishing will carry measurable campaign context into the same journey.
The architecture is unified; product data and permissions remain separated.
Built for developers who ship with AI
Your coding agent should read the contract—not invent the infrastructure.
Stable terms, crawlable status pages and copyable contracts give Codex, ChatGPT, Claude and other coding agents a factual source of truth. When a public endpoint does not exist, the docs say so.
Add email infrastructure to this Firebase project.Start from the sender, audience and Sandbox contracts without exposing a server secret in React.
Design attribution for every signup source.Define campaign IDs, sessions and conversion events before wiring a collector.
Explain which product is ready today.Read explicit Available, Sandbox, Preview and Coming soon states from the same public source.
Shared control plane
Shared context without shared access.
The platform foundation removes repeated account plumbing while preserving product and tenant boundaries.
One identity
A person uses one Firebase Auth identity across the Cloud Services family.
Organizations and projects
Teams group work by organization and keep each website, shop or brand in the project that owns its data.
Explicit permissions
Active membership, project context, product entitlement and server-side permissions are checked separately.
Separated product data
Shared IDs connect context; they do not grant one product direct access to another product's private data.
Concrete architecture
Infrastructure earns trust by showing its boundaries.
There are no invented compliance badges or vague security claims here—only mechanisms that exist in the current architecture.
Verified identityCore operations require a verified email address and active organization membership.
Project-scoped accessProduct reads and writes are checked against the selected project and entitlement on the server.
No customer-domain Firebase writesCustomer websites use product ingress boundaries; they never write product events directly to Firebase.
Secrets stay server-sidePrivate credentials are not placed in VITE_* configuration, browser examples or public documentation.
Straight answers
Know the boundary before you build.
What is MarkenGroup Cloud?
It is the shared control layer for organizations, projects, teams and the TrackMailer, TrackAny.Click and TrackPost product family. Each product keeps its own data and availability.
Are all three products available?
No. The Cloud workspace is live. TrackMailer has a live workspace and audience foundation without customer delivery, TrackAny.Click is a local release candidate with no public collector deployment, and TrackPost is coming soon.
Can I use the platform with React, Firebase or an AI coding agent?
Yes for the documented platform and preview workflows. Use the public docs as the source of truth and do not let an agent guess endpoints, credentials or unavailable capabilities.
Start with the project that owns the journey.
Open the shared workspace, then choose the product whose current status matches the work you need to do.