Klaviyo



Klaviyo



Klaviyo

Klaviyo

Beta version

The configuration and connection might need a bit of fine-tuning to get things running smoothly. Let us know if you hit any snags at team@tably.com.

Once created, a connection can be reused or copy-pasted in all other pages within same workspace without additional setup. The setup can be complex and, if in doubt, ask your developer for help. They will have all needed details and will be able to assist with possible errors.

Klaviyo API Key. See our docs if you need help finding this key.
Certain streams like the profiles stream can retrieve predictive analytics data from Klaviyo's API. However, at high volume, this can lead to service availability issues on the API which can be improved by not fetching this field. WARNING: Enabling this setting will stop the "predictive_analytics" column from being populated in your downstream destination.
The number of worker threads to use for the sync. The performance upper boundary is based on the limit of your Klaviyo plan. More info about the rate limit plan tiers can be found on Klaviyo's API docs.
The number of days to look back when syncing data in incremental mode. This helps capture any late-arriving data. Only applies to the events_detailed stream. For the flow_series_reports stream, use Reporting Lookback Window instead.
Re-syncs the last N days of the flow_series_reports stream on every incremental run. Klaviyo keeps updating conversion attribution after a send - by default for up to 5 days, and up to 90 days if you raise the attribution window in your account settings - so the numbers first reported for a day keep changing for a while. Set this to at least your attribution window to pick those revisions up. Because flow_series_reports rows are keyed by the calendar day they report on, a destination that deduplicates on the primary key replaces the row previously written for a re-synced day, while in append mode each re-synced day adds an extra row per sync. This does not apply to campaign_values_reports: that endpoint returns a single aggregate for the whole requested period instead of a per-day breakdown, so a re-read cannot replace anything and would only add double-counted rows. Defaults to 0 (no re-sync).
OPTIONAL: Comma-separated list of specific metric IDs to use for flow_series_reports and campaign_values_reports streams. If left empty, the connector will automatically fetch reports for ALL available metrics in your account. Due to Klaviyo's strict API rate limits - see Klaviyo's API docs, syncing all metrics can be extremely slow and may take hours to complete. RECOMMENDED: Specify only the conversion metrics you need (e.g., "RESQ6t" for Placed Order) to avoid slow syncs. Find metric IDs in your Klaviyo account under Analytics > Metrics, or use the metrics stream to list all available metrics and their IDs.
OPTIONAL: Comma-separated list of Klaviyo metric IDs to filter the events and events_detailed streams. If left empty, events for ALL metrics will be synced. Specify only the metrics you need to significantly reduce sync volume and duration. Note: Klaviyo does not support filtering by custom metrics - only built-in metrics can be filtered. Find metric IDs in your Klaviyo account under Analytics > Metrics, or use the metrics stream to list all available metrics and their IDs.
Loadingโ€ฆ