You may notice that some customer phone numbers or other profile attributes are getting overwritten or cleared (“unset”) in Klaviyo. This may happen even though the original data appeared to exist previously. This article explains why this happens, what the profile-bulk-import-jobs API flow represents, and how to prevent it going forward.
What’s Happening
Some customers observed that:
- Profiles updated through Amperity caused Klaviyo to remove phone numbers or other fields
- Downstream logs referenced an API called profile-bulk-import-jobs
- It appeared as if Amperity explicitly told Klaviyo to “unset” values
What That API Is
The profile-bulk-import-jobs endpoint is an internal Amperity API used by certain destination connectors, including the Klaviyo destination plugin. It is expected that you will not find this API in public documentation, because it is not customer-facing. It is simply the mechanism used to deliver bulk profile updates to Klaviyo.
Why Fields Get Cleared
- The Klaviyo connector intentionally clears a field when a null value is sent
- This applies to any profile attribute, not only phone number
- This behavior aligns with Klaviyo’s documented API behavior:
- Sending a field with null clears it.
- Not including a field leaves the existing value unchanged.
Root Cause
This typically happens when:
- A record enters Amperity without a phone number (or other attribute)
- That same record is included in a campaign or activation job to Klaviyo
- Amperity sends the profile payload the missing phone field is sent as null
- Klaviyo interprets that null value as “clear this field”
- Result: An existing phone number or attribute stored in Klaviyo gets overwritten with blank/empty.
This is expected system behavior.
Important Note
This is not caused by Amperity deleting data and it is not a bug in the Klaviyo connector. It occurs because upstream data did not include that attribute, and Klaviyo correctly honored the null update.
How to Prevent This
To avoid unintentionally clearing fields in Klaviyo:
- Option 1 — Fix upstream ingestion: Ensure phone numbers (or other important attributes) are consistently included in data feeds entering Amperity.
- Option 2 — Avoid sending incomplete records: Before activation, ensure records without those attributes are: filtered out or enriched before they are sent to Klaviyo
Once upstream data consistency is restored, this behavior will stop.