SubscribeProfile: A custom field named SubscribeProfile mapped to a true or false value controls the profile's subscription state. A value of true makes the profile eligible to receive subscription consent notifications and to be added to lists. No mapping, or a value of false, fully unsubscribes the profile, so this field should be mapped deliberately to honor opt-out status from other sources.

LIST_{list name}: A custom field named with the LIST_ prefix followed by a Klaviyo list name, mapped to true or false, adds the profile to (or removes it from) a list that uses double opt-in. When the list is configured for double opt-in, Klaviyo sends a consent email to the profile's email address, and the subscription completes only after the recipient responds.

UCLIST_{list name}: A custom field named with the UCLIST_ prefix followed by a Klaviyo list name, mapped to true or false, adds the profile to (or removes it from) a list that auto-subscribes without consent. When the list is configured for single opt-in, no consent email is sent and the profile is subscribed automatically.

Status: Enabled

Trigger Events: iPaaS.com Customer outbound triggers (Create, Update). The subscriber enables these triggers under Outbound Data Flows. Klaviyo does not send change webhooks to the integration, so the enabled outbound triggers — together with Manual Sync — are what drive these collections.

Identifier required for matching: Although Klaviyo marks every profile attribute as optional, a profile cannot be created or matched without at least one identifier. Either Email or PhoneNumber must resolve to a value.

Phone number format: Klaviyo requires phone numbers in an E.164-style format. The integration normalizes the iPaaS.com Customer number before sending; a number that cannot be normalized is omitted rather than sent. Klaviyo performs its own additional validation, so a number that Klaviyo rejects will cause the transfer to error.

Single address per profile: A Klaviyo profile supports a single address through the API. The address values are set in the parent mapping from the iPaaS.com Customer.

Partial update preserves unmapped fields: Updates are sent as a partial patch, so profile fields the Update collection does not map are left untouched. The overwrite risk to existing Klaviyo data is low.

Address sourced from primary billing address: The address fields (Address1, Address2, City, Region, Zip, Country) are read from the iPaaS.com Customer's primary billing address. A Customer without a primary billing address sends no address values. On an update, a partial patch leaves the profile's existing address untouched.

Identifier present: A Customer without an email address or a normalizable phone number cannot be transferred, because Klaviyo has no identifier to create or match the profile.

iPaaS.com as source of truth: The default templates both add and update a profile from iPaaS.com, which assumes iPaaS.com is the source of truth for all profile data. Splitting the templates into separate Add-only and Update-only collections preserves any values that Klaviyo controls going forward.

Subscription state is deliberate: Because an absent or false SubscribeProfile value fully unsubscribes the profile, the subscription custom field should be mapped intentionally rather than left unset.

Identify the Klaviyo lists that profiles should join, and confirm each list's opt-in configuration (single versus double opt-in), which determines whether a consent email is sent.

Enable the relevant iPaaS.com Customer outbound triggers under Outbound Data Flows so that profile creates and updates are sent automatically. Until these triggers are enabled, transfers occur only through Manual Sync.

Create the subscription custom fields the integration relies on — SubscribeProfile, any LIST_{list name} and UCLIST_{list name} fields, and any additional custom-property fields — and map values to them.

Refer to the Klaviyo installation and connection articles for the full authentication and connection walkthrough.

No valid identifier present — A Customer reaches the integration with no email address and no normalizable phone number, so Klaviyo has no identifier to create or match the profile and the transfer fails. Resolution: ensure the source Customer has a valid email address or a phone number that normalizes to E.164 format before sending.

Phone number rejected by Klaviyo — A phone number passes integration normalization but fails Klaviyo's own validation. Resolution: correct the source Customer number so it normalizes to a phone number Klaviyo accepts as valid.

Klaviyo API temporarily unavailable — A profile create or update runs while the Klaviyo API is unreachable, and the transfer fails. The error appears in iPaaS.com Dashboard / Integration Monitoring / Error Logs. Resolution: retry the transfer via Manual Sync once the API is reachable.

Create a new profile: Send an iPaaS.com Customer that is not yet linked to a Klaviyo profile and confirm a new profile is created in Klaviyo with the mapped name, email, phone, organization, and primary billing address, and that the iPaaS.com external id is stored on the profile.

Update an existing profile: Change a field on a Customer that is already linked to a Klaviyo profile, send it outbound, and confirm the same profile is patched and that unmapped Klaviyo fields are preserved.

Match by email: Send a Customer whose email matches an existing Klaviyo profile and confirm the existing profile is linked rather than duplicated.

Match by phone fallback: Send a Customer with no email but a valid phone number and confirm the profile is matched by phone number.

Missing identifier: Send a Customer with neither a valid email nor a normalizable phone number and confirm the transfer errors and is logged.

Phone normalization: Send a Customer number that includes non-digit characters and confirm it is normalized to E.164 format, and that a number Klaviyo rejects produces a logged error.

Subscription state: Map SubscribeProfile to false (or leave it unmapped) and confirm the profile is unsubscribed; map it to true with a list and confirm the profile is eligible for list membership.

Double vs single opt-in: Map a LIST_{list name} value against a double opt-in list and confirm a consent email is sent; map a UCLIST_{list name} value against a single opt-in list and confirm the profile is subscribed automatically without a consent email.

Manual Sync ID format: Manually sync a Customer by entering its iPaaS.com Customer ID and confirm the profile is created or updated.

The source Customer has an email address, or a phone number that normalizes to E.164 format.

The Id mapping resolves the Klaviyo profile link correctly so the Customer is routed to Add (unlinked) or Update (linked).

The ExternalId mapping stores the iPaaS.com Customer identifier on the created profile.

SubscribeProfile is mapped intentionally to honor the desired subscription state.

Any LIST_{list name} and UCLIST_{list name} values match real Klaviyo list names and the lists' opt-in configuration.

A primary billing address is present on the Customer when address values should appear on the profile.

Add-only and Update-only collections are kept separate when Klaviyo is the system of record for any profile field.

iPaaS.com is treated as the source of truth for profile data in the default templates. Splitting the templates into separate Add-only and Update-only collections is strongly recommended so that values controlled directly in Klaviyo — such as an in-Klaviyo unsubscribe — are not overwritten by a later outbound update.

A profile cannot be transferred when no valid email or phone number is available.

Klaviyo does not send change webhooks to the integration, so these collections run only when an enabled iPaaS.com outbound trigger fires or a Manual Sync is requested.

Klaviyo Installation Instructions

Klaviyo Connections and Settings

Klaviyo API Endpoints

Klaviyo Integration Known Limitations

Klaviyo Error Messages

Klaviyo to iPaaS.com Profile Mapping Documentation

Klaviyo to iPaaS.com Profile Address Mapping Documentation

Klaviyo Placed Order Event From iPaaS.com Mapping Documentation

Klaviyo Ordered Product Event From iPaaS.com Mapping Documentation