Advanced Analytica Advanced Analytica: IBOM
← All connectors
Customer.io logo

Source connector

Customer.io

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

Version 1.1.7 certified generally available

Customer.io

Use this page to set up and reference the Customer.io source connector.

The connector reads a Customer.io workspace through the App API. It reads automations and their actions, one-time sends and their variants, and API-triggered broadcasts and their actions. It also reads transactional message templates, sender identities, segments and their usage, subscription topics, object types, workspaces and reporting webhooks. Other data includes snippets, collections, message deliveries, the activity log, people, segment memberships and email suppression lists. Stream names follow the App API. Automations are campaigns, while one-time sends are newsletters. messages contains deliveries, with one record for each message sent to one person.

Prerequisites

  • A Customer.io account where you’re an Account Admin or Member with the account-level Manage API credentials permission to create the key
  • A private API key (sk_) or existing legacy App API key for the workspace you want to sync. Public API keys (pk_) and Track API keys don’t work.
  • Your Customer.io account’s Region, either US or EU
  • The IP addresses Airbyte connects from on your allowlist, if your account restricts API access by IP address

Set up the connector

1. Set up Customer.io

The connector uses bearer authentication with a private API key. Existing legacy App API keys still work, but Customer.io no longer allows you to create them. You can keep using an existing App API key for the workspace you want to sync. If you do, skip the key creation steps below.

  1. Confirm that you can manage API credentials. You must be an Account Admin or Member with the account-level Manage API credentials permission (Manage your API credentials).
  2. In Customer.io, go to Account Settings > API Credentials and click Create API key.
  3. Select the workspace you want to sync, then choose Private API key. Under Used in, leave the integration type empty if you’ll only use the key for the App API. Name the key and click Create private key (Create a key). Don’t choose Public API key or Track site ID + key. Neither can read the App API data this connector syncs.
  4. Copy the private key immediately and store it securely. Customer.io shows it only once. If you lose it, create a new key.
  5. Find your account’s region, either US or EU. Account Admins can find it under Settings > Account Settings > Data and Privacy. Other roles can’t see it, so ask an Account Admin (How do I know what region my data is in?). The wrong region causes the connection test to fail with a 401 error.
  6. If your workspace restricts API access by IP address, allow the addresses Airbyte connects from. Use the Airbyte Cloud IP addresses for Airbyte Cloud or your deployment’s public IP addresses for Self-Managed Airbyte. On the API Credentials page, under IP address allowlist, click Add IP address. Enter an address, select the workspace and click Add IP address, once for each address (Restrict API access by IP address). Customer.io denies addresses missing from the list, even when the key is valid.

2. Set up the connector in Airbyte

  1. In the Airbyte UI, go to Sources and click + New source.
  2. Select Customer.io from the list.
  3. Enter a name for the source.
  4. Complete the fields below, then click Set up source. You’ll find Region, Start Date and the other optional fields under Optional fields. Accounts in the EU region must set Region.

App API Key: Enter the private API key (sk_) created in Step 1 for the workspace you want to sync. You can instead enter an existing legacy App API key. The field remains named App API Key, but accepts either credential. Airbyte sends the credential as a bearer token. Public API keys (pk_) and Track API keys don’t work.

Region (optional, required for EU accounts): Select your Customer.io account’s data centre region. Choose US, the default, or EU. Account Admins can find it under Settings > Account Settings > Data and Privacy. The connector calls api.customer.io/v1 or api-eu.customer.io/v1. Customer.io doesn’t redirect App API requests to the other region. A region that doesn’t match your account causes a 401 error (Specifying your region in the API).

Start Date (optional): Enter a UTC date and time in the format YYYY-MM-DDTHH:MM:SSZ, such as 2023-01-01T00:00:00Z. Supported streams only sync records created or last updated at or after this value. This applies to incremental sync and Full Refresh mode. Automations, actions, one-time sends, broadcasts, transactional message templates, segments and snippets use their last update. messages uses creation time, while activities uses event time. Full-refresh-only streams, including newsletter_variants, people, segment_memberships and esp_suppressions, sync every record. Leave this field blank to sync all records. See Incremental sync and Start Date.

Messages Lookback Window (Days) (optional): Set how many days each incremental messages sync rereads before the last synced message. This brings later opens, clicks, conversions, bounces and unsubscribes into the destination. Customer.io can record conversions up to 90 days after a message is sent, opened or clicked (conversions). It records opens and clicks for up to 6 months (delivery metrics). A longer window keeps these metrics more complete. However, each sync requests one page for every 1,000 messages sent during the window. Enter 1 to 180 days. The default is 30.

Activities Lookback Window (Days) (optional): Set how many days each incremental activities sync rereads before the last synced activity. Customer.io can record an activity with a time well before processing it. This can happen when it merges an anonymous person’s events into a profile or receives a backdated event (Filtering Logs). An incremental sync skips activities arriving later than this window. Customer.io guarantees 30 days of activities, so a 30-day window covers them all. A longer window skips fewer late activities. However, each sync requests one page for every 100 activities in the window. Enter 1 to 30 days. The default is 7.

Sending Domains for ESP Suppressions (optional): Enter your email sending domains in lowercase, such as mail.example.com. Customer.io lists them under Settings > Workspace Settings > Email. esp_suppressions reads each Customer.io email service provider (ESP) suppression list once for each domain. It records the domain on every row. Customer.io suppresses an address on the domain where it bounced or was reported as spam (suppressions across domains). If you send from multiple domains, enter them all. Leave this field empty to read each list once without a domain filter. The domain column will then be empty. You don’t need this field if you send through your own SMTP server.

Number of Concurrent Workers (optional): Set how many requests Airbyte sends to Customer.io simultaneously across all streams. Every request counts towards Customer.io’s workspace limit of 10 requests per second (see Performance considerations). Increasing the value beyond about 5 rarely makes a sync faster. Enter 2 to 10. The default is 3.

When you click Set up source, Airbyte tests the connection by reading automations (campaigns). If the test returns a 401 or 403 error, see Troubleshooting.

Supported sync modes

The Customer.io source connector supports these sync modes:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncYes
NamespacesNo

Ten streams support incremental sync. The other eleven support full refresh only. No stream marks records deleted in Customer.io. See Limitations & Troubleshooting.

Supported streams

New connections select streams marked Yes under Selected by default. Select other streams when you need them.

StreamCustomer.io resourcePrimary keyCursorSync modesSelected by default
campaignsAutomationsidupdatedFull Refresh, IncrementalYes
campaigns_actionsAutomation actionsidupdated, per automationFull Refresh, IncrementalYes
newslettersOne-time sendsidupdatedFull Refresh, IncrementalYes
broadcastsAPI-triggered broadcastsidupdatedFull Refresh, IncrementalYes
broadcast_actionsBroadcast actionsbroadcast_id, idupdated, per broadcastFull Refresh, IncrementalNo
newsletter_variantsOne-time send variantsnewsletter_id, idNoneFull RefreshNo
transactional_messagesTransactional messages: templates, not deliveriesidupdated_atFull Refresh, IncrementalYes
sender_identitiesSender identitiesidNoneFull RefreshNo
segmentsSegmentsidupdated_atFull Refresh, IncrementalYes
segment_usageSegment dependenciessegment_idNoneFull RefreshNo
subscription_topicsSubscription topicsidNoneFull RefreshNo
object_typesObject typesidNoneFull RefreshNo
workspacesWorkspacesidNoneFull RefreshNo
reporting_webhooksReporting webhooksidNoneFull RefreshNo
snippetsSnippetsnameupdated_atFull Refresh, IncrementalNo
collectionsCollectionsidNoneFull RefreshNo
messagesMessages: deliveriesidcreatedFull Refresh, IncrementalNo (personal data)
activitiesActivitiesidtimestampFull Refresh, IncrementalNo (personal data)
peopleCustomers with their attributes and devicescio_idNoneFull RefreshNo (personal data)
segment_membershipsCustomers in a segmentsegment_id, cio_idNoneFull RefreshNo (personal data)
esp_suppressionsESP-suppressed emailssuppression_type, domain, emailNoneFull RefreshNo (personal data)

reporting_webhooks syncs each webhook’s endpoint URL after removing any username:password@ part. Tokens in the URL path or query string sync exactly as Customer.io returns them (reporting webhooks FAQ). New connections don’t select this stream. Select it only when the destination can store these tokens. Connections set to Propagate all field and stream changes add and sync it automatically after upgrading to 0.7.0. To stop syncing it, deselect the stream and clear its destination data.

workspaces lists every workspace in the account. It includes message counts for the current billing period and current totals for people and objects. Customer.io caches these values for up to two hours. The records have no update time. Use Full Refresh | Overwrite for the latest counts. Use Full Refresh | Append to keep one snapshot from each sync.

collections lists each collection’s name, schema, row count and size, but not its contents. It supports full refresh only, so every sync contains the current counts.

messages contains one record for each delivery, meaning one message sent to one person. Each record includes when every metric was recorded, including delivered, opened, clicked and converted. Syncs read deliveries in 30-day creation-time windows, with one request for every 1,000 deliveries. Start Date applies to the creation time. Customer.io records opens and clicks for up to 6 months. It records conversions for up to 90 days. Each incremental sync rereads deliveries created during the last Messages Lookback Window (Days). The default is 30 days, with a maximum of 180. Use Incremental | Append + Deduped. Increase the setting or occasionally run a full refresh for complete metrics. Reduce it to shorten syncs in high-volume workspaces. Records include the recipient’s address and identifiers, subject line, and per-person open and click times.

activities is the workspace activity log, with one record for each event. Events include sent, opened and clicked messages, tracked events, page views, screen views and attribute changes. The log includes events for deleted people. Customer.io guarantees only the last 30 days. Sync at least every 30 days and use Incremental | Append + Deduped to retain older history. Expect several records for each sent message. The first sync reads every retained activity, with 100 records per request. Each incremental sync rereads activities from the last Activities Lookback Window (Days) before the newest synced activity. The default is 7 days, with a maximum of 30. Customer.io can record an activity with a time well before processing it. Activities arriving after the window are skipped. Set the window to 30 to cover Customer.io’s guaranteed 30 days. Customer.io’s list can place a page of 100 older activities before newer activities. If that page falls outside the window, the newer activities are also skipped. Records include email addresses, your person IDs, event and attribute values, and page URLs. They also include IP addresses and user agents for opens and clicks.

people contains one record for each person, keyed by cio_id. Customer.io assigns this ID to every person. Records include every profile attribute, identifier, subscription preference and device push token. Each sync reads every profile. It uses one request for every 1,000 people to find them, then one for every 100 to fetch them. Reading 1,000,000 people takes about 11,000 requests. At 10 requests per second, this takes at least 18 minutes. Start Date doesn’t apply. Full Refresh | Overwrite mirrors the workspace. Append retains deleted people.

segment_memberships contains one record for each person in each segment. Records include the person’s cio_id, ID and email address. The stream therefore contains the sum of all segment sizes, often several times the total number of people. Each request returns up to 30,000 members. Membership has no timestamps, so use Full Refresh | Overwrite. Append adds a complete copy during every sync. Segment members can be outdated while Customer.io calculates them when state is build. Archived segments aren’t included.

esp_suppressions contains one record for each address on every Customer.io email suppression list. These lists cover bounces, blocks, spam reports and invalid emails. A reason can repeat the address. Each sync makes one request for every 1,000 addresses on each list. It makes at least 4 requests, or 4 for each configured domain. Lifted suppressions leave the list without a record, so use Full Refresh | Overwrite. Append adds a complete copy during every sync. Customer.io suppresses an address on the sending domain where it bounced or received a spam report. If you use several domains, enter them in Sending Domains for ESP Suppressions. Each list is then read once for each domain, and records include their domain. A mistyped or unknown domain returns no records instead of an error. Lists can include addresses suppressed by other workspaces using the same sending domain. Your email provider stores suppressions when you use your own SMTP server, so deselect this stream.

messages, activities, people, segment_memberships and esp_suppressions contain personal data and aren’t selected by default. Connections set to Propagate all field and stream changes add and sync them automatically after upgrading to 0.8.0. To stop syncing them, deselect the streams and clear their destination data. Incremental and Append syncs retain rows for people later deleted or suppressed in Customer.io. You must therefore also handle erasure requests in the destination. If these streams return a 403 error, check that the key can read their data. Also confirm that the Airbyte IP addresses are on your allowlist, or deselect the streams.

Incremental sync and Start Date

Only deliveries support server-side time filtering, so Customer.io filters messages on the server. Other incremental streams use client-side cursors. Each sync reads the full list, although activities can stop early as described below. It emits records at or after the saved cursor minus one hour. For activities, it instead subtracts Activities Lookback Window (Days). Cursors use updated, updated_at or timestamp in Unix seconds. The lists aren’t sorted by cursor. A record edited during a sync can therefore fall behind the saved cursor. The one-hour lookback captures it during the next sync. The lookback adds no requests because each sync already reads the full lists. However, activities rereads its lookback window, with one request for every 100 activities. Records updated within the lookback before the saved cursor repeat until a newer change advances the cursor. Use Incremental | Append + Deduped. Incremental | Append stores these records as repeated rows. Both modes make the same requests for these streams. Incremental | Append + Deduped writes fewer rows. Full Refresh | Overwrite also removes records deleted in Customer.io.

campaigns_actions and broadcast_actions keep one cursor for each automation or broadcast. They request actions from every automation or broadcast, including parents last updated before the Start Date. This happens because changing an action doesn’t change its parent’s update time. The actions remain filtered by the Start Date. Actions from a newly added automation or broadcast don’t start from the Start Date. They start from the stream’s newest saved update time, minus the previous sync’s duration and one-hour lookback. Actions that retain an older update time arrive only after they change. This can affect a duplicated automation. Customer.io doesn’t document whether copied actions retain their update time.

messages reads 30-day creation-time windows. Each incremental sync begins Messages Lookback Window (Days) before the newest synced created. This brings metrics recorded after sending into the destination. activities reads newest records first. It stops at the first page without activity inside the cursor window. Customer.io guarantees only the last 30 days of activity. See the notes for both streams under Supported Streams for the trade-offs.

Start Date applies to streams supporting incremental sync, including in Full Refresh mode. These streams skip records created or last updated before that date. messages uses creation time, while activities uses event time. The eleven full-refresh streams ignore Start Date and sync every record. A future Start Date passes the connection check. Until that date, a sync only emits records changed while it runs. Leave Start Date blank to sync all records.

Performance

Customer.io limits most App API endpoints to 10 requests per second for each workspace (Rate Limits). Every App API call without a separate limit uses one shared bucket, including writes (Design Studio API rate limits). The connector shares this bucket with your other App API traffic. It limits itself to 10 requests per rolling second across all streams. It sends the number of simultaneous requests set by Number of Concurrent Workers, which defaults to 3. When other traffic fills the bucket, Customer.io returns 429 errors and the connector waits. See Troubleshooting.

These streams have the highest request costs:

  • campaigns_actions, broadcast_actions, newsletter_variants and segment_usage: one request for each automation, broadcast, one-time send or segment. Each additional actions page needs another request. Reading 1,000 one-time sends adds about 100 seconds of newsletter_variants requests.
  • messages: one request for every 1,000 deliveries, plus one for each 30-day window. Reading 10 million deliveries takes about 10,000 requests during the first sync. Every incremental sync rereads the lookback window. With a blank Start Date, about 690 empty windows since 1970 add roughly 70 seconds to the first sync. They add the same time to every sync while the workspace has no deliveries.
  • activities: one request for every 100 activities, with pages read sequentially. The first sync takes about 10,000 requests for every million activities. Incremental syncs read new activities, the lookback window and one additional page. With the default 7-day window, 100,000 daily activities take about 7,000 requests for each sync. This stream sends requests sequentially. Testing showed 0.3 to 0.6 seconds per request, giving a total of about 35 to 70 minutes.
  • people: one request for every 1,000 people, plus one for every 100. Reading 1,000,000 people takes about 11,000 requests and at least 18 minutes.
  • segment_memberships: one request for each segment and every 30,000 members. Reading 10 million memberships across 200 segments takes at most about 735 requests.
  • esp_suppressions: one request for every 1,000 addresses on each of the four suppression lists. This means at least 4 requests, multiplied by the number of configured domains.

Keep streams you don’t need unselected.

Limitations and troubleshooting

Connector limitations

The connector handles Customer.io HTTP errors as follows:

HTTP statusBehavior
401The sync fails with a configuration error: Customer.io rejected the key. See Troubleshooting.
403The sync fails with a configuration error: Customer.io denied the key access to the data. See Troubleshooting.
404On campaigns_actions, broadcast_actions, newsletter_variants, segment_usage and segment_memberships, the records of an automation, broadcast, one-time send or segment deleted during the sync are skipped. On other streams, the sync fails.
429Retried up to 30 times after the wait in the Retry-After header; with Retry-After: 1, that rides out about a minute of rate limiting. Customer.io leaves the header out when a daily quota is reached; the connector then backs off exponentially and fails the sync after about 17 minutes.
500, 502, 503, 504Retried with exponential backoff; the sync fails after about 17 minutes of errors.
  • Deletions: Customer.io omits deleted records from its lists, so no stream marks deletions. In Incremental and Append modes, deleted records retain their last version in the destination. Full Refresh | Overwrite mirrors the current state when Start Date is blank. With a Start Date, it retains only records last updated since that date. snippets use name as their key, and you can’t rename a snippet. A snippet copied under a new name arrives as a new record. Deleting the old snippet retains its last version, like any other deleted record.
  • Archived segments: Customer.io omits archived segments from its segment list. As a result, segments, segment_usage and segment_memberships skip them. A segment archived after an incremental sync retains its last destination row. You can archive a segment while archived automations or sent one-time sends still use it. That usage never reaches segment_usage.
  • Deprecated fields: Customer.io’s List automations reference marks campaigns.type, the trigger type, as “Sunsetting on March 30, 2025”. It also marks campaigns.msg_templates as deprecated. These values may arrive as null or stop arriving. Don’t build new reports using them.
  • Field types that differ from the API reference: campaigns_actions.id is a string, as Customer.io sends it, although the reference documents an integer. campaigns.actions[].id is an integer, so cast one side when joining them. broadcast_actions.id is cast to the documented integer. The campaigns fields audience.person_filters, audience.relationship_filters, object_attribute_triggers and relationship_attribute_triggers have no declared type. The reference types them as objects, but its examples show JSON strings. campaigns_actions.payload_android also has no declared type because the reference doesn’t document it. campaigns.webhook_id is cast to the documented integer when Customer.io sends a string of up to 18 digits. Other strings don’t match the declared integer. Typed destinations therefore store null and record the change in _airbyte_meta. messages also contains transactional_message_id and msg_template_id, which the reference’s response schema doesn’t declare. Version 1.0.0 changed the declared types of campaigns_actions.from_id and reply_to_id. It also changed newsletters.sent_at and four ID and tag arrays. See the migration guide.
  • Joins: object_types.id is a string because Customer.io sends object type IDs as strings. campaigns.object_type_id is an integer, so cast one side when joining them.
  • Variants: broadcast_actions contains one record for each message language variant. Every variant has the same multi_language_branch_action_id. newsletter_variants contains one record for each language or A/B test of a one-time send. Each record has its own id.
  • Hidden senders: sender_identities includes hidden senders. Use hidden to identify them.
  • Empty streams: subscription_topics remains empty until the workspace has subscription topics. A non-empty stream doesn’t mean the subscription centre is enabled. broadcasts and broadcast_actions remain empty without API-triggered broadcasts. activities can be empty after 30 days without activity.
  • Deliveries without content: a messages record with forgotten: true has content that Customer.io didn’t retain. For example, this can be a transactional message sent with message retention disabled.
  • Log warning: campaigns_actions logs “Parent state handling is not supported for CartesianProductStreamSlicer.” during every sync. This message is harmless and requires no action.

Troubleshooting

  • 401 errors: Customer.io rejected the key. Confirm it’s a private API key (sk_) or legacy App API key. It mustn’t be a public API key (pk_) or Track API key. Also confirm that you copied the complete key. Create a new private key if you lost the original. Check that Region matches your account (see Step 1). If your workspace restricts API access by IP address, add Airbyte’s connection addresses to the allowlist (Step 1). Customer.io doesn’t document which error a blocked address receives. Therefore, both the 401 and 403 messages mention this restriction. The connector’s error message still refers to an App API key. Private keys work in the same field.
  • 403 errors: Customer.io denied the key access to the stream’s data. Alternatively, Airbyte’s connection addresses aren’t on the allowlist. Use a key that can read the data, or deselect the stream.
  • 429 errors or slow syncs: your other App API traffic shares the limit of 10 requests per second. Schedule syncs when that traffic is low, sync less often or deselect expensive streams listed in Performance considerations.
  • 5xx errors: Customer.io returned temporary errors. If the sync fails after its retries, check Customer.io Status and sync again later.
  • Records missing from incremental streams: incremental streams skip records last updated before Start Date. activities skips activities dated more than Activities Lookback Window (Days) before the newest synced activity. Actions from a new automation or broadcast start from the stream’s newest saved update time. See Incremental sync and Start Date. For activities, increase Activities Lookback Window (Days). For other streams, move Start Date earlier or leave it blank, then clear the stream. Clearing also removes destination rows for records deleted in Customer.io. In Append modes, it also removes each record’s earlier versions. Don’t clear activities. Customer.io guarantees only the last 30 days, so clearing permanently removes older destination activity.
  • Repeated rows: Incremental | Append repeats records updated during the hour before the saved cursor on every sync. messages and activities also repeat their lookback windows. Use Incremental | Append + Deduped.

Changelog

Expand to review
VersionDatePull RequestSubject
1.1.72026-11-1091486Update dependencies
1.1.62026-11-0390493Update dependencies
1.1.52026-11-0290331Consolidate substream error handling into a single error handler; no behavior change
1.1.42026-10-2789851Update dependencies
1.1.32026-10-2089499Mark the connector as certified
1.1.22026-10-2089495Add the Customer.io OpenAPI spec to the documentation URLs
1.1.12026-10-2089163Update dependencies
1.1.02026-10-1288473Add worker and activity lookback options (7-day default) and declare fields seen in production
1.0.02026-10-0988159Declare from_id, reply_to_id and sent_at as integers and the item types of four ID and tag arrays
0.8.02026-10-0888158Add message, activity, people, segment membership and ESP suppression streams
0.7.02026-10-0888135Add subscription topic, object type, workspace, reporting webhook, snippet and collection streams
0.6.02026-10-0788130Add broadcast, newsletter variant, transactional message, sender identity and segment streams
0.5.02026-10-0788129Add rate limiting, Retry-After retries, clearer authentication errors, a one-hour lookback, and missing fields
0.4.172026-10-0687812Update dependencies
0.4.162026-09-2987129Update dependencies
0.4.152026-09-2286584Update dependencies
0.4.142026-09-1585996Update dependencies
0.4.132026-09-0885433Update dependencies
0.4.122026-08-1884549Update dependencies
0.4.112026-08-1183899Update dependencies
0.4.102026-08-0483394Update dependencies
0.4.92026-07-2882865Update dependencies
0.4.82026-07-2182368Update dependencies
0.4.72026-07-1481795Update dependencies
0.4.62026-06-3081036Update dependencies
0.4.52026-06-2380394Update dependencies
0.4.42026-06-1679829Update dependencies
0.4.32026-06-0979257Update dependencies
0.4.22026-06-0278639Update dependencies
0.4.12026-05-0877895Upgrade the base image to source-declarative-manifest 7.18.1
0.4.02026-05-0877819Add pagination, incremental sync, and EU region support
0.3.192025-08-2065113Update logo
0.3.182025-05-1160049Update dependencies
0.3.172025-05-0458875Update dependencies
0.3.162025-04-1957766Update dependencies
0.3.152025-04-0557225Update dependencies
0.3.142025-03-2956546Update dependencies
0.3.132025-03-2255918Update dependencies
0.3.122025-03-0855311Update dependencies
0.3.112025-03-0154942Update dependencies
0.3.102025-02-2254374Update dependencies
0.3.92025-02-1851670Update dependencies
0.3.82025-01-1151062Update dependencies
0.3.72025-01-0450582Update dependencies
0.3.62024-12-2149999Update dependencies
0.3.52024-12-1449490Update dependencies
0.3.42024-12-1248923Update dependencies
0.3.32024-11-0548225Update dependencies
0.3.22024-10-2847464Update dependencies
0.3.12024-08-1744196Bump source-declarative-manifest version
0.3.02024-08-1644158Refactor connector to manifest-only format
0.2.152024-08-1243889Update dependencies
0.2.142024-08-1143513Update dependencies
0.2.132024-08-0443185Update dependencies
0.2.122024-07-2842631Update dependencies
0.2.112024-07-2142219Update dependencies
0.2.102024-07-1441808Update dependencies
0.2.92024-07-1041389Update dependencies
0.2.82024-07-1041225Update dependencies
0.2.72024-07-0740883Update dependencies
0.2.62024-06-3040624Update dependencies
0.2.52024-06-2738318Make the connector compatible with Connector Builder
0.2.42024-06-2640369Update dependencies
0.2.32024-06-2339953Update dependencies
0.2.22024-06-0538980[autopull] Upgrade base image to v1.2.1
0.2.12024-05-3138812[autopull] Migrate to base image and poetry
0.2.02023-08-2929385Migrate TS CDK to Low code
0.1.232021-11-09126Add Customer.io source
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.