--- title: "Wire HubSpot into your warehouse without breaking attribution - Stacksync CRM" description: "How to keep model lineage clean when HubSpot becomes both source and sink." canonical: https://www.stacksync.com/crm/hubspot-warehouse-without-breaking-attribution last_modified: 2026-06-03 --- # Wire HubSpot into your warehouse without breaking attribution > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Once your warehouse starts writing back to HubSpot, the lineage your attribution model depends on starts to drift. This is how to keep both sides honest. Author Ruben Burdin · Founder & CEO Published June 3, 2026 Read time 11 min CRM ## Tag lineage before anything else The first thing to set up, before any data moves, is a `source_system` tag on every field in the warehouse. Fields that came from HubSpot get tagged `hubspot`. Fields that came from product analytics get tagged `amplitude`. Computed fields get tagged `derived/`. This is the single piece of metadata that lets your attribution model exclude reverse-ETL fields without code. Why this is the first move Once data is flowing both ways, you cannot retroactively tell which fields are real and which are derived. Tagging at ingestion is free. Tagging after the fact is impossible. ## What to write back to HubSpot - and what not to Two kinds of fields belong in HubSpot: data the sales team needs to act on (account tier, product usage signals, churn risk) and data the marketing automation needs to segment on (lifecycle stage, last activity from product). Everything else, model scores, raw event counts, historical state, stays in the warehouse. - Write back named, business-meaningful fields. Don't write back column names. - Write back at most daily. Real-time write-back is rarely useful and frequently triggers workflow loops. - Never write back into a HubSpot property that's also a workflow input unless you've audited every workflow that reads it. Two systems, one record, no batch window See your own stack synced live. Book a demo with the engineers who built it. [Book a demo](https://www.stacksync.com/book-a-demo) ## Keep the attribution model on a diet Once warehouse fields land in HubSpot, the temptation is to feed them straight into the attribution model. Don't. The attribution model's job is to explain what HubSpot saw, not what your warehouse already knows. Treat the warehouse-derived fields as decoration in the CRM and as inputs to a separate revenue model that runs on the warehouse. Run two models, in two places, with two purposes. They'll disagree at the edges. That disagreement is the most useful signal you have, it tells you where HubSpot's lifecycle is lagging the actual customer state. Suppressing it by merging them is how attribution becomes superstition. Start with one sync and see it hold Connect two systems, watch a record move both ways, then decide. [Start syncing](https://app.stacksync.com/) FAQ ## Frequently asked questions Won't writing computed fields back into HubSpot break my marketing attribution? Only if the computed field is treated by the model as native HubSpot data. Tag every reverse-ETL field with a source_system property at ingestion, exclude reverse-ETL fields from the attribution input set, and the model stays honest. The mistake is failing to mark the field, not the act of writing it back. Should we use HubSpot's webhooks or polling for the warehouse-side feed? Webhooks for everything that has them (contact, company, deal lifecycle changes). Polling for object types HubSpot doesn't yet emit webhooks for. The hybrid is normal; the goal is to keep both feeds in a single ordered event log on the warehouse side so the downstream model doesn't need to know which mechanism delivered each event. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync More CRM insights ## Related insights [All articles](https://www.stacksync.com/crm) [CRM Real-time CRM sync, explained without the marketing layer 9 min read](https://www.stacksync.com/crm/real-time-crm-sync-explained) [CRM Field-level mapping across CRM, ERP and warehouse 12 min read](https://www.stacksync.com/crm/field-level-mapping-crm-erp-warehouse) [CRM Sync Salesforce to Postgres bidirectionally in under 30 minutes 15 min read](https://www.stacksync.com/crm/salesforce-postgres-bidirectional-sync) ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)