Skip to content
Go to www.furball.tech
  • There are no suggestions because the search field is empty.

Data Ingestion Studio Changelog

New features, improvements and fixes since version 1.1

Overview

Follow the changes that affect your team's imports, from new workflows to everyday fixes. The current documented Studio version is 1.1.4. You can find your running version in the Studio footer.

The changelog starts with version 1.1.0. Product Updates tracks new and refreshed help articles; the roadmap covers work that is not yet available.

1.1.4 - Skipped rows and header selection

  • Choosing a header row now preserves rows already skipped below that header, whether you use the grid's Header action 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 display readable messages instead of raw technical details.

You can keep title rows, blank separators and disclaimers in an Excel export, choose the correct header and skip unwanted rows without copying the data into a new workbook. See Upload a File and Choose the Data to Process.

1.1.3 - Existing contact custom events

  • Existing eligible contact custom events now appear correctly in the Map dropdown.
  • Automatic activity definitions and events linked to other object types remain excluded.
  • An empty list now says No contact custom events found.

Custom-event permissions and your HubSpot subscription still apply. See Prepare and Send Contact Custom Events.

1.1.2 - Contacts and marketing-event participation together

  • New Contacts only automated runs send contact properties and marketing-event registration, attendance and departure timestamps together in one file.
  • Email can identify a contact when no record ID is known. Known record IDs keep priority.
  • Previously confirmed runs retain their saved steps, so completed work is not replayed.

Event creation, custom event occurrences and optional segments remain separate actions. See Import Marketing Event Registration and Attendance.

1.1.0 - Delta imports and contact custom events

  • Start Import delta from a completed import and upload an updated file.
  • Compare all shared columns, or choose one or more matching columns such as Email or an occurrence ID.
  • Review which rows are new and which are skipped before preparing the delta.
  • Choose an existing contact custom event in Map, or create one from selected columns with suggested Yes/No, Number, Date and time, Dropdown and Text properties.
  • Keep repeated email addresses as separate event occurrences, then send them after the contacts are imported or prepare a file for manual import.

Delta matching by Email skips an email already in the baseline even when other values changed. For repeat activities, choose an occurrence-level key instead. Read Import Only New Rows with Delta Imports and Prepare and Send Contact Custom Events.

What to do next

  • Check your running version before reporting a problem and include it when contacting support.
  • Review new feature settings before changing a recurring import process.
  • Use the linked guides for operational steps. A release entry does not remove HubSpot plan requirements, portal permissions or confirmation safeguards.