Update Timeline events without overwriting what's already there
Imports can now update only the fields you map on existing Timeline events.
Until now, importing a Timeline event that already existed replaced the whole event. Any property missing from the file or payload was cleared. A new option on the Timeline import step, "Update existing Timeline events with mapped fields only," changes that. Turn it on, and BlueConic writes your mapped fields onto matching events and leaves everything else alone.
That means you can refresh an order status or a campaign field without resending every property. The option works in the S3, SFTP, Google Cloud Storage, Azure Blob Storage, Azure Data Lake, Google Drive, and HubSpot connections.
Benefits:
- Updates individual Timeline properties without losing stored values
- Removes the need to resend every property on every import
- Works across six file-based connections and HubSpot
To learn more, read our documentation.