Data Ingestion Studio changelog

New capabilities, practical improvements and everyday fixes. Current documented version: 1.2.0. Find your running version in the Studio footer.

See the latest changesExplore the Studio

Release history

The changelog starts with version 1.1.0, which brought delta imports and contact custom events together.

v1.2.0 · Latest

Reusable templates and governed automation

  • Save a completed import as a portal template and repeat its preparation, mappings, details and saved HubSpot options on a new file.
  • Matching automated runs go straight to a change summary. HubSpot writes still require your explicit confirmation, with an editable name for new marketing events.
  • Different files, changed defaults and processing errors reopen the usual import screens. Restricted users can request help or approval to save and update templates.
  • Delta templates can match chosen keys and use the latest successful automated run as their next baseline.
  • The admin API reference now groups endpoints by workflow and shares the Studio's colours, navigation and release version.
Read the guide for v1.2.0

v1.1.4

Skipped rows and header selection

  • Choosing the header row preserves rows already skipped below it, using either the grid or the Header row field.
  • Skipping blank separators no longer blocks preparation. The Studio still flags row selections that do not belong to the chosen data.
  • Validation errors show readable messages instead of raw technical details.
Read the guide for v1.1.4

v1.1.3

Existing contact custom events

  • Existing eligible contact custom events appear correctly in Map, while automatic definitions and events for other objects remain excluded.
  • An empty list says No contact custom events found. HubSpot subscription and permission requirements still apply.
Read the guide for v1.1.3

v1.1.2

Contacts and event participation in one file

  • New Contacts only runs import contact properties and marketing-event registration, attendance and departure timestamps together.
  • Email identifies contacts without a known record ID; known IDs keep priority.
  • Previously confirmed runs retain their saved steps. Event creation, custom event occurrences and segments remain separate actions.
Read the guide for v1.1.2

v1.1.0

Delta imports and contact custom events

  • Start Import delta from a completed import, upload the updated file and compare all shared columns or choose keys such as Email or an occurrence ID.
  • Review which rows are new and which are skipped before preparing the delta.
  • Choose or create contact custom events in Map, with suggested Yes/No, Number, Date and time, Dropdown and Text properties.
  • Keep repeated emails as separate event occurrences and send them after importing contacts, or prepare a manual import file.
Read the guide for v1.1.0

Release notes describe available product changes, not future commitments. HubSpot subscription, portal permissions and confirmation safeguards still apply.

Changelog in the documentationSee what is planned