Advanced Analytica Advanced Analytica: IBOM
← All connectors
Klaviyo logo

Source connector

Klaviyo

Set up Klaviyo as a source and move its data into your chosen destination.

Version 4.0.5 certified generally available

Klaviyo

Use this page to set up the Klaviyo source connector and find reference information.

Prerequisites

Setup guide

Step 1: Set up Klaviyo

  1. Create a Klaviyo account.
  2. Create a Private API key. Grant read access for every stream you want to replicate, as listed in Required API key scopes. If the key lacks a scope, Klaviyo rejects that stream’s requests with a 403 error. The sync then fails.

Required API key scopes

Klaviyo private API keys carry per-object scopes. Each stream needs read access to the objects behind its endpoints:

StreamRequired scopes
Campaigns, Campaigns Detailedcampaigns:read
Campaign Values Reportscampaigns:read, metrics:read
Email Templatestemplates:read
Events, Events Detailedevents:read
Flowsflows:read
Flow Series Reportsflows:read, metrics:read
GlobalExclusions, Profilesprofiles:read
Lists, Lists Detailedlists:read
Metricsmetrics:read
Segmentssegments:read

The two report streams also need metrics:read. The connector lists your account’s metrics to decide which conversion metrics to request reports for. Klaviyo publishes each endpoint’s required scopes in its API reference and OpenAPI specification.

Step 2: Set up the Klaviyo connector in Airbyte

Airbyte Cloud

  1. Log into your Airbyte Cloud account.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Klaviyo from the Source type dropdown.
  4. Enter a name for the Klaviyo connector.
  5. For Api Key, enter the Klaviyo Private API key.
  6. For Start Date, enter a UTC date and time in YYYY-MM-DDTHH:MM:SSZ format, for example, 2017-01-25T00:00:00Z. Airbyte replicates data added on or after this date. This field is optional. If you leave it blank, Airbyte replicates the previous year’s data. The metrics and global_exclusions streams ignore this date. Their first sync reads all metric definitions and the full suppression list. Later incremental syncs continue from the stored cursor. See Metrics stream and GlobalExclusions stream.
  7. (Optional) Select Disable Fetching Predictive Analytics to stop the connector requesting predictive analytics data. See Performance considerations.
  8. For Number of concurrent threads, enter the number of worker threads used by the sync. The default is 10, and the maximum is 50. Lower this value if syncs reach Klaviyo rate limits. Raise it only if your Klaviyo plan’s rate limit tier allows greater throughput.
  9. For Lookback Window (Days), enter the lookback period in days for incremental syncs. This period helps capture late-arriving data. The default is 0 days if you don’t provide a value. This setting only applies to the events_detailed stream. For Flow Series Reports, use Reporting Lookback Window (Days) instead.
  10. (Optional) For Reporting Lookback Window (Days), enter how many days of Flow Series Reports data each incremental run should re-sync. Klaviyo revises conversion attribution after a send. Set this value to at least your attribution window to capture those revisions. Re-synced days replace the rows already written for those days. The default is 0. See Analytics streams for details.
  11. (Optional) For Report Stream Conversion Metric IDs, enter a comma-separated list of Klaviyo metric IDs. This limits the Campaign Values Reports and Flow Series Reports streams to specific conversion metrics. Without this list, the connector fetches reports for all metrics. Rate limits can make this process slow. See Analytics streams for details.
  12. (Optional) For Event Stream Metric IDs, enter a comma-separated list of Klaviyo metric IDs. This filters the Events and Events Detailed streams to specific metrics. Without this list, all events are synced. See Event stream filtering below.
  13. Click Set up source.

Airbyte Open Source

  1. Go to the Airbyte Open Source dashboard.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Klaviyo from the Source type dropdown.
  4. Enter a name for the Klaviyo connector.
  5. For Api Key, enter the Klaviyo Private API key.
  6. For Start Date, enter a UTC date and time in YYYY-MM-DDTHH:MM:SSZ format, for example, 2017-01-25T00:00:00Z. Airbyte replicates data added on or after this date. This field is optional. If you leave it blank, Airbyte replicates the previous year’s data. The metrics and global_exclusions streams ignore this date. Their first sync reads all metric definitions and the full suppression list. Later incremental syncs continue from the stored cursor. See Metrics stream and GlobalExclusions stream.
  7. (Optional) Select Disable Fetching Predictive Analytics to stop the connector requesting predictive analytics data. See Performance considerations.
  8. For Number of concurrent threads, enter the number of worker threads used by the sync. The default is 10, and the maximum is 50. Lower this value if syncs reach Klaviyo rate limits. Raise it only if your Klaviyo plan’s rate limit tier allows greater throughput.
  9. For Lookback Window (Days), enter the lookback period in days for incremental syncs. This period helps capture late-arriving data. The default is 0 days if you don’t provide a value. This setting only applies to the events_detailed stream. For Flow Series Reports, use Reporting Lookback Window (Days) instead.
  10. (Optional) For Reporting Lookback Window (Days), enter how many days of Flow Series Reports data each incremental run should re-sync. Klaviyo revises conversion attribution after a send. Set this value to at least your attribution window to capture those revisions. Re-synced days replace the rows already written for those days. The default is 0. See Analytics streams for details.
  11. (Optional) For Report Stream Conversion Metric IDs, enter a comma-separated list of Klaviyo metric IDs. This limits the Campaign Values Reports and Flow Series Reports streams to specific conversion metrics. Without this list, the connector fetches reports for all metrics. Rate limits can make this process slow. See Analytics streams for details.
  12. (Optional) For Event Stream Metric IDs, enter a comma-separated list of Klaviyo metric IDs. This filters the Events and Events Detailed streams to specific metrics. Without this list, all events are synced. See Event stream filtering below.
  13. Click Set up source.

Supported sync modes

The Klaviyo source connector supports these sync modes:

Supported streams

Metrics stream

The Metrics stream always syncs every metric definition, regardless of the configured Start Date. You need metric definitions as reference data to interpret other streams. For example, you can join relationships.data.metric.id in events to a metric name. The Klaviyo API doesn’t support filtering metrics by date. Later incremental syncs emit only new and updated metric definitions. After upgrading from an earlier connector version, older metric definitions might be missing. Clear or reset the metrics stream to backfill them.

GlobalExclusions stream

The GlobalExclusions stream reads the same Klaviyo /profiles endpoint as Profiles. It keeps only profiles with a suppressed email marketing subscription. Suppressions include unsubscribes, hard bounces and manual suppressions. Each record stores the suppression details under attributes.subscriptions.email.marketing.suppressions.

This stream ignores Start Date. A first sync, or a sync after you clear the stream, returns your account’s complete suppression list. Later incremental syncs request only profiles whose updated timestamp changed since the previous sync. These requests use a fixed one-hour lookback. Klaviyo doesn’t always advance a profile’s updated timestamp when recording a suppression. Bounce-driven and API-driven suppressions can arrive shortly afterwards. Each incremental sync therefore emits any suppressed profile again when its updated timestamp falls within the previous hour. Destinations that deduplicate on the id primary key replace those rows in place. Append-only destinations keep them as duplicate rows.

The lookback doesn’t cover every case. Klaviyo might record a suppression more than an hour after the profile’s updated timestamp. If Klaviyo never updates that profile again, incremental syncs won’t capture the suppression. Clear the stream to reload the full suppression list and recover these rows.

Connector versions 2.10.14 through 3.0.2 paged through every profile during each sync, then filtered the results. Upgrading therefore makes this stream’s incremental syncs considerably shorter.

Streams that filter after fetching

The Metrics, Lists, Lists Detailed and Segments streams request every Klaviyo record during each sync. They then discard records older than the cursor position. Start Date and incremental sync reduce the records these streams emit, but not their API requests. Sync duration scales with your account’s total lists, segments and metrics, rather than its new data volume.

Analytics streams

The Campaign Values Reports and Flow Series Reports streams provide performance analytics from Klaviyo’s Reporting API.

Flow Series Reports emits one record for each calendar day and flow message. Each statistics field contains that day’s value. Its date field identifies the day covered by the row. This field forms part of the primary key: date, flow_id, flow_message_id, send_channel, conversion_metric_id. Reading a day again returns it with its existing identity.

Campaign Values Reports doesn’t provide a daily breakdown. The endpoint returns one aggregate for the connector’s entire requested period. date is the midnight that closes that period. A row dated 2024-06-15T00:00:00+00:00 therefore covers everything through the end of 2024-06-14. Its primary key is date, campaign_id, campaign_message_id, send_channel and conversion_metric_id.

The connector requests both reports in windows of up to 30 days. During the first sync, each Campaign Values Reports row therefore aggregates up to 30 days of activity. Later incremental syncs request only days since the previous sync, so their rows cover shorter periods.

Report periods always cover whole calendar days in your Klaviyo account’s company timezone. Klaviyo ignores the timezone offset in a custom report timeframe. It interprets the timeframe using your account’s configured company timezone. However, returned timestamps use a +00:00 offset. If your start date includes a time, the first period extends back to the previous midnight. Every sync stops after the last complete day. The current day’s data therefore arrives with the next sync.

Klaviyo continues revising conversion attribution after a send. The default period is up to 5 days. It can reach 90 days if you’ve increased the attribution window in your account settings. Numbers first reported for a day can therefore keep changing. Use Reporting Lookback Window (Days) to re-sync recent Flow Series Reports days during every incremental run. Set it to at least your attribution window to capture those revisions. A destination that deduplicates on the primary key replaces the existing row for each re-synced day. In append mode, each re-synced day adds another row during every sync. This setting doesn’t apply to Campaign Values Reports. That endpoint reports one aggregate for each requested period, rather than daily values. Re-reading it could only add another row covering the same days.

Both streams partition data by conversion metric. By default, the connector fetches reports for every metric in your account. Use the optional Report Stream Conversion Metric IDs configuration field to limit reporting to specific conversion metrics. Enter a comma-separated list of metric IDs, for example, RESQ6t,ABC123.

:::warning These analytics endpoints have strict Klaviyo API rate limits (see documentation). They allow a burst of 1 request per second, a steady 2 requests per minute and 225 requests daily. The connector makes a separate API request for every metric and time window. Syncing all metrics can therefore take several hours and exhaust the daily quota. Exceeding the quota causes the sync to fail with a rate limit error. See Performance considerations. Use the Report Stream Conversion Metric IDs field to specify only the conversion metrics you need. :::

Not every Klaviyo metric supports conversion value queries. For example, you can’t query values data for metrics without a $value property. The connector automatically skips unsupported metrics and continues syncing the others. If you receive fewer results than expected, check whether your selected metrics support values data in Klaviyo.

To find your conversion metric IDs:

  1. Sign in to your Klaviyo account.
  2. Go to Analytics > Metrics.
  3. Select the metric you want to track conversions for, such as “Placed Order”.
  4. Copy the metric ID from the URL. Alternatively, use the Metrics stream to list every available metric and its ID.

Event stream filtering

The Events and Events Detailed streams support server-side filtering by metric ID through the Event Stream Metric IDs configuration field.

Klaviyo’s metric_id filter only supports the equals operator. The connector therefore sends a separate request set for each configured metric ID. Every additional metric ID multiplies the API requests made during each sync. If syncs reach Klaviyo rate limits, configure fewer metrics or lower the Number of concurrent threads setting.

:::note Klaviyo’s Get Events endpoint doesn’t support custom metrics in the metric_id filter. Filter only on built-in metrics, such as Placed Order or Opened Email. :::

A metric ID added to an existing configuration syncs forward from the stream’s current cursor position. The connector doesn’t backfill older events for that metric. To sync its history, update the configuration and then clear the affected stream.

Find metric IDs under Analytics > Metrics in your Klaviyo account. Alternatively, use the Metrics stream to list every available metric and its ID.

Performance considerations

Klaviyo rate limits restrict the connector. When Klaviyo responds with 429, the connector checks the response’s Retry-After header. It waits for the specified number of seconds, then retries. Burst and steady limit waits typically last from seconds to about one minute. Syncs usually recover without any action from you.

The connector waits up to 10 minutes for each retry. If Retry-After specifies a longer wait, the sync fails with a rate limit error. This usually affects the reporting endpoints for the Campaign Values Reports and Flow Series Reports streams. These endpoints enforce 225 daily requests alongside their burst and steady limits. After a sync exhausts this quota, Retry-After contains the seconds remaining until the next daily reset. That wait can last many hours. To stay within the quota, narrow your requested conversion metrics with Report Stream Conversion Metric IDs. You can also sync these streams less often. Alternatively, move them to a separate connection so quota failures don’t interrupt your other streams. Connector versions before 3.0.1 waited for the complete Retry-After value on every stream. This stalled the sync until Airbyte stopped and restarted the attempt.

Create an issue if you encounter rate limit issues that retries don’t resolve.

The Campaigns Detailed stream includes estimated_recipient_count and campaign_message alongside information from the Campaigns stream. Fetching this extra data takes more time.

The Lists Detailed stream includes profile_count alongside information from the Lists stream. Klaviyo API limitation means fetching this extra data takes more time.

The Events Detailed stream includes the name field for the metric relationship, alongside info.

The Profiles stream can encounter temporary API errors under heavy load. Use the Disable Fetching Predictive Analytics setting to increase sync success rates. This setting affects only the predictive_analytics field. The connector always fetches profile subscription and consent data, which remains unaffected.

:::warning With the Disable Fetching Predictive Analytics setting, records in the Profiles stream no longer contain the predictive_analytics field. Workflows that depend on this field will stop working. :::

Data type map

Integration TypeAirbyte Type
stringstring
numbernumber
arrayarray
objectobject

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
4.0.52026-11-1091622Update dependencies
4.0.42026-11-0390629Update dependencies
4.0.32026-10-2789977Update dependencies
4.0.22026-10-2089305Update dependencies
4.0.12026-10-1388714Update dependencies
4.0.02026-10-0785352Upgrade to Klaviyo API revision 2026-01-15 ahead of the 2024-10-15 retirement. Syncs and destinations are not affected, and the connector auto-upgrades at the deadline; only downstream consumers of campaigns and campaigns_detailed need to move to new nested paths. In campaigns and campaigns_detailed, attributes.send_strategy.options_static.datetime/is_local/send_past_recipients_immediately, options_throttled.datetime/throttle_percentage and options_sto.date move to attributes.send_strategy.datetime, .options.is_local, .options.send_past_recipients_immediately, .throttle_percentage and .date. In campaigns_detailed, campaign_messages[].attributes.channel/label/content/render_options move to campaign_messages[].attributes.definition.*. SMS messages no longer carry a label (Klaviyo stopped generating one). Refresh the source schema to pick up the new fields. See the migration guide
3.0.62026-10-0687223Update dependencies
3.0.52026-09-2286678Update dependencies
3.0.42026-09-1586109Update dependencies
3.0.32026-09-1085217Send the global_exclusions cursor filter to Klaviyo, with a one-hour lookback window, so incremental syncs no longer re-page all profiles; a first/stateless sync still returns the full suppression list.
3.0.22026-09-0884635Update dependencies
3.0.12026-08-2184908Fail fast with a rate limit error instead of sleeping for hours when Klaviyo returns a daily-quota Retry-After
3.0.02026-08-1475495Emit one record per calendar day with scalar statistics in flow_series_reports, add a reporting lookback window for that stream, and align both report streams to whole-day windows to stop boundary double-counting (refresh the schema and clear both report streams)
2.21.12026-08-1183991Update dependencies
2.21.02026-08-0775301Add optional metric ID filtering for the events and events_detailed streams
2.20.02026-08-0561338Sync all metric definitions in the metrics stream regardless of the configured start date (existing connections: clear/reset the metrics stream to backfill older metric definitions)
2.19.32026-07-2883194Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override
2.19.22026-07-281082Roll Cloud back to 2.19.0 — 2.19.1 is built on SDM 7.23.7, which breaks bundled custom components
2.19.12026-07-2882475Update dependencies
2.19.02026-07-1581637Default start date to one year back when not provided
2.18.62026-07-1481870Update dependencies
2.18.52026-06-3081120Update dependencies
2.18.42026-06-2380514Update dependencies
2.18.32026-06-2276919fix(source-klaviyo): Add missing unsubscribe and spam complaint fields to reporting streams
2.18.22026-06-1679898Update dependencies
2.18.12026-06-0979342Update dependencies
2.18.02026-06-0476941Add new segments stream
2.17.92026-06-0278784Update dependencies
2.17.82026-04-2877313Update dependencies
2.17.72026-04-2577008Fix sync failure when conversion metrics do not support values data queries in flow_series_reports and campaign_values_reports streams
2.17.62026-04-2175707Update dependencies
2.17.52026-04-1675180Restore subscriptions field to profiles stream additional-fields[profile] parameter, fixing a regression introduced in v2.16.x where the subscriptions data was no longer fetched from the Klaviyo API
2.17.42026-04-1376276Rename “concurrent workers” to “concurrent threads” in connector spec
2.17.32026-03-1774995Update dependencies
2.17.22026-03-1074435Update dependencies
2.17.12026-03-0373958Update dependencies
2.17.02026-02-1973642Add new analytics streams: Flow Series Reports and Campaign Values Reports
2.16.152026-02-1773540Update dependencies
2.16.142026-02-1073058Update dependencies
2.16.132026-02-0372750Update dependencies
2.16.122026-01-2072040Update dependencies
2.16.112026-01-1970208Add chunking to events_detailed stream to fix full refresh stalling and incremental mode returning zero rows
2.16.102026-01-1471461Update dependencies
2.16.92025-12-1870783Update dependencies
2.16.82025-11-2570028Update dependencies
2.16.72025-11-1869457Update dependencies
2.16.62025-10-2968983Update dependencies
2.16.52025-10-2168298Update dependencies
2.16.42025-10-1468028Update dependencies
2.16.32025-10-0767517Update dependencies
2.16.22025-09-3066643Update dependencies
2.16.12025-09-0966070Update dependencies
2.16.02025-09-0865990Revert the v2.15.0 change, which caused subscriptions data to stop being fetched on the profiles stream (fixed in v2.17.5)
2.15.02025-09-0765935Fetch subscriptions data on the profiles stream
2.14.222025-08-2565509Fix custom migrations to reference DeclarativeStream Pydantic model instead of runtime component
2.14.212025-08-2365317Update dependencies
2.14.202025-08-0964618Update dependencies
2.14.192025-08-0264210Update dependencies
2.14.182025-07-2663815Update dependencies
2.14.172025-07-1963482Update dependencies
2.14.162025-07-1263154Update dependencies
2.14.152025-07-0562631Update dependencies
2.14.142025-06-2862167Update dependencies
2.14.132025-06-2161858Update dependencies
2.14.122025-06-1460653Update dependencies
2.14.112025-05-1059260Update dependencies
2.14.102025-04-2958123Add missing fields for events_detailed stream for attributions
2.14.92025-04-2658192Update dependencies
2.14.82025-04-1257751Update dependencies
2.14.72025-04-0557033Update dependencies
2.14.62025-03-2956634Update dependencies
2.14.52025-03-2256017Update dependencies
2.14.42025-03-1455772Add back step to streams that can process date ranges in parallel
2.14.32025-03-0855479Update dependencies
2.14.22025-03-0354720Add event_properties option to events request
2.14.12025-03-0154770Update dependencies
2.14.02025-02-2654166Migrate to Manifest-only
2.13.12025-02-2254369Update dependencies
2.13.02025-02-1851551Upgrade to API v2024-10-15
2.12.12025-02-1552710Update dependencies
2.12.02025-02-1153223Add API Budget
2.11.112025-01-2752563Fix lists_detailed incremental sync
2.11.102025-01-2552285Update dependencies
2.11.92025-01-1151198Update dependencies
2.11.82025-01-0951010Fix AirbyteMessage serialization with integers bigger than 64 bits
2.11.72025-01-0450893Update dependencies
2.11.62024-12-2850653Update dependencies
2.11.52024-12-2150088Update dependencies
2.11.42024-12-1449250Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
2.11.32024-12-1249144Update dependencies
2.11.22024-12-0248748Bump CDK to evict non retriable requests to avoid high memory usage
2.11.12024-11-2648710Retry on “Temporary failure in name resolution”
2.11.02024-11-1848452Enable concurrency for syncs that don’t have client-side filtering
2.10.142024-11-0748391Remove custom datetime cursor dependency
2.10.132024-11-0548331Update dependencies
2.10.122024-10-2947797Update dependencies
2.10.112024-10-2847043Update dependencies
2.10.102024-10-1446741Add checkpointing to events stream to improve large syncs after clear data
2.10.92024-10-1246787Update dependencies
2.10.82024-10-0546503Update dependencies
2.10.72024-09-2846174Update dependencies
2.10.62024-09-2145813Update dependencies
2.10.52024-09-1445530Update dependencies
2.10.42024-09-0745244Update dependencies
2.10.32024-08-3145064Update dependencies
2.10.22024-08-3044930Fix typing in profiles stream for field attributes.location.region
2.10.12024-08-2444628Update dependencies
2.10.02024-08-1844366Add field[metrics] to events stream
2.9.42024-08-1744317Update dependencies
2.9.32024-08-1243806Update dependencies
2.9.22024-08-1043613Update dependencies
2.9.12024-08-0343247Update dependencies
2.9.02024-08-0142891Migrate to CDK v4.X and remove custom BackoffStrategy implementation
2.8.22024-07-3142895Add config option disable_fetching_predictive_analytics to prevent 503 Service Unavailable errors
2.8.12024-07-2742664Update dependencies
2.8.02024-07-1942121Migrate to CDK v3.9.0
2.7.82024-07-2042185Update dependencies
2.7.72024-07-0840608Update the events_detailed stream to improve efficiency using the events API
2.7.62024-07-1341903Update dependencies
2.7.52024-07-1041548Update dependencies
2.7.42024-07-0941211Update dependencies
2.7.32024-07-0640770Update dependencies
2.7.22024-06-2640401Update dependencies
2.7.12024-06-2240032Update dependencies
2.7.02024-06-0839350Add events_detailed stream
2.6.42024-06-0638879Implement CheckpointMixin for handling state in Python streams
2.6.32024-06-0438935[autopull] Upgrade base image to v1.2.1
2.6.22024-05-0837789Move stream schemas and spec to manifest
2.6.12024-05-0738010Add error handler for 5XX status codes
2.6.02024-04-1937370Add streams campaigns_detailed and lists_detailed
2.5.02024-04-1536264Migrate to low-code
2.4.02024-04-1136989Update Campaigns schema
2.3.02024-03-1936267Pin airbyte-cdk version to ^0
2.2.02024-02-2735637Fix predictive_analytics field in stream profiles
2.1.32024-02-1535336Added type transformer for the profiles stream.
2.1.22024-02-0935088Manage dependencies with Poetry.
2.1.12024-02-0734998Add missing fields to stream schemas
2.1.02023-12-0733237Continue syncing streams even when one of the stream fails
2.0.22023-12-0533099Fix filtering for archived records stream
2.0.12023-11-0832291Add logic to have regular checkpointing schedule
2.0.02023-11-0332128Use the latest API for streams campaigns, email_templates, events, flows, global_exclusions, lists, and metrics
1.1.02023-10-2331710Make start_date config field optional
1.0.02023-10-1831565Add new known fields for ‘events’ stream
0.5.02023-10-1931611Add date-time format for datetime field in Events stream
0.4.02023-10-1831562Add archived field to Flows stream
0.3.32023-10-1331379Skip streams that the connector no longer has access to
0.3.22023-06-2027498Do not store state in the future
0.3.12023-06-0827162Anonymize check connection error message
0.3.02023-02-1823236Add Email Templates stream
0.2.02023-03-1323968Add Profiles stream
0.1.132023-02-1322942Specified date formatting in specification
0.1.122023-01-3022071Fix Events stream schema
0.1.112023-01-2722012Set AvailabilityStrategy for streams explicitly to None
0.1.102022-09-2917422Update CDK dependency
0.1.92022-09-2817304Migrate to per-stream state.
0.1.62022-07-2014872Increase test coverage
0.1.52022-07-1214617Set max_retries = 10 for lists stream.
0.1.42022-04-1511723Enhance klaviyo source for flows stream and update to events stream.
0.1.32021-12-098592Improve performance, make Global Exclusions stream incremental and enable Metrics stream.
0.1.22021-10-196952Update schema validation in SAT
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.