Iterable trigger sync Insert/Update/Upsert modes
Iterable trigger syncs gain Update and Upsert modes across channels, letting data changes re-trigger a campaign, not just first appearance.
Entries on this page are generated by AI from vendor sources. How AI is used
Reverse ETL & data syncs
Syncing modeled warehouse data out to operational tools on a schedule or trigger.
| Month | Changes |
|---|---|
| 2026-06 | 2 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 1 |
Select a month to view the whole-record timeline. This clears timeline filters.
Platforms with recorded changes
Platforms with at least one feature state classified in this capability (primary or secondary, minor updates included), in the site's fixed order. Select one to filter the timeline. Counts are not shown side by side: they reflect how finely each vendor documents, not how much it offers.
Timeline
← Back to the Release MatrixTimeline filters
Filters apply to the timeline. The chart and platform totals describe the whole record. Selecting a chart month clears timeline filters to show that same whole-record scope.
Matches the Release Matrix evidence: latest state reached in the selected period, entries under review excluded, primary and secondary capabilities included.
No recorded changes match these filters.
Within each period: major updates as cards, then notable ones as rows; newest first in each group. Minor updates below.
September 20261 change
June 20262 changes
Hightouch 2 minor updates Reverse ETL & data syncs
- GA AI Decisioning sync payload column selection source AI Decisioning lets you choose which user columns are included in destination sync payloads instead of sending the whole model.