OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Customer export returns selected profile records.
Customer.io export customer data ↗
Export customer data · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Asynchronous export metadata leads to downloadable customer files.
Customer.io export customer data ↗
Export metadata / download endpoint · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Export filters combine segments and attributes with AND/OR/NOT.
Customer.io export customer data ↗
filters · Checked 2026-10-16
Access cost barrier -
-
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish access cost barrier.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish third-party eligibility.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Downstream permission -
-
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish downstream permission.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Track v1 PUT creates or updates a customer profile by identifier.
Customer.io Track v1 add or update a customer ↗
Add or update a customer · Checked 2026-10-16
Custom application path -
-
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish custom application path.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Reporting Webhooks notify external services of subscribed customer/message events.
Customer.io Reporting Webhooks delivery contract ↗
Reporting webhooks / Set up webhooks · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
App export documents ten-per-second limit and Retry-After.
Customer.io export customer data ↗
429 response · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Customer event notifications support changes; complete deletion identity coverage unresolved.
Customer.io Reporting Webhooks delivery contract ↗
Reporting webhook format / Customer · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Reporting Webhooks backlog/retry for seven days; durable consumer replay unestablished.
Customer.io Reporting Webhooks delivery contract ↗
Timeouts and failures · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Export endpoint supplies metadata for downloading the selected customer export.
Customer.io export customer data ↗
Export customer data · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish post-cancellation access.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Portable selected profiles; full activity/history and automation reconstruction unverified.
Customer.io export customer data ↗
filters / attributes · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
Customer code handles reporting events and invokes fixed APIs.
Customer.io Reporting Webhooks delivery contract ↗
Set up webhooks · Checked 2026-10-16
Rights to custom logic -
-
Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts.
The reviewed Customer.io route does not establish rights to custom logic.
Customer.io export customer data ↗
Reviewed route documentation; applicable scoring contract not established · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
App API keys have selected scopes; Track credentials use a Site ID and secret with Basic authentication. The appropriate US or EU endpoint matters because cross-region redirects may traverse US servers.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
POST /exports/customers filters people by segments and attributes, then returns metadata used to download the export. This route does not establish all activity history or complete automation reconstruction.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Scoped Journeys App API key | API key | Customer | Not confirmed | app api bearer key; correct us/eu workspace region | 2026-10-16 |
| Track v1 customer profile writes | HTTP Basic | Customer | Not confirmed | site id and api key; customer identifier settings; separate from app api | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Most App API endpoints permit ten requests per second; export errors include Retry-After. Track has separate ingestion guidance rather than the same fixed budget. Lowest-plan export entitlement remains unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Track v1 PUT /customers/{identifier} creates or updates a customer profile. Customer identity settings and identifier rules must be checked before mutating records.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Reporting Webhooks use a four-second acknowledgement timeout and retry with backoff for seven days, blocking subsequent delivery behind failures. Workflow-action webhook retries follow a different contract.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Customer event notifications support changes; complete deletion identity coverage unresolved. | Customer.io Reporting Webhooks delivery contract ↗Reporting webhook format / CustomerChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Reporting Webhooks backlog/retry for seven days; durable consumer replay unestablished. | Customer.io Reporting Webhooks delivery contract ↗Timeouts and failuresChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customers can download the selected people export for external use. Full event history, message content, attachments and independently runnable native workflows remain unverified.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External integrations can process exports and react to reporting events. A seven-day retry backlog is not a consumer-controlled event journal (native artifact rights and cancellation retrieval remain unresolved).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Customer export returns selected profile records. | Customer.io export customer data ↗Export customer dataChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Asynchronous export metadata leads to downloadable customer files. | Customer.io export customer data ↗Export metadata / download endpointChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Export filters combine segments and attributes with AND/OR/NOT. | Customer.io export customer data ↗filtersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish third-party eligibility. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish access cost barrier. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish downstream permission. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Track v1 PUT creates or updates a customer profile by identifier. | Customer.io Track v1 add or update a customer ↗Add or update a customerChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish custom application path. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Reporting Webhooks notify external services of subscribed customer/message events. | Customer.io Reporting Webhooks delivery contract ↗Reporting webhooks / Set up webhooksChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. App export documents ten-per-second limit and Retry-After. | Customer.io export customer data ↗429 responseChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Export endpoint supplies metadata for downloading the selected customer export. | Customer.io export customer data ↗Export customer dataChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish post-cancellation access. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Customer code handles reporting events and invokes fixed APIs. | Customer.io Reporting Webhooks delivery contract ↗Set up webhooksChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Customer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. The reviewed Customer.io route does not establish rights to custom logic. | Customer.io export customer data ↗Reviewed route documentation; applicable scoring contract not establishedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedCustomer.io Journeys App API customer export, Track v1 profile writes and Reporting Webhooks; Pipelines and workflow-action webhooks have separate contracts. Portable selected profiles; full activity/history and automation reconstruction unverified. | Customer.io export customer data ↗filters / attributesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum-plan API/export entitlement and access charges
- Arbitrary third-party application eligibility
- Complete deletion identity coverage
- Consumer-controlled replay and native workflow portability
- Full history and post-cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.