Skip to content
  • There are no suggestions because the search field is empty.

HubSpot Uninstall Tracking

Review HubSpot Uninstall Tracking

Summary

  • Uninstall tracking is fully accurate from 5 January 2026 onward.

  • Historical uninstall data is partially available and was baseline-aligned at go‑live.

  • Live workflows now maintain uninstall state, dates, and counts going forward.

  • Historical gaps are intentional and documented.

Deal Properties Used

1. Currently Uninstalled (Yes / No)

Purpose: Indicates whether the retailer is currently in an uninstalled state.

Behaviour:

  • Set to Yes when a deal enters Uninstalled App

  • Set to No when a deal leaves Uninstalled App

Notes:

  • Mirrors the deal stage

  • Used for quick filtering and visibility

2. First App Uninstalled Date

Purpose: Captures the first known uninstall date for a retailer.

Behaviour:

  • Set once only

  • Never overwritten

Historical behaviour:

  • For deals already uninstalled at go‑live, this reflects the earliest uninstall HubSpot still exposes

  • It does not guarantee the retailer’s first‑ever uninstall

3. Last App Uninstalled Date

Purpose: Stores the most recent uninstall event.

Behaviour:

  • Updated each time a deal enters Uninstalled App

Historical behaviour:

  • Backfilled at go‑live using Date entered Uninstalled App where available

4. Uninstall Count (Number)

Purpose: Tracks how many uninstall events have occurred.

Behaviour:

  • Incremented on each uninstall event after go‑live

Historical behaviour:

  • Deals already uninstalled at go‑live were initialised to 1

  • This represents a minimum truthful baseline (“at least one uninstall”)

Workflows

A. Deal – App Uninstalled → Update uninstall tracking

Status: ON (live)

Purpose: Core live uninstall tracking.

Trigger:

  • Deal enters Uninstalled App stage

Actions:

  • Set Currently Uninstalled = Yes

  • Set Last App Uninstalled Date = Date entered Uninstalled App

  • Increment Uninstall Count by 1

Notes:

  • Forward‑only

  • Should never be manually run

B. Deal – Capture FIRST uninstall date

Status: OFF (completed)

Purpose: One‑time baseline capture for first uninstall date.

Behaviour:

  • Sets First App Uninstalled Date only when blank

  • Never overwrites existing values

Notes:

  • Used only at go‑live

  • Disabled after completion

C. Deal – App Reinstalled → Clear uninstall status

Status: ON (live)

Purpose: Keeps uninstall flag in sync when a retailer reinstalls.

Trigger:

  • Deal leaves Uninstalled App stage

Actions:

  • Set Currently Uninstalled = No

D. Backfill Workflows (Historical – Completed)

These workflows were used once at go‑live and are now deleted or disabled:

  • Set Currently Uninstalled = Yes for deals already uninstalled

  • Backfill Last App Uninstalled Date

  • Initialise Uninstall Count = 1

These workflows must not be recreated or re‑run.

Data Accuracy & Limitations

Accuracy Boundary

Uninstall tracking is fully accurate from 5 January 2026 onward.

Before this date:

  • First uninstall date reflects the earliest uninstall HubSpot still exposes

  • Uninstall count represents a minimum baseline

  • Some historical uninstall timelines may be incomplete

Why historical gaps exist

HubSpot does not reliably allow historical stage‑entry timestamps to be written into custom properties via workflows once the original event has passed.

If required, full historical uninstall timelines could be reconstructed via API analysis.

What This System Is (and Is Not)

This system is:

  • Accurate going forward from January 5 2026

  • Has historical limits

This system is not:

  • A perfect reconstruction of pre‑2026 uninstall behaviour

  • A replacement for API‑level history analysis

Maintenance Notes

  • Do not manually run live workflows

  • Do not re‑enable backfill workflows

  • Any future changes should update this document