Questions, answered
Quick answers for buyers, portal admins, and IT.
FAQ
Can this be “HubSpot-only” (no external hosting)?
The user experience is “HubSpot-first”: your team opens the app from HubSpot’s app menu and views charts inside HubSpot. For security and reliability, the app uses a dedicated backend service to call HubSpot APIs, cache results briefly, and enforce licensing. If your IT policy requires it, we can deploy the backend into your cloud environment.
Where do users open the charts in HubSpot?
After installation, users open the app from HubSpot’s app menu. The App Home page shows a chart picker; selecting a chart opens it in a full-screen modal inside HubSpot.
Is it truly read-only?
Yes. Drag/resize/progress interactions are disabled. The app only reads data (campaigns, lists, contacts, deals).
Do you store our HubSpot data outside HubSpot?
We don’t copy your HubSpot CRM/marketing objects (campaigns, contacts, deals) into a database. Reports are computed on demand.
We do store a small amount of operational data required to run the app:
- Connection tokens (OAuth access/refresh) per portal so the portal stays connected. Tokens remain server-side (never exposed to the browser) and are stored encrypted at rest.
- Subscription metadata (plan, seat count, and Stripe identifiers) when billing is enabled.
- Seat assignments (HubSpot user IDs) when per-seat licensing is enabled.
What is cached, and for how long?
To keep the UI responsive and reduce HubSpot API calls, the backend uses short-lived caching (minutes). This may include:
- Campaign lists (IDs, names, status, and start/end dates)
- List search results (list IDs/names and sizes)
- Computed report outputs (aggregated counts and rates)
Cache duration is short and can be tuned for enterprise requirements.
Is anything stored in the user’s browser?
Yes—only UI preferences. We store filter selections (like date range/view) and metric settings (period/compare) in the browser so the app remembers your last view. This is stored locally in the user’s browser per portal.
How can we revoke access or request deletion?
Portal admins can revoke the app’s access from HubSpot at any time. If you want us to delete stored operational data for a portal (OAuth tokens, billing metadata, seat assignments), email support@fullstackmarketing.digital.
How is cost per lead calculated?
Cost per lead is computed as total marketing spend ÷ new leads created for the selected period. “New leads” uses the contact lifecycle stage lead date, and “spend” is read from a marketing campaign spend/budget field in HubSpot.
What happens if campaigns are missing dates?
Campaigns without start/end dates are listed separately so teams can fix data hygiene without breaking the chart.
Can you limit which portals can use it?
Yes. Access can be restricted to approved HubSpot portal IDs.