Summary
The address held on a Klaviyo Profile can be transferred into iPaaS.com as a Customer Address record. The address is dispatched as a child of the parent Klaviyo Profile transfer: when a profile is brought into iPaaS.com, its location details, along with the profile's name, organization, and phone number, are written to a Customer Address attached to the matching iPaaS.com Customer. Two mapping collections cover this flow, one that creates the address the first time it transfers and one that maintains it on later transfers.
Parent Collection
This document covers the address child collections, which never transfer on their own. They are dispatched as part of the parent Klaviyo Profile transfer. For the parent profile flow, including how a Klaviyo profile is matched to an iPaaS.com Customer and how the profile fields are mapped, see Klaviyo to iPaaS.com Profile Mapping Documentation.
ID Format
The address child collections do not accept an identifier on the iPaaS.com Manual Sync page. They are never synced on their own. To transfer an address on demand, sync its parent profile from the iPaaS.com Manual Sync page using the parent profile's identifier.
The parent Klaviyo Profile is identified by its Klaviyo Profile ID. An example value is 44552.
External ID Format
After a parent profile transfers, the Klaviyo Profile ID is saved as the external ID on the resulting iPaaS.com Customer. The address record itself is attached to that Customer and is not tracked by its own Klaviyo external ID, because Klaviyo stores the address inside the profile rather than as a separate record.
Deleted Record Support
Outbound delete is not supported for the Customer Address entity in this integration. Removing the address from a Klaviyo profile does not delete the corresponding Customer Address in iPaaS.com, and delete mappings are not included in the default templates. Deletions do not propagate to iPaaS.com.
Custom Field Support
These collections do not map any Klaviyo values into iPaaS.com custom fields. Subscribers can add custom-field mappings if additional Klaviyo profile values need to travel with the address.
Mapping Collection Status
Both address collections ship Enabled.
Add Klaviyo Profile Address TO iPaaS.com: Trigger event Add. Runs when the parent profile is transferred and the address does not yet exist in iPaaS.com.
Update Klaviyo Profile Address TO iPaaS.com: Trigger event Update. Runs when the parent profile is transferred and the address already exists in iPaaS.com.
Both are dispatched only as children of their respective parent profile transfer, whether that transfer runs on the polling schedule or via Manual Sync of the parent profile. Klaviyo does not send change webhooks to the integration, so the polling schedule is the automatic path for keeping iPaaS.com current.
Duplicate or Conflicting Mappings
The inbound address flow is intentionally split into two collections so that the Add path creates the Customer Address and the Update path maintains it:
Add Klaviyo Profile Address TO iPaaS.com creates the address the first time it transfers.
Update Klaviyo Profile Address TO iPaaS.com writes changes to an address that already exists in iPaaS.com.
Both collections set the PreventDuplicate control field to "true" (see the Mappings section). This triggers an exact-address-match check during the transfer: the integration compares the incoming address against the Customer's existing address and, when an exact match is found, does not add a duplicate. This keeps a single Customer Address per profile across repeated transfers.
There is no configurable collision-handling method on these collections. The address entity does not implement selectable collision resolution; the only duplicate-prevention mechanism is the PreventDuplicate exact-match check described above.
System Caveats
Klaviyo Caveats
Single address per profile: Klaviyo holds at most one address per profile inside the profile's location details, so each collection transfers one Customer Address per profile.
Address sourced from the parent profile: Every value in these collections is read from the parent profile rather than from a separate address object, because Klaviyo stores the address as part of the profile.
Partial addresses are skipped: An address transfers only when the profile's street address, city, and country are all present (see the Mapping Filter in the Mappings section). A profile missing any of those three values transfers its profile but not its address.
iPaaS.com Caveats
No entity-required field: The iPaaS.com Customer Address record does not mark any of the transferred fields as entity-required. The street address, city, and country are made effectively required by the collection filter rather than by the Customer Address record itself.
Address attaches to the matching Customer: The Customer Address is linked to the iPaaS.com Customer created or matched by the parent Profile collection. If the parent profile does not resolve to a Customer, the address has nothing to attach to.
Integration-Specific Caveats
Child dispatched with the parent transfer: These collections run only as children of the parent Klaviyo Profile transfer. They do not poll, do not support independent transfer, and are not available for stand-alone Manual Sync. The address moves whenever its parent profile moves.
Integration Flow
The integration retrieves a Klaviyo profile, either on the polling schedule (checking for recently updated profiles) or via Manual Sync of the parent profile.
The parent Profile collection creates or matches an iPaaS.com Customer for the profile. An inbound profile whose email matches an existing iPaaS.com Customer links to that Customer; otherwise a new Customer is added.
The address child collection runs. Its filter checks that the profile's street address, city, and country are all present. If any of the three is missing, the address child is skipped and no Customer Address is written; the parent profile still transfers.
When the filter passes, the integration maps the profile's name, organization, location details, and phone number to a Customer Address. The PreventDuplicate control field is set so the integration checks for an exact address match on the Customer before adding the address.
The Add child runs when no matching address exists yet and creates the Customer Address. The Update child runs when an address already exists and writes the current values back to it in place.
Mappings
Both collections carry the same filter and the same field mappings. The only difference is the trigger: the Add collection creates the address and the Update collection maintains an address that already exists.
Add Klaviyo Profile Address TO iPaaS.com
Mapping Filter
Parent.CustomerAttributes.Location.Address1 != null && Parent.CustomerAttributes.Location.City != null && Parent.CustomerAttributes.Location.Country != null
Filter Description. This filter requires that the parent profile's street address, city, and country are all present before the address transfers. A profile that supplies all three values passes the filter, and its Customer Address is created in iPaaS.com. A profile missing any one of the three is skipped by this child collection: no Customer Address is written for it, and the parent profile still transfers on its own. This is why the street address, city, and country are effectively required even though the Customer Address record does not mark them as entity-required.
Description. Creates a Customer Address attached to the matching iPaaS.com Customer from the parent profile's location details, name, organization, and phone number.
Mapping Type | Source Field (Klaviyo) | Destination Field (iPaaS.com) | Description |
Static |
| PreventDuplicate | Control mapping. Triggers an exact-address-match check so the integration does not add a duplicate address when one already exists on the Customer, keeping a single Customer Address per profile. |
Dynamic Formula |
| Address1 | Effectively required (enforced by the collection filter). Street address from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| Address2 | Recommended. Secondary address line from the profile's location details, when present. |
Dynamic Formula |
| City | Effectively required (enforced by the collection filter). City from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| Region | Recommended. Region or state from the profile's location details. |
Dynamic Formula |
| PostalCode | Recommended. Postal or ZIP code from the profile's location details. |
Dynamic Formula |
| Country | Effectively required (enforced by the collection filter). Country from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| FirstName | Recommended. First name from the parent profile, so the address record carries the contact name. |
Dynamic Formula |
| LastName | Recommended. Last name from the parent profile. |
Dynamic Formula |
| Company | Recommended. Organization name from the parent profile. |
Dynamic Formula |
| PhoneNumber | Recommended. Phone number from the parent profile. |
Update Klaviyo Profile Address TO iPaaS.com
Mapping Filter
Parent.CustomerAttributes.Location.Address1 != null && Parent.CustomerAttributes.Location.City != null && Parent.CustomerAttributes.Location.Country != null
Filter Description. This filter requires that the parent profile's street address, city, and country are all present before the address update transfers. A profile that supplies all three values passes the filter, and its existing Customer Address is updated in iPaaS.com. A profile missing any one of the three is skipped by this child collection: no Customer Address update is written for it, and the parent profile still transfers on its own.
Description. Updates the Customer Address attached to the matching iPaaS.com Customer with the parent profile's current location details, name, organization, and phone number.
Mapping Type | Source Field (Klaviyo) | Destination Field (iPaaS.com) | Description |
Static |
| PreventDuplicate | Control mapping. Triggers an exact-address-match check so the integration matches the incoming address against the Customer's existing address and updates it in place rather than creating a duplicate, keeping a single Customer Address per profile. |
Dynamic Formula |
| Address1 | Effectively required (enforced by the collection filter). Street address from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| Address2 | Recommended. Secondary address line from the profile's location details, when present. |
Dynamic Formula |
| City | Effectively required (enforced by the collection filter). City from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| Region | Recommended. Region or state from the profile's location details. |
Dynamic Formula |
| PostalCode | Recommended. Postal or ZIP code from the profile's location details. |
Dynamic Formula |
| Country | Effectively required (enforced by the collection filter). Country from the profile's location details. The address does not transfer when this value is empty. |
Dynamic Formula |
| FirstName | Recommended. First name from the parent profile, so the address record carries the contact name. |
Dynamic Formula |
| LastName | Recommended. Last name from the parent profile. |
Dynamic Formula |
| Company | Recommended. Organization name from the parent profile. |
Dynamic Formula |
| PhoneNumber | Recommended. Phone number from the parent profile. |
Error Handling
Address does not appear in iPaaS.com after a profile transfer — Most often the profile is missing one or more of the three filter values: street address, city, or country. When any of the three is absent, the address child is skipped by design and the parent profile transfers without it. Resolution: confirm the Klaviyo profile has a street address, city, and country, then re-sync the parent profile.
Profile transfer fails when Klaviyo is temporarily unavailable — If the Klaviyo API is unreachable while a profile transfer runs, the transfer fails and the address child does not run. The error appears in iPaaS.com Dashboard / Integration Monitoring / Error Logs. Resolution: retry via Manual Sync of the parent profile once Klaviyo is reachable.
Address has nothing to attach to — If the parent profile does not resolve to an iPaaS.com Customer, the address child has no Customer to attach to. Resolution: confirm the parent profile transferred successfully and resolved to a Customer; the address attaches to that Customer.
Testing & Validation
Test Scenarios
Create a new profile with a complete address. In Klaviyo, create a profile with a street address, city, and country. Transfer the parent profile and verify a Customer Address is created on the matching iPaaS.com Customer with the expected location details, name, organization, and phone number.
Update an address field. Change the city or postal code on an existing Klaviyo profile, re-sync the parent profile, and verify the change propagates to the existing Customer Address without creating a duplicate.
Verify the filter on a partial address. Transfer a profile that is missing the country (or city, or street address) and confirm the parent profile transfers while no Customer Address is written for it.
Verify duplicate prevention. Transfer the same complete profile twice and confirm only one Customer Address exists on the Customer after both transfers.
Verify the ID format. From the iPaaS.com Manual Sync page, sync the parent profile using its Klaviyo Profile ID and confirm the address transfers with it.
Verify parent-child sync. Create a parent profile with a complete address, transfer the parent, and confirm both the Customer and its Customer Address sync together as part of one transfer.
Validation Checklist
The Customer Address is attached to the iPaaS.com Customer created or matched by the parent profile.
The street address, city, and country are populated; the address was not written for any profile missing one of the three.
Only one Customer Address exists per profile after repeated transfers.
Address field changes in Klaviyo propagate to the existing Customer Address on the next transfer of the parent profile.
Transfer errors, when they occur, appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs and can be retried via Manual Sync of the parent profile.
Additional Notes
Klaviyo does not send change webhooks to the integration, so address changes reach iPaaS.com on the polling schedule or via Manual Sync of the parent profile rather than instantly. This reflects the Klaviyo platform's design at the time this documentation was written.
An address is transferred only when the profile's street address, city, and country are all present, so partially completed addresses in Klaviyo do not reach iPaaS.com. This reflects the collection filter in place at the time this documentation was written.