Skip to content
English
Submit a request
  • There are no suggestions because the search field is empty.

Engagement Insights: HubSpot Integration

Dispatching microapp session data to HubSpot CRM as engagement signals

1. Purpose & Scope

This article documents the first CRM integration for Tiled engagement signals, released in v60.0.0. Session data generated from microapp interactions is now dispatchable to a connected HubSpot CRM instance, enabling sales and marketing teams to act on real-time engagement intelligence.

Scope: Tiled customers with HubSpot CRM accounts who have enabled the integration. Applicable to Library Administrators responsible for integration configuration and Data Privacy Officers reviewing personal data transfer controls.

2. Control Objective

The control objective is to ensure that microapp session engagement data is transmitted to HubSpot accurately, completely, and only when authorized by the account administrator. The integration must not transmit data in excess of what is necessary for the stated business purpose (data minimization), and transmission must occur over secure channels.

3. Integration Architecture

The HubSpot integration consists of four components shipped in v60.0.0:

Session Data Dispatcher (TD-6720)

Captures microapp session events from the Tiled platform and queues them for dispatch.

Integration Session Orchestrator (TD-6721)

Manages routing logic — determines which sessions qualify for CRM dispatch based on configuration.

HubSpot Dispatch (TD-6723)

Handles authenticated API calls to the HubSpot endpoint, including payload formatting and error handling.

Session Dispatch Configuration (TD-6725)

UI and backend configuration allowing administrators to connect HubSpot, map fields, and control dispatch scope.

4. Configuration Procedures

4.1 Connect HubSpot Account

  1.     From the Tiled Library, navigate to Settings > Integrations.
  2.     Locate the HubSpot section and click Connect.
  3.     Authenticate with your HubSpot account credentials. Tiled will request the minimum required OAuth scopes.
  4.     Upon successful connection, the integration status will display as Active.

4.2 Configure Session Dispatch

  1.     Within the HubSpot integration settings, configure Session Dispatch using the options provided.
  2.     Define which microapps or microapp categories should dispatch session data.
  3.     Map Tiled session fields (e.g., recipient email, session duration, page views) to HubSpot contact or engagement properties.
  4.     Save the configuration. Session dispatch will begin for newly recorded sessions after the configuration is saved.

5. Data Fields Transmitted

Recipient Email

Used to identify or create a HubSpot contact record. Must match the email captured at share or session level.

Session Timestamp

Start time of the microapp engagement session.

Microapp Identifier

The Tiled microapp name or ID associated with the session.

Session Duration

Total time the recipient spent in the microapp session.

Page / Screen Views

Number of pages or states visited within the microapp during the session.

 

Note: Only session data for microapps configured for dispatch will be transmitted. Data minimization is enforced at the configuration layer. Tiled does not transmit financial, health, or sensitive personal category data as part of this integration.

6. Personal Data & Privacy Controls

This integration transmits personal data (email addresses and behavioral engagement data) to a third-party CRM. The following controls apply:

  •   Data transmission occurs over TLS-encrypted channels.
  •   HubSpot is treated as a data processor. Customers must ensure their HubSpot Data Processing Agreement (DPA) covers this use case.
  •   Under Tiled's SOC 2 CC9.2 (Vendor & Third-Party Risk) controls, customers acting as data controllers are responsible for ensuring an adequate legal basis for transmitting recipient engagement data to HubSpot.
  •   Tiled retains session data per its standard data retention policy. Once dispatched, HubSpot's own data retention policies govern the CRM-side records.

7. Audit Evidence & Logging

  •   Each dispatch event is logged with a timestamp, target integration (HubSpot), and status (success/failure).
  •   Failed dispatch events surface in the integration health dashboard for administrator review.
  •   Dispatch configuration changes are logged to the Tiled audit trail, recording the administrator who made the change and the timestamp.

9. Change History

v1.0 — May 5, 2026

Initial article. Integration shipped in Tiled v60.0.0 (TD-6720, TD-6721, TD-6723, TD-6725).