{
  "schemaVersion": "1.2.0",
  "schema": "https://hivesilo.com/evidence/company-fact-sheet.schema.json",
  "slug": "hubspot",
  "product": "HubSpot",
  "url": "https://hivesilo.com/integrations/hubspot",
  "title": "HubSpot Integration: Scored Buyers on the Contact Record | HiveSilo",
  "description": "HubSpot integration with HiveSilo: scored website buyers upserted to contact records through the documented CRM API, with scopes your administrator approves at install.",
  "reviewed": "2026-11-11",
  "connectionStatus": "available",
  "image": {
    "width": 1800,
    "height": 1195,
    "group": "crm",
    "alt": "Illustrative enterprise office at dusk for the HubSpot integration workflow",
    "heroVariants": [
      {
        "path": "/img/integrations/hubspot-integration-crm-480.854e22807114.webp",
        "width": 480,
        "height": 319,
        "bytes": 21216
      },
      {
        "path": "/img/integrations/hubspot-integration-crm-768.3a4946822424.webp",
        "width": 768,
        "height": 510,
        "bytes": 47770
      },
      {
        "path": "/img/integrations/hubspot-integration-crm-1200.742eae743649.webp",
        "width": 1200,
        "height": 797,
        "bytes": 98032
      },
      {
        "path": "/img/integrations/hubspot-integration-crm-1800.bc95e30e4f11.webp",
        "width": 1800,
        "height": 1195,
        "bytes": 169500
      }
    ],
    "socialImage": {
      "path": "/og/hubspot-integration-intelligence.7a1e96bb0f8a.png",
      "width": 1200,
      "height": 630,
      "bytes": 766603
    },
    "retiredSocialImages": [],
    "sourceSha256": "40f59dc928a0",
    "source": "AI-generated illustrative scene; not a vendor or customer facility",
    "illustrative": true
  },
  "content": {
    "inventoryId": "P702",
    "slug": "hubspot",
    "product": "HubSpot",
    "shortName": "HubSpot",
    "niche": "crm-platforms",
    "connectionStatus": "available",
    "reviewed": "2026-11-11",
    "contentVersion": "1.2.0",
    "title": "HubSpot Integration: Scored Buyers on the Contact Record | HiveSilo",
    "description": "HubSpot integration with HiveSilo: scored website buyers upserted to contact records through the documented CRM API, with scopes your administrator approves at install.",
    "primaryKeyword": "HubSpot integration",
    "secondaryKeywords": [
      "HubSpot lead scoring integration",
      "HubSpot contacts API upsert",
      "HubSpot buyer intent data",
      "HiveSilo HubSpot"
    ],
    "sources": [
      {
        "id": "P702-D01",
        "title": "HubSpot Developers: CRM API, Contacts guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-contacts-v3/guide",
        "supports": "POST /crm/v3/objects/contacts/batch/upsert creates or updates contacts matched by email or a custom unique identifier property; batch operations are limited to 100 records; partial upserts are not supported when email is the idProperty; the lifecyclestage property can only be set forward; the page lists the scopes crm.objects.contacts.read and crm.objects.contacts.write.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D02",
        "title": "HubSpot Developers: CRM API, Properties guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-properties-v3/guide",
        "supports": "A POST request to /crm/v3/properties/{objectType} creates a custom property with a groupName, type and fieldType; setting hasUniqueValue to true makes a unique identifier property, with up to ten per object; the scope list on the page includes crm.schemas.contacts.write.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D03",
        "title": "HubSpot Developers: Activities, Notes guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-notes-v3/guide",
        "supports": "A POST request to /crm/v3/objects/notes logs a note on a record timeline; hs_timestamp is required, hs_note_body is limited to 65,536 characters, and an associations object links the note to an existing record.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D04",
        "title": "HubSpot Developers: Authentication overview",
        "url": "https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/overview",
        "supports": "Apps distributed to multiple accounts must use OAuth, with the access token sent in the Bearer authorization header; a static auth access token serves a single account; private distribution allows installation in a maximum of 10 accounts at a time.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D05",
        "title": "HubSpot Developers: Scopes",
        "url": "https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/scopes",
        "supports": "Required scopes must be authorized by the user at install; OAuth apps can also declare conditionally required and optional scopes; the scopes an endpoint needs are listed in the Scope requirements section of its API guide.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D06",
        "title": "HubSpot Developers: API usage guidelines and limits",
        "url": "https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines",
        "supports": "Marketplace-distributed OAuth apps are limited to 110 requests every 10 seconds per installing account; privately distributed apps get 100 per 10 seconds per app on Free and Starter and 190 on Professional and Enterprise, with daily limits of 250,000, 625,000 and 1,000,000 per account; exceeding a limit returns a 429 response.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D07",
        "title": "HubSpot Developers: CRM API, Timeline events (legacy)",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-timeline-v3/guide",
        "supports": "The v1 and v3 timeline events APIs are only available for app partners with existing v1 or v3 timeline events defined in their public app.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D08",
        "title": "HubSpot Developers: App listing requirements in the HubSpot Marketplace",
        "url": "https://developers.hubspot.com/docs/apps/developer-platform/list-apps/listing-your-app/app-marketplace-listing-requirements",
        "supports": "A marketplace listing requires OAuth as the sole authorization method, at least three active, unique installs and a manual review by HubSpot. HiveSilo does not claim a marketplace listing.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D09",
        "title": "HubSpot Developers: CRM API, Companies guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-companies-v3/guide",
        "supports": "Company records store data about businesses; POST /crm/v3/objects/companies creates one and PATCH /crm/v3/objects/companies/{companyId} updates one; domain is the primary unique identifier to avoid duplicate companies; the scope list on the page shows crm.objects.companies.read and crm.objects.companies.write.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D10",
        "title": "HubSpot Developers: CRM API, Deals guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-deals-v3/guide",
        "supports": "Deals represent transactions with contacts or companies and are tracked through pipeline stages until they are won or lost; GET /crm/v3/objects/deals and GET /crm/v3/objects/deals/{dealId} retrieve them; the scope list on the page shows crm.objects.deals.read and crm.objects.deals.write.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D11",
        "title": "HubSpot Developers: Lists (Segments) API guide",
        "url": "https://developers.hubspot.com/docs/api-reference/crm-lists-v3/guide",
        "supports": "Lists, now called segments, have the processing types MANUAL, DYNAMIC and SNAPSHOT; a DYNAMIC list is processed by HubSpot so that a record is reevaluated against the list filters whenever it changes; the scope list shows crm.lists.read and crm.lists.write; the legacy v1 lists API was sunset as of April 30th, 2026.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D12",
        "title": "HubSpot Developers: HubSpot account types",
        "url": "https://developers.hubspot.com/docs/getting-started/account-types",
        "supports": "A standard HubSpot account can create up to 10 developer test accounts to test apps and integrations without affecting real HubSpot data; with an Enterprise subscription, a standard sandbox account copies the structure of the standard account for testing workflows and integrations.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "P702-D13",
        "title": "HubSpot Developers: Account activity API",
        "url": "https://developers.hubspot.com/docs/api-reference/account-audit-logs-v3/guide",
        "supports": "GET /account-info/v3/activity/security returns security activity including CRM exports, adding and removing users, and installing integrations; GET /account-info/v3/activity/audit-logs returns user actions including CRM object creation and property value updates and is available for Enterprise accounts only; the scope shown is account-info.security.read.",
        "reviewed": "2026-11-11"
      },
      {
        "id": "HSF1",
        "title": "HiveSilo capability overview",
        "url": "https://hivesilo.com/evidence/features.md",
        "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI governance, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
        "reviewed": "2026-11-11"
      }
    ],
    "hero": {
      "h1": "HubSpot. See which contacts arrived ready to buy.",
      "lede": "HubSpot holds your contacts, their lifecycle and their timeline. HiveSilo scores buying intent on your own website and writes the score, the tier and the reasons to the contact record through the CRM API HubSpot documents.",
      "imageLines": [
        "The contact you already have.",
        "The intent you could not see."
      ]
    },
    "problem": {
      "heading": "The contact exists. The buying evidence is thin.",
      "summary": "A HubSpot contact shows who someone is and what your team has done with them. How seriously they shopped your website before enquiring is harder to read from the record.",
      "question": "Which new contacts should a rep open first this morning?",
      "paragraphs": [
        "A form fill creates or updates a contact with an email address and a source. Two contacts can enter the same lifecycle stage on the same day while one shows strong buying intent and the other shows little. The rep sees two similar rows in a list.",
        "HubSpot offers its own scoring, lists and workflows, and those stay in charge. HiveSilo adds first-party evidence from your own website, scored for buying intent and screened for invalid traffic, and places it in contact properties your administrator creates, so your existing HubSpot tools can use it."
      ]
    },
    "value": {
      "heading": "Add buyer evidence to the properties your workflows already read.",
      "summary": "HiveSilo does not run your HubSpot automation. It supplies a score, a tier and a short explanation on the contact, and your lists, views and reports take it from there.",
      "decisions": [
        {
          "title": "Who gets the first call.",
          "body": "Sort new contacts by observed buying intent, next to the criteria you already use."
        },
        {
          "title": "What the rep should know.",
          "body": "Put a short reason for the score on the timeline before the conversation starts."
        },
        {
          "title": "Which sources earn their budget.",
          "body": "Compare campaigns by the buyers they send as well as by the contacts they create."
        }
      ],
      "capabilities": [
        {
          "heading": "One contact, kept current.",
          "body": "HiveSilo uses the batch upsert endpoint, matched on email or on a custom unique identifier property. HubSpot documents that existing contacts are updated and missing ones are created.",
          "output": "A single contact per buyer with a current score and tier.",
          "sourceIds": [
            "P702-D01",
            "P702-D02"
          ]
        },
        {
          "heading": "The reasons, on the timeline.",
          "body": "A short reason for the score and a suggested next step are logged as a note associated with the contact, which HubSpot shows on the record timeline for other users in the account.",
          "output": "A dated note on the contact that explains the score.",
          "sourceIds": [
            "P702-D03"
          ]
        },
        {
          "heading": "Properties you can filter and report on.",
          "body": "Score and tier live in custom contact properties, so they are available to the lists, views and reports you build in HubSpot.",
          "output": "A source and campaign comparison built in your own HubSpot reporting.",
          "sourceIds": [
            "P702-D02",
            "HS1"
          ]
        }
      ]
    },
    "integration": {
      "heading": "How HiveSilo connects to HubSpot",
      "statusNote": "The connection is activated for each client on request, inside that client's own HubSpot account, with the scopes and contact properties their administrator approves.",
      "intro": "Each row below names a route in HubSpot's public developer documentation. HiveSilo makes outbound calls to that API to write these records. In this workflow it does not read deals, lifecycle history or other records back, and it does not ask HubSpot to call into your systems.",
      "tableCaption": "What HiveSilo writes to HubSpot and the documented route for each item",
      "flows": [
        {
          "sends": "A buyer who identifies themselves on your website",
          "lands": "A contact record, created or updated",
          "route": "POST /crm/v3/objects/contacts/batch/upsert, with idProperty set to email or to a custom unique identifier property. Existing contacts are updated; others are created.",
          "sourceIds": [
            "P702-D01"
          ]
        },
        {
          "sends": "Buyer score and Tier 1, Tier 2 or Tier 3 qualification",
          "lands": "Custom contact properties your administrator approves",
          "route": "Properties are created with POST /crm/v3/properties/{objectType} and then set in the same upsert request body.",
          "sourceIds": [
            "P702-D01",
            "P702-D02"
          ]
        },
        {
          "sends": "A short reason for the score and a suggested next step",
          "lands": "A note on the contact's timeline",
          "route": "POST /crm/v3/objects/notes with hs_timestamp and hs_note_body, and an associations object that links the note to the contact.",
          "sourceIds": [
            "P702-D03"
          ]
        },
        {
          "sends": "Campaign and source context",
          "lands": "Contact properties alongside the score",
          "route": "The same upsert request. Batch operations are limited to 100 records per request.",
          "sourceIds": [
            "P702-D01",
            "P702-D02"
          ]
        }
      ],
      "facts": [
        {
          "label": "Access you grant",
          "body": "OAuth, with the access token sent as a Bearer header. HubSpot requires OAuth for an app installed in more than one account. The contacts and notes guides list crm.objects.contacts.read and crm.objects.contacts.write; the properties guide lists crm.schemas.contacts.write for creating properties.",
          "sourceIds": [
            "P702-D01",
            "P702-D02",
            "P702-D03",
            "P702-D04"
          ]
        },
        {
          "label": "Scopes are approved at install",
          "body": "Required scopes must be authorized by the installing user. OAuth apps can mark other scopes as conditionally required or optional, so the grant can match the features you switch on.",
          "sourceIds": [
            "P702-D05"
          ]
        },
        {
          "label": "Limits to plan for",
          "body": "HubSpot applies a per-10-second limit and, for privately distributed apps, a daily limit per account that rises from Free and Starter to Professional and Enterprise. A request over the limit returns a 429 response.",
          "sourceIds": [
            "P702-D06"
          ]
        },
        {
          "label": "Matching on email",
          "body": "HubSpot does not support partial upserts when email is the idProperty. A custom unique identifier property removes that restriction, and HubSpot allows up to ten such properties per object.",
          "sourceIds": [
            "P702-D01",
            "P702-D02"
          ]
        },
        {
          "label": "Deprecation to know",
          "body": "HubSpot limits its v1 and v3 timeline events APIs to app partners with existing events. HiveSilo uses notes and contact properties, which are current routes.",
          "sourceIds": [
            "P702-D07",
            "P702-D03"
          ]
        },
        {
          "label": "Test before production",
          "body": "HubSpot documents developer test accounts for testing apps and integrations without affecting real data. With an Enterprise subscription you can also create a standard sandbox account that copies the structure of your standard account.",
          "sourceIds": [
            "P702-D12"
          ]
        }
      ],
      "questionsHeading": "Who, what, when, where, how and why",
      "questions": [
        {
          "label": "Who",
          "body": "Teams that run HubSpot as their CRM and want sales to see buying intent from the company website. A HubSpot user with permission to install apps authorizes the scopes.",
          "sourceIds": [
            "P702-D05"
          ]
        },
        {
          "label": "What",
          "body": "A buyer score, a Tier 1, Tier 2 or Tier 3 qualification, a short reason for them, a suggested next step, and campaign and source context, written to the contact and to a note on its timeline.",
          "sourceIds": [
            "P702-D01",
            "P702-D03"
          ]
        },
        {
          "label": "When",
          "body": "When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes.",
          "sourceIds": [
            "HS1"
          ]
        },
        {
          "label": "Where",
          "body": "In your own HubSpot account, on the contact record your team already opens. No separate customer list is created for sales to check.",
          "sourceIds": [
            "P702-D01",
            "HS4"
          ]
        },
        {
          "label": "How",
          "body": "Outbound calls to the documented HubSpot CRM API, authorized with OAuth and matched on email or a unique identifier property.",
          "sourceIds": [
            "P702-D01",
            "P702-D04"
          ]
        },
        {
          "label": "Why",
          "body": "HubSpot knows the relationship and its history. HiveSilo knows how the buyer behaved on your website before they enquired. The rep sees both on one contact.",
          "sourceIds": [
            "HS1",
            "HS2"
          ]
        }
      ],
      "summary": "HubSpot is the CRM of record for your contacts, companies and deals. HiveSilo scores buying intent on your own website, screens invalid traffic and writes a Tier 1, Tier 2 or Tier 3 qualification to the contact through the CRM API HubSpot documents, under scopes your administrator approves at install. Customer identities stay in your HubSpot account and your own confidential environment.",
      "summarySourceIds": [
        "P702-D01",
        "HSF1",
        "HS4"
      ],
      "features": {
        "heading": "Where each HiveSilo capability meets HubSpot",
        "intro": "Each row pairs a published HiveSilo capability with the HubSpot feature it works with. Scope is agreed for each client. Rows that read from HubSpot need a separate read scope from your administrator.",
        "rows": [
          {
            "capability": "Buyer intelligence and three-tier qualification",
            "feature": "Contact records and custom contact properties, set through the batch upsert endpoint",
            "gain": "Owners see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the contact they already open.",
            "sourceIds": [
              "P702-D01",
              "P702-D02",
              "HSF1"
            ]
          },
          {
            "capability": "Business insights and oversight",
            "feature": "Lists (segments) with the DYNAMIC processing type",
            "gain": "A list your team filters on the qualification property is reevaluated by HubSpot when a contact changes, so views and reports follow the current tier.",
            "sourceIds": [
              "P702-D11",
              "HSF1"
            ]
          },
          {
            "capability": "AI firewall, bot defense and site protection",
            "feature": "Contact creation through the contacts API",
            "gain": "Invalid traffic is screened before it becomes a contact your team has to work.",
            "sourceIds": [
              "P702-D01",
              "HSF1"
            ]
          },
          {
            "capability": "AdBrain",
            "feature": "Custom contact properties that hold campaign and source context",
            "gain": "Your own HubSpot reports can compare campaigns by qualified demand as well as by contacts created.",
            "sourceIds": [
              "P702-D02",
              "HSF1"
            ]
          },
          {
            "capability": "Offline conversions, qualified-demand scaling and outcome measurement",
            "feature": "The lifecyclestage contact property and deals tracked through pipeline stages until won or lost",
            "gain": "With a read scope you grant, such as crm.objects.deals.read, won deals can inform the qualified-buyer feedback sent to supported advertising platforms.",
            "sourceIds": [
              "P702-D01",
              "P702-D10",
              "HSF1"
            ]
          },
          {
            "capability": "Revenue Seeker",
            "feature": "Contact, company and deal records already in your account",
            "gain": "With read scopes you grant, HubSpot can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records.",
            "sourceIds": [
              "P702-D09",
              "P702-D10",
              "HSF1"
            ]
          },
          {
            "capability": "AI Governance & Control",
            "feature": "Scopes authorized at install, and the security activity history in the account activity API",
            "gain": "The connection can do only what the installing user approved, a person decides the outreach, and your administrators can see integrations being installed in HubSpot's own activity history.",
            "sourceIds": [
              "P702-D05",
              "P702-D13",
              "HS6"
            ]
          },
          {
            "capability": "Client-controlled privacy and verification",
            "feature": "OAuth authorization for the app in your own account",
            "gain": "Customer identities stay in your HubSpot account and your confidential environment, outside HiveSilo's visibility.",
            "sourceIds": [
              "P702-D04",
              "HS4",
              "HSF1"
            ]
          }
        ]
      },
      "capture": {
        "heading": "How the buying signals are captured and linked",
        "paragraphs": [
          "Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors. HiveSilo scores those non-PII signals. Anything that could identify a person goes from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform.",
          "An anonymous session has a score but no HubSpot contact. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored contact is written to your HubSpot account from there."
        ],
        "sourceIds": [
          "HS3",
          "HS4"
        ]
      },
      "setup": {
        "heading": "What your HubSpot team does",
        "intro": "The connection is configuration in your HubSpot account plus activation on the HiveSilo side. These are the steps on your side.",
        "steps": [
          {
            "title": "Choose the matching property.",
            "body": "Decide whether contacts are matched on email or on a custom unique identifier property. HubSpot does not support partial upserts when email is the idProperty.",
            "sourceIds": [
              "P702-D01"
            ]
          },
          {
            "title": "Create the score and tier properties.",
            "body": "Add custom contact properties for the buyer score, the qualification and the source context, in HubSpot or through POST /crm/v3/properties/{objectType}. A unique identifier property is one created with hasUniqueValue set to true.",
            "sourceIds": [
              "P702-D02"
            ]
          },
          {
            "title": "Test in a test account or sandbox first.",
            "body": "HubSpot documents developer test accounts for testing integrations without affecting real data, and a standard sandbox account for Enterprise subscriptions. Check the property mapping and the timeline note there.",
            "sourceIds": [
              "P702-D12"
            ]
          },
          {
            "title": "Install the app and approve the scopes.",
            "body": "A HubSpot user installs the app through OAuth and authorizes its required scopes. Scopes for optional features can be left out of the grant.",
            "sourceIds": [
              "P702-D04",
              "P702-D05"
            ]
          },
          {
            "title": "Build a list on the qualification.",
            "body": "Create a DYNAMIC list filtered on the qualification property so that sales works from a segment HubSpot keeps current.",
            "sourceIds": [
              "P702-D11"
            ]
          },
          {
            "title": "Check API headroom.",
            "body": "HubSpot applies per-10-second and daily request limits that your other integrations share. Confirm the tier that applies to your account.",
            "sourceIds": [
              "P702-D06"
            ]
          }
        ],
        "timeline": "HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The HubSpot steps above run on your own change process.",
        "timelineSourceIds": [
          "HSF1"
        ]
      },
      "preview": {
        "heading": "What the contact owner sees",
        "note": "Illustrative example, not a HubSpot screen. Property names are chosen by your administrator. The score shown is HiveSilo's published specimen.",
        "sourceIds": [
          "HS8"
        ],
        "fields": [
          {
            "label": "Lifecycle stage",
            "value": "Lead"
          },
          {
            "label": "HiveSilo buyer score (custom property)",
            "value": "3,790 of 5,000"
          },
          {
            "label": "HiveSilo qualification (custom property)",
            "value": "Tier 1"
          },
          {
            "label": "HiveSilo source context (custom property)",
            "value": "Paid search, product comparison page"
          }
        ],
        "task": {
          "label": "Note on the contact timeline",
          "subject": "Call first: strong buying intent on the website",
          "body": "Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: call today."
        }
      }
    },
    "example": {
      "heading": "Two form fills before nine. Who gets the call?",
      "setup": "Illustrative workflow: two people submit the same enquiry form within an hour. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3.",
      "nativeBaseline": "HubSpot creates or updates both contacts, sets their lifecycle stage and runs the workflows and scoring you have configured. None of that changes.",
      "inputs": [
        "The contact as HubSpot holds it, with owner and original source.",
        "HiveSilo's score and tier for the website sessions behind each form fill.",
        "A short reason for each score, including any invalid-traffic concern."
      ],
      "decision": "The owner calls the Tier 1 buyer first and handles the second contact according to its lower score.",
      "output": "A contact whose properties show score and tier, with a timeline note that explains them.",
      "owner": "The contact owner in HubSpot decides the outreach. HiveSilo supplies evidence; it does not send messages on the owner's behalf in this workflow.",
      "hold": "Hold automated outreach when the score is low, a traffic-quality concern is unresolved or contact permission is unclear.",
      "record": "Record the outcome on the contact or deal in HubSpot as usual, so your own HubSpot reports can compare score with result. HiveSilo does not read that outcome back in this workflow.",
      "sourceIds": [
        "P702-D01",
        "P702-D03"
      ]
    },
    "governance": {
      "intro": "A score is advice for the contact owner. It is not an instruction to a workflow.",
      "example": "Decide in advance which HubSpot actions a score may start and which need a person. Setting a property is different from enrolling a contact in a sequence or changing its owner. Note that HubSpot only lets the lifecycle stage move forward through the API, so agree whether the connection may touch that property at all, and send anything outside the agreed scope to a named owner first."
    },
    "privacy": {
      "intro": "Your HubSpot contacts stay in your HubSpot account.",
      "detail": "The contact's identity is written to your own HubSpot account from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. The scopes approved at install bound what the connection can touch, and HubSpot's own user permissions continue to apply to everyone who reads the properties and notes."
    },
    "outcomes": {
      "intro": "Bring website buying evidence to the HubSpot contact, so the first call, the follow-up and the campaign review start from the same facts.",
      "panels": [
        "Sort new HubSpot contacts by observed buying intent before the first call.",
        "Find the campaigns and pages your strongest contacts share, then build more of them.",
        "Review spend on sources whose contacts score low and rarely reach a deal.",
        "Screen invalid traffic before it becomes a contact your team has to work.",
        "Revisit existing HubSpot contacts whose website behavior shows renewed interest."
      ]
    },
    "fit": {
      "intro": "Most useful where HubSpot is the CRM of record and the website is a material source of new contacts.",
      "good": [
        "Sales teams that work contacts and deals in HubSpot every day.",
        "Businesses with considered, higher-value purchases where calling the right buyer first matters.",
        "Teams able to name the properties and the decision a score should inform."
      ],
      "consider": [
        "HubSpot's own scoring and workflows may already answer the question for some teams.",
        "API limits differ by product tier and are shared with your other integrations.",
        "Matching on email alone does not allow partial upserts; a unique identifier property may be needed."
      ]
    },
    "connection": {
      "heading": "Agree the account, the properties and the scopes.",
      "paragraphs": [
        "Confirm your HubSpot product tier, the property used for matching, and the contact properties that will hold the score, tier and source context. The installing user authorizes only the scopes those writes need.",
        "The connection is available and is activated for each client on request. Public documentation establishes what the HubSpot API supports; your configured account, your agreements with HubSpot and your agreement with HiveSilo determine the scope that is switched on."
      ],
      "sourceIds": [
        "P702-D01",
        "P702-D02",
        "P702-D05",
        "HS10"
      ]
    },
    "faqs": [
      {
        "question": "Does HiveSilo connect to HubSpot?",
        "answer": "Yes. The HubSpot connection is available and is activated for each client on request. It uses HubSpot's documented CRM API with scopes your administrator approves.",
        "sourceIds": [
          "P702-D01",
          "HS2"
        ]
      },
      {
        "question": "Which HubSpot objects and features are in scope?",
        "answer": "Contacts, through the batch upsert endpoint, and notes associated with those contacts. Score and qualification go into custom contact properties your administrator approves, which your lists and reports can then use. Other objects, including companies and deals, are scoped for each client through the same documented CRM API and their own scopes.",
        "sourceIds": [
          "P702-D01",
          "P702-D02",
          "P702-D03",
          "P702-D09",
          "P702-D10",
          "P702-D11"
        ]
      },
      {
        "question": "Will it create duplicate contacts?",
        "answer": "The upsert matches on email or on a custom unique identifier property. HubSpot documents that a matching contact is updated and a new one is created only when none exists. HubSpot recommends always including email as the primary unique identifier.",
        "sourceIds": [
          "P702-D01"
        ]
      },
      {
        "question": "Which scopes does the connection need?",
        "answer": "HubSpot's contacts and notes guides list crm.objects.contacts.read and crm.objects.contacts.write. Creating custom contact properties by API falls under crm.schemas.contacts.write, or your administrator can create the properties in HubSpot.",
        "sourceIds": [
          "P702-D01",
          "P702-D02",
          "P702-D03"
        ]
      },
      {
        "question": "How is access granted, and can we test before production?",
        "answer": "Through OAuth. A HubSpot user installs the app and authorizes its required scopes, and API requests then carry an access token in the Bearer header. HubSpot documents developer test accounts, and a standard sandbox account for Enterprise subscriptions, so the mapping can be checked before your production account is connected.",
        "sourceIds": [
          "P702-D04",
          "P702-D05",
          "P702-D12"
        ]
      },
      {
        "question": "Does HiveSilo read data back from HubSpot?",
        "answer": "Not in this workflow. HiveSilo writes the score, the qualification and the note; comparing score with outcome happens in your own HubSpot reports. Reading deals or lifecycle outcomes would need a separate read scope that you choose to grant. Each write counts toward your HubSpot API limits, and batch upserts of up to 100 contacts per request keep the call count down.",
        "sourceIds": [
          "P702-D01",
          "P702-D06",
          "P702-D10"
        ]
      },
      {
        "question": "Does HubSpot already score contacts?",
        "answer": "HubSpot offers its own scoring, lists and workflows, and those remain in place. HiveSilo adds first-party evidence from your own website, including traffic-quality screening, to the same contact.",
        "sourceIds": [
          "HS1"
        ]
      },
      {
        "question": "Is HiveSilo listed in the HubSpot Marketplace?",
        "answer": "No listing or partnership is claimed. HubSpot sets its own requirements and review for marketplace listings. This connection is set up directly with your account using access you authorize.",
        "sourceIds": [
          "P702-D08"
        ]
      }
    ],
    "relationshipContext": {
      "privacyContext": "The contact's identity is written to your own HubSpot account from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. HubSpot scopes and user permissions continue to govern what the connection can write and who can read it.",
      "diagramLabels": [
        "Customer identities stay in your HubSpot account",
        "Permitted non-PII website signals and buyer scores",
        "HiveSilo: buyer score, tier and reasons"
      ],
      "reviewIntentSentences": [
        "A HubSpot review should start with the scoring, lists and workflows already configured in your account.",
        "A HubSpot review of the connection should confirm the scopes authorized at install and the contact properties it may write.",
        "When you review HubSpot with HiveSilo, ask which sales decision a website buyer score would change."
      ],
      "sourceIds": [
        "P702-D04",
        "P702-D05",
        "HS3",
        "HS4"
      ]
    }
  },
  "shared": {
    "privacyModel": "Customer identities and re-identifiable data stay in the customer-controlled environment; only permitted non-PII signals and scores cross the configured boundary. Account, billing and support records are separate.",
    "governanceSteps": [
      {
        "title": "Request",
        "detail": "An AI proposes an action"
      },
      {
        "title": "Check",
        "detail": "Policy and authority"
      },
      {
        "title": "Approve",
        "detail": "Named owner, when required"
      },
      {
        "title": "Act",
        "detail": "Within permitted scope"
      },
      {
        "title": "Record",
        "detail": "Keep the action, outcome and accountable owner traceable."
      }
    ],
    "outcomes": [
      {
        "value": "3,790",
        "prefix": "",
        "suffix": "of 5,000",
        "label": "UHNW buyer score",
        "note": "Illustrative score"
      },
      {
        "value": "4–6×",
        "prefix": "",
        "suffix": "",
        "label": "Reported conversion lift",
        "note": "Closed-revenue outcomes"
      },
      {
        "value": "31%",
        "prefix": "Up to",
        "suffix": "",
        "label": "Reported ad-spend savings",
        "note": "Bot and invalid-traffic filtering"
      },
      {
        "value": "99.9999%",
        "prefix": "",
        "suffix": "",
        "label": "Bot detection",
        "note": "Observed client results"
      },
      {
        "value": "5–21%",
        "prefix": "",
        "suffix": "",
        "label": "Revenue lift from existing data",
        "note": "HiveSilo-reported client results"
      }
    ],
    "outcomeContext": "Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary.",
    "botDetectionGoal": "99.9999999% is a goal, not an achieved result."
  },
  "sources": [
    {
      "id": "P702-D01",
      "title": "HubSpot Developers: CRM API, Contacts guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-contacts-v3/guide",
      "supports": "POST /crm/v3/objects/contacts/batch/upsert creates or updates contacts matched by email or a custom unique identifier property; batch operations are limited to 100 records; partial upserts are not supported when email is the idProperty; the lifecyclestage property can only be set forward; the page lists the scopes crm.objects.contacts.read and crm.objects.contacts.write.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D02",
      "title": "HubSpot Developers: CRM API, Properties guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-properties-v3/guide",
      "supports": "A POST request to /crm/v3/properties/{objectType} creates a custom property with a groupName, type and fieldType; setting hasUniqueValue to true makes a unique identifier property, with up to ten per object; the scope list on the page includes crm.schemas.contacts.write.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D03",
      "title": "HubSpot Developers: Activities, Notes guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-notes-v3/guide",
      "supports": "A POST request to /crm/v3/objects/notes logs a note on a record timeline; hs_timestamp is required, hs_note_body is limited to 65,536 characters, and an associations object links the note to an existing record.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D04",
      "title": "HubSpot Developers: Authentication overview",
      "url": "https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/overview",
      "supports": "Apps distributed to multiple accounts must use OAuth, with the access token sent in the Bearer authorization header; a static auth access token serves a single account; private distribution allows installation in a maximum of 10 accounts at a time.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D05",
      "title": "HubSpot Developers: Scopes",
      "url": "https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/scopes",
      "supports": "Required scopes must be authorized by the user at install; OAuth apps can also declare conditionally required and optional scopes; the scopes an endpoint needs are listed in the Scope requirements section of its API guide.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D06",
      "title": "HubSpot Developers: API usage guidelines and limits",
      "url": "https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines",
      "supports": "Marketplace-distributed OAuth apps are limited to 110 requests every 10 seconds per installing account; privately distributed apps get 100 per 10 seconds per app on Free and Starter and 190 on Professional and Enterprise, with daily limits of 250,000, 625,000 and 1,000,000 per account; exceeding a limit returns a 429 response.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D07",
      "title": "HubSpot Developers: CRM API, Timeline events (legacy)",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-timeline-v3/guide",
      "supports": "The v1 and v3 timeline events APIs are only available for app partners with existing v1 or v3 timeline events defined in their public app.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D08",
      "title": "HubSpot Developers: App listing requirements in the HubSpot Marketplace",
      "url": "https://developers.hubspot.com/docs/apps/developer-platform/list-apps/listing-your-app/app-marketplace-listing-requirements",
      "supports": "A marketplace listing requires OAuth as the sole authorization method, at least three active, unique installs and a manual review by HubSpot. HiveSilo does not claim a marketplace listing.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D09",
      "title": "HubSpot Developers: CRM API, Companies guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-companies-v3/guide",
      "supports": "Company records store data about businesses; POST /crm/v3/objects/companies creates one and PATCH /crm/v3/objects/companies/{companyId} updates one; domain is the primary unique identifier to avoid duplicate companies; the scope list on the page shows crm.objects.companies.read and crm.objects.companies.write.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D10",
      "title": "HubSpot Developers: CRM API, Deals guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-deals-v3/guide",
      "supports": "Deals represent transactions with contacts or companies and are tracked through pipeline stages until they are won or lost; GET /crm/v3/objects/deals and GET /crm/v3/objects/deals/{dealId} retrieve them; the scope list on the page shows crm.objects.deals.read and crm.objects.deals.write.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D11",
      "title": "HubSpot Developers: Lists (Segments) API guide",
      "url": "https://developers.hubspot.com/docs/api-reference/crm-lists-v3/guide",
      "supports": "Lists, now called segments, have the processing types MANUAL, DYNAMIC and SNAPSHOT; a DYNAMIC list is processed by HubSpot so that a record is reevaluated against the list filters whenever it changes; the scope list shows crm.lists.read and crm.lists.write; the legacy v1 lists API was sunset as of April 30th, 2026.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D12",
      "title": "HubSpot Developers: HubSpot account types",
      "url": "https://developers.hubspot.com/docs/getting-started/account-types",
      "supports": "A standard HubSpot account can create up to 10 developer test accounts to test apps and integrations without affecting real HubSpot data; with an Enterprise subscription, a standard sandbox account copies the structure of the standard account for testing workflows and integrations.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "P702-D13",
      "title": "HubSpot Developers: Account activity API",
      "url": "https://developers.hubspot.com/docs/api-reference/account-audit-logs-v3/guide",
      "supports": "GET /account-info/v3/activity/security returns security activity including CRM exports, adding and removing users, and installing integrations; GET /account-info/v3/activity/audit-logs returns user actions including CRM object creation and property value updates and is available for Enterprise accounts only; the scope shown is account-info.security.read.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HSF1",
      "title": "HiveSilo capability overview",
      "url": "https://hivesilo.com/evidence/features.md",
      "supports": "Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI governance, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope.",
      "reviewed": "2026-11-11"
    },
    {
      "id": "HS0",
      "title": "HiveSilo: industry coverage",
      "url": "https://hivesilo.com",
      "supports": "First-party description of buyer intelligence across 12 luxury niches.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS1",
      "title": "HiveSilo: platform",
      "url": "https://hivesilo.com/platform",
      "supports": "Published intent, sales-prioritization and traffic-quality capabilities.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS2",
      "title": "HiveSilo: integration scope",
      "url": "https://hivesilo.com/integrations",
      "supports": "Named destinations, scoped activation and customer-controlled dispatch.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS3",
      "title": "HiveSilo: security architecture",
      "url": "https://hivesilo.com/security-architecture",
      "supports": "Documented confidential processing, BYOK and customer control.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS4",
      "title": "HiveSilo: data handling",
      "url": "https://hivesilo.com/data-handling",
      "supports": "Customer identity custody, pseudonymous-data boundaries and separate account records.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS5",
      "title": "HiveSilo: published outcomes",
      "url": "https://hivesilo.com/case-studies",
      "supports": "Existing first-party outcomes material, with client-reported and illustrative descriptions.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS6",
      "title": "HiveSilo: AI agentic governance",
      "url": "https://hivesilo.com/ai-agentic-governance",
      "supports": "Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS7",
      "title": "HiveSilo: AI implementation layer",
      "url": "https://hivesilo.com/ai-implementation-layer",
      "supports": "Published combined implementation model for intelligence, confidential processing and AI governance.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS8",
      "title": "HiveSilo: bot-detection results and buyer-score specimen",
      "url": "https://hivesilo.com/",
      "supports": "The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS9",
      "title": "HiveSilo: owned-data revenue result briefing",
      "url": "https://hivesilo.com/contact",
      "supports": "HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows on 25 October 2026.",
      "reviewed": "2026-10-25"
    },
    {
      "id": "HS10",
      "title": "HiveSilo: enterprise agreements and responsibility",
      "url": "https://hivesilo.com/terms",
      "supports": "Signed enterprise agreements govern the engagement and take precedence over website summaries.",
      "reviewed": "2026-10-26"
    }
  ],
  "articleText": "Enterprise CRM & customer data HubSpot + HiveSilo Available View scope HiveSilo / Integrations / HubSpot HubSpot. See which contacts arrived ready to buy. HubSpot holds your contacts, their lifecycle and their timeline. HiveSilo scores buying intent on your own website and writes the score, the tier and the reasons to the contact record through the CRM API HubSpot documents. Contact HiveSilo Explore the fit Start with a conversation. No client records needed. The contact you already have. The intent you could not see. Your client list stays yours. The value AI control Your data What you could gain Let’s talk FAQs & evidence The contact exists. The buying evidence is thin. A HubSpot contact shows who someone is and what your team has done with them. How seriously they shopped your website before enquiring is harder to read from the record. Which new contacts should a rep open first this morning? A form fill creates or updates a contact with an email address and a source. Two contacts can enter the same lifecycle stage on the same day while one shows strong buying intent and the other shows little. The rep sees two similar rows in a list. HubSpot offers its own scoring, lists and workflows, and those stay in charge. HiveSilo adds first-party evidence from your own website, scored for buying intent and screened for invalid traffic, and places it in contact properties your administrator creates, so your existing HubSpot tools can use it. A HubSpot review should start with the scoring, lists and workflows already configured in your account. [P702-D04] [P702-D05] [HS3] [HS4] Add buyer evidence to the properties your workflows already read. HiveSilo does not run your HubSpot automation. It supplies a score, a tier and a short explanation on the contact, and your lists, views and reports take it from there. Talk through your use case Who gets the first call. Sort new contacts by observed buying intent, next to the criteria you already use. What the rep should know. Put a short reason for the score on the timeline before the conversation starts. Which sources earn their budget. Compare campaigns by the buyers they send as well as by the contacts they create. Available The connection is activated for each client on request, inside that client's own HubSpot account, with the scopes and contact properties their administrator approves. How HiveSilo connects to HubSpot HubSpot is the CRM of record for your contacts, companies and deals. HiveSilo scores buying intent on your own website, screens invalid traffic and writes a Tier 1, Tier 2 or Tier 3 qualification to the contact through the CRM API HubSpot documents, under scopes your administrator approves at install. Customer identities stay in your HubSpot account and your own confidential environment. [P702-D01] [HSF1] [HS4] What the contact owner sees Lifecycle stage Lead HiveSilo buyer score (custom property) 3,790 of 5,000 HiveSilo qualification (custom property) Tier 1 HiveSilo source context (custom property) Paid search, product comparison page Note on the contact timeline Call first: strong buying intent on the website Strong buying intent on your website this week. Traffic screened as genuine. Suggested next step: call today. Illustrative example, not a HubSpot screen. Property names are chosen by your administrator. The score shown is HiveSilo's published specimen. [HS8] What HiveSilo sends and the route HubSpot documents Each row below names a route in HubSpot's public developer documentation. HiveSilo makes outbound calls to that API to write these records. In this workflow it does not read deals, lifecycle history or other records back, and it does not ask HubSpot to call into your systems. What HiveSilo writes to HubSpot and the documented route for each item HiveSilo sends Where it lands in HubSpot Documented route A buyer who identifies themselves on your website A contact record, created or updated POST /crm/v3/objects/contacts/batch/upsert, with idProperty set to email or to a custom unique identifier property. Existing contacts are updated; others are created. [P702-D01] Buyer score and Tier 1, Tier 2 or Tier 3 qualification Custom contact properties your administrator approves Properties are created with POST /crm/v3/properties/{objectType} and then set in the same upsert request body. [P702-D01] [P702-D02] A short reason for the score and a suggested next step A note on the contact's timeline POST /crm/v3/objects/notes with hs_timestamp and hs_note_body, and an associations object that links the note to the contact. [P702-D03] Campaign and source context Contact properties alongside the score The same upsert request. Batch operations are limited to 100 records per request. [P702-D01] [P702-D02] Access you grant OAuth, with the access token sent as a Bearer header. HubSpot requires OAuth for an app installed in more than one account. The contacts and notes guides list crm.objects.contacts.read and crm.objects.contacts.write; the properties guide lists crm.schemas.contacts.write for creating properties. [P702-D01] [P702-D02] [P702-D03] [P702-D04] Scopes are approved at install Required scopes must be authorized by the installing user. OAuth apps can mark other scopes as conditionally required or optional, so the grant can match the features you switch on. [P702-D05] Limits to plan for HubSpot applies a per-10-second limit and, for privately distributed apps, a daily limit per account that rises from Free and Starter to Professional and Enterprise. A request over the limit returns a 429 response. [P702-D06] Matching on email HubSpot does not support partial upserts when email is the idProperty. A custom unique identifier property removes that restriction, and HubSpot allows up to ten such properties per object. [P702-D01] [P702-D02] Deprecation to know HubSpot limits its v1 and v3 timeline events APIs to app partners with existing events. HiveSilo uses notes and contact properties, which are current routes. [P702-D07] [P702-D03] Test before production HubSpot documents developer test accounts for testing apps and integrations without affecting real data. With an Enterprise subscription you can also create a standard sandbox account that copies the structure of your standard account. [P702-D12] Where each HiveSilo capability meets HubSpot Each row pairs a published HiveSilo capability with the HubSpot feature it works with. Scope is agreed for each client. Rows that read from HubSpot need a separate read scope from your administrator. Where each HiveSilo capability meets HubSpot HiveSilo capability HubSpot feature it works with What you gain Buyer intelligence and three-tier qualification Contact records and custom contact properties, set through the batch upsert endpoint Owners see a buyer score and a Tier 1, Tier 2 or Tier 3 qualification on the contact they already open. [P702-D01] [P702-D02] [HSF1] Business insights and oversight Lists (segments) with the DYNAMIC processing type A list your team filters on the qualification property is reevaluated by HubSpot when a contact changes, so views and reports follow the current tier. [P702-D11] [HSF1] AI firewall, bot defense and site protection Contact creation through the contacts API Invalid traffic is screened before it becomes a contact your team has to work. [P702-D01] [HSF1] AdBrain Custom contact properties that hold campaign and source context Your own HubSpot reports can compare campaigns by qualified demand as well as by contacts created. [P702-D02] [HSF1] Offline conversions, qualified-demand scaling and outcome measurement The lifecyclestage contact property and deals tracked through pipeline stages until won or lost With a read scope you grant, such as crm.objects.deals.read, won deals can inform the qualified-buyer feedback sent to supported advertising platforms. [P702-D01] [P702-D10] [HSF1] Revenue Seeker Contact, company and deal records already in your account With read scopes you grant, HubSpot can be one of the authorized sources searched for revenue opportunities, which go to your own salespeople. HiveSilo cannot see those records. [P702-D09] [P702-D10] [HSF1] AI Governance & Control Scopes authorized at install, and the security activity history in the account activity API The connection can do only what the installing user approved, a person decides the outreach, and your administrators can see integrations being installed in HubSpot's own activity history. [P702-D05] [P702-D13] [HS6] Client-controlled privacy and verification OAuth authorization for the app in your own account Customer identities stay in your HubSpot account and your confidential environment, outside HiveSilo's visibility. [P702-D04] [HS4] [HSF1] How the buying signals are captured and linked Lightweight first-party instrumentation on your own website reads pseudonymous behavior from your visitors. HiveSilo scores those non-PII signals. Anything that could identify a person goes from your website into your own per-tenant confidential enclave, not into HiveSilo's shared platform. An anonymous session has a score but no HubSpot contact. The link is made when the visitor identifies themselves on your website, for example through an enquiry form. That match happens inside your enclave, and the scored contact is written to your HubSpot account from there. [HS3] [HS4] What your HubSpot team does The connection is configuration in your HubSpot account plus activation on the HiveSilo side. These are the steps on your side. Choose the matching property. Decide whether contacts are matched on email or on a custom unique identifier property. HubSpot does not support partial upserts when email is the idProperty. [P702-D01] Create the score and tier properties. Add custom contact properties for the buyer score, the qualification and the source context, in HubSpot or through POST /crm/v3/properties/{objectType}. A unique identifier property is one created with hasUniqueValue set to true. [P702-D02] Test in a test account or sandbox first. HubSpot documents developer test accounts for testing integrations without affecting real data, and a standard sandbox account for Enterprise subscriptions. Check the property mapping and the timeline note there. [P702-D12] Install the app and approve the scopes. A HubSpot user installs the app through OAuth and authorizes its required scopes. Scopes for optional features can be left out of the grant. [P702-D04] [P702-D05] Build a list on the qualification. Create a DYNAMIC list filtered on the qualification property so that sales works from a segment HubSpot keeps current. [P702-D11] Check API headroom. HubSpot applies per-10-second and daily request limits that your other integrations share. Confirm the tier that applies to your account. [P702-D06] HiveSilo's published typical deployment is approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. The HubSpot steps above run on your own change process. [HSF1] Who, what, when, where, how and why Who Teams that run HubSpot as their CRM and want sales to see buying intent from the company website. A HubSpot user with permission to install apps authorizes the scopes. [P702-D05] What A buyer score, a Tier 1, Tier 2 or Tier 3 qualification, a short reason for them, a suggested next step, and campaign and source context, written to the contact and to a note on its timeline. [P702-D01] [P702-D03] When When a visitor identifies themselves on your website, for example through an enquiry form, and again when a returning buyer's score changes. [HS1] Where In your own HubSpot account, on the contact record your team already opens. No separate customer list is created for sales to check. [P702-D01] [HS4] How Outbound calls to the documented HubSpot CRM API, authorized with OAuth and matched on email or a unique identifier property. [P702-D01] [P702-D04] Why HubSpot knows the relationship and its history. HiveSilo knows how the buyer behaved on your website before they enquired. The rep sees both on one contact. [HS1] [HS2] See the intelligence behind the next move One contact, kept current. HiveSilo uses the batch upsert endpoint, matched on email or on a custom unique identifier property. HubSpot documents that existing contacts are updated and missing ones are created. [P702-D01] [P702-D02] Useful output: A single contact per buyer with a current score and tier. The reasons, on the timeline. A short reason for the score and a suggested next step are logged as a note associated with the contact, which HubSpot shows on the record timeline for other users in the account. [P702-D03] Useful output: A dated note on the contact that explains the score. Properties you can filter and report on. Score and tier live in custom contact properties, so they are available to the lists, views and reports you build in HubSpot. [P702-D02] [HS1] Useful output: A source and campaign comparison built in your own HubSpot reporting. Two form fills before nine. Who gets the call? Illustrative workflow: two people submit the same enquiry form within an hour. One shows strong buying intent and is qualified Tier 1; the other shows little and is Tier 3. Start with HubSpot HubSpot creates or updates both contacts, sets their lifecycle stage and runs the workflows and scoring you have configured. None of that changes. Bring the relevant context together The contact as HubSpot holds it, with owner and original source. HiveSilo's score and tier for the website sessions behind each form fill. A short reason for each score, including any invalid-traffic concern. Make the decision The owner calls the Tier 1 buyer first and handles the second contact according to its lower score. A useful output A contact whose properties show score and tier, with a timeline note that explains them. Keep responsibility clear The contact owner in HubSpot decides the outreach. HiveSilo supplies evidence; it does not send messages on the owner's behalf in this workflow. Hold and ask Hold automated outreach when the score is low, a traffic-quality concern is unresolved or contact permission is unclear. Record the outcome Record the outcome on the contact or deal in HubSpot as usual, so your own HubSpot reports can compare score with result. HiveSilo does not read that outcome back in this workflow. [P702-D01] [P702-D03] Require control before AI acts. A score is advice for the contact owner. It is not an instruction to a workflow. Decide in advance which HubSpot actions a score may start and which need a person. Setting a property is different from enrolling a contact in a sequence or changing its owner. Note that HubSpot only lets the lifecycle stage move forward through the API, so agree whether the connection may touch that property at all, and send anything outside the agreed scope to a named owner first. 1 Request An AI proposes an action 2 Check Policy and authority 3 Approve Named owner, when required 4 Act Within permitted scope 5 Record Keep the action, outcome and accountable owner traceable. Unclear authority? Hold the action. Resolve with the named, authorized owner before proceeding. Controls apply to actions routed through the configured HiveSilo boundary. Read the governance and escalation requirements Make accountable authorization a condition of putting AI to work. HiveSilo describes an operating layer that combines buyer intelligence, customer-data privacy and governance. Your deployment should establish the responsible owner and permitted scope before an agent can change records, contact buyers or trigger campaigns. HiveSilo documents policy checks before execution, default denial when authorization is unclear, human checkpoints, scoped stop controls and decision receipts. These controls apply to actions routed through its policy boundary. Keep decisions, required approvals and held actions traceable as the workflow progresses, then record the action, outcome and accountable owner. [HS6] [HS7] Who Identify the acting agent or person and name the business owner accountable for this workflow. What Define the action and permitted data categories before execution. Where Specify the approved system, destination and customer custody boundary. How Require an approved execution path, access scope and applicable policy checks. When Set the permitted conditions and approval validity; recheck authority before a held action resumes. Why Record the business purpose and the basis for allowing, denying or holding the action. An edge case should stop the affected action. For the deployment, require unresolved authority, an unapproved destination or an out-of-policy action to remain on hold. A timeout or unanswered approval request must not become permission to proceed. Who gets the question? Agree a named owner and authorized delegate for each workflow. A proposed responsibility model is: sales for buyer outreach and lead handling; marketing for campaign spend and audiences; security or privacy for data-access exceptions; the platform owner for connector or runtime changes. Test the escalation route. If no authorized reviewer is available, keep the action held. Named-owner routing is configured and demonstrated for each deployment. Governance covers actions routed through its configured boundary; external systems remain responsible for actions outside that scope. Make responsibility part of the AI rollout. Use the AI implementation layer to put policy checks, approval checkpoints and decision records around the actions in scope. Your enterprise agreement defines the legal responsibilities and any agreed liability allocation or transfer. [HS7] [HS10] Explore the AI implementation layer · How enterprise agreements govern the engagement Your client list stays yours. Your HubSpot contacts stay in your HubSpot account. Explore the security architecture Your client records stay with your business under HiveSilo’s published architecture. How your data stays under your control The contact's identity is written to your own HubSpot account from the environment you control. HiveSilo's shared platform receives permitted non-PII signals and scores. HubSpot scopes and user permissions continue to govern what the connection can write and who can read it. [P702-D04] [P702-D05] [HS3] [HS4] [HS4] Your controlled environment Customer identities stay in your HubSpot account Identities and re-identifiable records stay here. Your enclave. Your keys. Only permitted non-PII signals and scores Permitted non-PII website signals and buyer scores HiveSilo intelligence HiveSilo: buyer score, tier and reasons No customer identity transfer to HiveSilo. Published architecture. Confirm the data boundary for your deployment. Customer-controlled keys Documented BYOK options cover AWS, Azure and GCP. Review key ownership, revocation and the deployment's access policy with your security team. [HS3] Protected processing The architecture describes confidential computing and trusted execution environments. Request deployment-specific attestation and data-flow evidence for your CISO's review. [HS3] Scoped destinations and actions Agree which systems receive outputs and what actions are authorized. Keep identity handling within the documented customer boundary. [HS2] [HS4] Control through the full relationship Review permitted use, export, retention, deletion and offboarding terms. Customer-controlled keys are one control; they do not establish every contractual exit right. [HS3] [HS4] The contact's identity is written to your own HubSpot account from the environment you control. HiveSilo's shared platform works with permitted non-PII signals and scores. The scopes approved at install bound what the connection can touch, and HubSpot's own user permissions continue to apply to everyone who reads the properties and notes. A HubSpot review of the connection should confirm the scopes authorized at install and the contact properties it may write. [P702-D04] [P702-D05] [HS3] [HS4] Customer identity custody is separate from HiveSilo account, billing and support records. Re-identifiable pseudonymous data is not anonymous. What you could gain. Bring website buying evidence to the HubSpot contact, so the first call, the follow-up and the campaign review start from the same facts. Explore HiveSilo case studies Contact HiveSilo Select a benefit to explore Pause rotation Buyer scoring Scale winners Less waste Bot protection Find revenue 3,790 of 5,000 · UHNW buyer score 3 , 7 9 0 of 5,000 Illustrative score 4–6× · Reported conversion lift 4 – 6 × Closed-revenue outcomes Up to 31% · Reported ad-spend savings Up to 3 1 % Bot and invalid-traffic filtering 99.9999% · Bot detection 9 9 . 9 9 9 9 % Observed client results 5–21% · Revenue lift from existing data 5 – 2 1 % HiveSilo-reported client results Sharper scoring. Clearer intent. 3,790 of 5,000 · UHNW buyer score Illustrative score Sort new HubSpot contacts by observed buying intent before the first call. Find more clients like your best. 4–6× · Reported conversion lift Closed-revenue outcomes Find the campaigns and pages your strongest contacts share, then build more of them. Put more of your budget to work. Up to 31% · Reported ad-spend savings Bot and invalid-traffic filtering Review spend on sources whose contacts score low and rarely reach a deal. Keep evolving your protection. 99.9999% · Bot detection Observed client results Screen invalid traffic before it becomes a contact your team has to work. Goal, not an achieved result: toward 99.9999999% bot detection as the hive evolves. Observed client results vary. Find revenue in data you already own. 5–21% · Revenue lift from existing data HiveSilo-reported client results Revisit existing HubSpot contacts whose website behavior shows renewed interest. Published outcomes include client-reported results and illustrative, unaudited ranges. The owned-data revenue range was supplied by HiveSilo; request the measurement context in your briefing. Results vary. Measure what matters Define the result. Then require the evidence. Focus on better-directed follow-up, less acquisition waste, protected customer identity custody and accountable AI execution. Agree the baseline, success measures and scope for your business. CEO: a clearer decision about the opportunities that merit attention. CFO: an agreed baseline, evaluation costs and attributable outcomes before any ROI claim. CTO: a demonstrated, permitted connection and a usable handoff into the agreed system. CISO: verified identity custody and pre-action authorization, with tested hold, approval and revocation behavior. Explore HiveSilo’s published outcomes and the measurement context behind them. [HS5] [HS8] [HS9] Make your next conversation count. Bring your HubSpot workflow. Map the decision, the data you control and a measurable next step with HiveSilo. Enterprise CRM & customer data · Sales, marketing operations, technology & security Contact HiveSilo Mention HubSpot and your business question. No client records or credentials. A closer look, when you need it. Product scope, a practical workflow and source-backed answers for your team and its research tools. Read fact sheet Structured JSON RSS updates Reviewed November 2026 Contact HiveSilo HubSpot connection & briefing scope Agree the account, the properties and the scopes. Confirm your HubSpot product tier, the property used for matching, and the contact properties that will hold the score, tier and source context. The installing user authorizes only the scopes those writes need. The connection is available and is activated for each client on request. Public documentation establishes what the HubSpot API supports; your configured account, your agreements with HubSpot and your agreement with HiveSilo determine the scope that is switched on. When you review HubSpot with HiveSilo, ask which sales decision a website buyer score would change. [P702-D04] [P702-D05] [HS3] [HS4] [P702-D01] [P702-D02] [P702-D05] [HS10] A useful fit when Most useful where HubSpot is the CRM of record and the website is a material source of new contacts. Sales teams that work contacts and deals in HubSpot every day. Businesses with considered, higher-value purchases where calling the right buyer first matters. Teams able to name the properties and the decision a score should inform. Consider the fit HubSpot's own scoring and workflows may already answer the question for some teams. API limits differ by product tier and are shared with your other integrations. Matching on email alone does not allow partial upserts; a unique identifier property may be needed. In your enquiry, name HubSpot and the business decision. Please leave out client records, credentials and sensitive samples. Eight questions before your briefing 1. Does HiveSilo connect to HubSpot? Yes. The HubSpot connection is available and is activated for each client on request. It uses HubSpot's documented CRM API with scopes your administrator approves. [P702-D01] [HS2] 2. Which HubSpot objects and features are in scope? Contacts, through the batch upsert endpoint, and notes associated with those contacts. Score and qualification go into custom contact properties your administrator approves, which your lists and reports can then use. Other objects, including companies and deals, are scoped for each client through the same documented CRM API and their own scopes. [P702-D01] [P702-D02] [P702-D03] [P702-D09] [P702-D10] [P702-D11] 3. Will it create duplicate contacts? The upsert matches on email or on a custom unique identifier property. HubSpot documents that a matching contact is updated and a new one is created only when none exists. HubSpot recommends always including email as the primary unique identifier. [P702-D01] 4. Which scopes does the connection need? HubSpot's contacts and notes guides list crm.objects.contacts.read and crm.objects.contacts.write. Creating custom contact properties by API falls under crm.schemas.contacts.write, or your administrator can create the properties in HubSpot. [P702-D01] [P702-D02] [P702-D03] 5. How is access granted, and can we test before production? Through OAuth. A HubSpot user installs the app and authorizes its required scopes, and API requests then carry an access token in the Bearer header. HubSpot documents developer test accounts, and a standard sandbox account for Enterprise subscriptions, so the mapping can be checked before your production account is connected. [P702-D04] [P702-D05] [P702-D12] 6. Does HiveSilo read data back from HubSpot? Not in this workflow. HiveSilo writes the score, the qualification and the note; comparing score with outcome happens in your own HubSpot reports. Reading deals or lifecycle outcomes would need a separate read scope that you choose to grant. Each write counts toward your HubSpot API limits, and batch upserts of up to 100 contacts per request keep the call count down. [P702-D01] [P702-D06] [P702-D10] 7. Does HubSpot already score contacts? HubSpot offers its own scoring, lists and workflows, and those remain in place. HiveSilo adds first-party evidence from your own website, including traffic-quality screening, to the same contact. [HS1] 8. Is HiveSilo listed in the HubSpot Marketplace? No listing or partnership is claimed. HubSpot sets its own requirements and review for marketplace listings. This connection is set up directly with your account using access you authorize. [P702-D08] Sources, scope & verification HubSpot Developers: CRM API, Contacts guide [P702-D01] POST /crm/v3/objects/contacts/batch/upsert creates or updates contacts matched by email or a custom unique identifier property; batch operations are limited to 100 records; partial upserts are not supported when email is the idProperty; the lifecyclestage property can only be set forward; the page lists the scopes crm.objects.contacts.read and crm.objects.contacts.write. Reviewed November 2026 HubSpot Developers: CRM API, Properties guide [P702-D02] A POST request to /crm/v3/properties/{objectType} creates a custom property with a groupName, type and fieldType; setting hasUniqueValue to true makes a unique identifier property, with up to ten per object; the scope list on the page includes crm.schemas.contacts.write. Reviewed November 2026 HubSpot Developers: Activities, Notes guide [P702-D03] A POST request to /crm/v3/objects/notes logs a note on a record timeline; hs_timestamp is required, hs_note_body is limited to 65,536 characters, and an associations object links the note to an existing record. Reviewed November 2026 HubSpot Developers: Authentication overview [P702-D04] Apps distributed to multiple accounts must use OAuth, with the access token sent in the Bearer authorization header; a static auth access token serves a single account; private distribution allows installation in a maximum of 10 accounts at a time. Reviewed November 2026 HubSpot Developers: Scopes [P702-D05] Required scopes must be authorized by the user at install; OAuth apps can also declare conditionally required and optional scopes; the scopes an endpoint needs are listed in the Scope requirements section of its API guide. Reviewed November 2026 HubSpot Developers: API usage guidelines and limits [P702-D06] Marketplace-distributed OAuth apps are limited to 110 requests every 10 seconds per installing account; privately distributed apps get 100 per 10 seconds per app on Free and Starter and 190 on Professional and Enterprise, with daily limits of 250,000, 625,000 and 1,000,000 per account; exceeding a limit returns a 429 response. Reviewed November 2026 HubSpot Developers: CRM API, Timeline events (legacy) [P702-D07] The v1 and v3 timeline events APIs are only available for app partners with existing v1 or v3 timeline events defined in their public app. Reviewed November 2026 HubSpot Developers: App listing requirements in the HubSpot Marketplace [P702-D08] A marketplace listing requires OAuth as the sole authorization method, at least three active, unique installs and a manual review by HubSpot. HiveSilo does not claim a marketplace listing. Reviewed November 2026 HubSpot Developers: CRM API, Companies guide [P702-D09] Company records store data about businesses; POST /crm/v3/objects/companies creates one and PATCH /crm/v3/objects/companies/{companyId} updates one; domain is the primary unique identifier to avoid duplicate companies; the scope list on the page shows crm.objects.companies.read and crm.objects.companies.write. Reviewed November 2026 HubSpot Developers: CRM API, Deals guide [P702-D10] Deals represent transactions with contacts or companies and are tracked through pipeline stages until they are won or lost; GET /crm/v3/objects/deals and GET /crm/v3/objects/deals/{dealId} retrieve them; the scope list on the page shows crm.objects.deals.read and crm.objects.deals.write. Reviewed November 2026 HubSpot Developers: Lists (Segments) API guide [P702-D11] Lists, now called segments, have the processing types MANUAL, DYNAMIC and SNAPSHOT; a DYNAMIC list is processed by HubSpot so that a record is reevaluated against the list filters whenever it changes; the scope list shows crm.lists.read and crm.lists.write; the legacy v1 lists API was sunset as of April 30th, 2026. Reviewed November 2026 HubSpot Developers: HubSpot account types [P702-D12] A standard HubSpot account can create up to 10 developer test accounts to test apps and integrations without affecting real HubSpot data; with an Enterprise subscription, a standard sandbox account copies the structure of the standard account for testing workflows and integrations. Reviewed November 2026 HubSpot Developers: Account activity API [P702-D13] GET /account-info/v3/activity/security returns security activity including CRM exports, adding and removing users, and installing integrations; GET /account-info/v3/activity/audit-logs returns user actions including CRM object creation and property value updates and is available for Enterprise accounts only; the scope shown is account-info.security.read. Reviewed November 2026 HiveSilo capability overview [HSF1] Published HiveSilo capabilities: buyer intelligence with Tier 1, Tier 2 and Tier 3 qualification, Revenue Seeker, AdBrain, offline conversion feedback, AI governance, bot defense, business insights and client-controlled privacy; typical deployment of approximately 72 hours to set up and 7 days to live mapping and go-live, subject to fit, customer readiness and agreed scope. Reviewed November 2026 HiveSilo: industry coverage [HS0] First-party description of buyer intelligence across 12 luxury niches. Reviewed October 2026 HiveSilo: platform [HS1] Published intent, sales-prioritization and traffic-quality capabilities. Reviewed October 2026 HiveSilo: integration scope [HS2] Named destinations, scoped activation and customer-controlled dispatch. Reviewed October 2026 HiveSilo: security architecture [HS3] Documented confidential processing, BYOK and customer control. Reviewed October 2026 HiveSilo: data handling [HS4] Customer identity custody, pseudonymous-data boundaries and separate account records. Reviewed October 2026 HiveSilo: published outcomes [HS5] Existing first-party outcomes material, with client-reported and illustrative descriptions. Reviewed October 2026 HiveSilo: AI agentic governance [HS6] Published pre-action policy checks, default denial, human checkpoints, scoped stop controls and governance receipts. Reviewed October 2026 HiveSilo: AI implementation layer [HS7] Published combined implementation model for intelligence, confidential processing and AI governance. Reviewed October 2026 HiveSilo: bot-detection results and buyer-score specimen [HS8] The homepage presents 99.9999% bot detection as observed client results, 99.9999999% as a goal, and a 3,790-of-5,000 UHNW buyer-score specimen. Reviewed October 2026 HiveSilo: owned-data revenue result briefing [HS9] HiveSilo supplied a 5–21% client revenue increase range for existing-data workflows in October 2026. Reviewed October 2026 HiveSilo: enterprise agreements and responsibility [HS10] Signed enterprise agreements govern the engagement and take precedence over website summaries. Reviewed October 2026 Vendor sources describe their own product. The workflows on this page describe a HiveSilo application, scoped to customer permissions, contracts and the selected product edition. HiveSilo’s reported outcomes retain their original measurement context; the illustrative score and future bot-detection goal are identified in the outcomes section. Independent HiveSilo use-case page. HubSpot is identified to explain the workflow; no endorsement, certification or partnership is implied. Your next move starts with a conversation. Contact HiveSilo"
}
