Bring customer, product and transaction data into Pika's decision chain under control.
Pika supports bringing customer, product and transaction data into the platform through Excel, CSV or the asynchronous REST Ingestion API to help establish the data foundation for downstream intelligence and decision layers.
The objective is not to imply a ready-made connector for every source system, but to bring usable data into the platform through Pika's confirmed ingestion paths and data contract.
How does data enter Pika?
Pika's confirmed ingestion paths are Excel/CSV batch-import flows and the asynchronous REST Ingestion API under /api/v1/ingest/.
These ingestion paths bring customer, product and transaction data into a context that downstream Customer Intelligence, Product Intelligence and decision layers can use.
Data → ingestion → intelligence → opportunity / decision → controlled action.
Evaluate the ingestion path against source-system and data scope.
Data Domain
Onboarding begins by defining which customer, product and transaction fields are required and which source system provides them.
Excel / CSV
Batch scenarios can use Excel (.xlsx) or CSV files with the available column-mapping flow.
REST Ingestion API
System-to-system transfer can use the asynchronous /api/v1/ingest/ endpoint, where an accepted request enters processing with a 202 Accepted response.
Idempotency
The X-Idempotency-Key in the REST ingestion contract helps control duplicate-ingestion risk when the same request is repeated.
Data onboarding is more than one file-upload screen. Source, data contract and ingestion method are evaluated together.
Bring data into the platform. Keep analytical responsibility in the correct layer.
Data onboarding establishes Pika's data-entry foundation. Customer evaluation remains in Customer Intelligence, product meaning in Product Intelligence, while opportunity and audience decisions remain in their relevant downstream product layers.
Data ingestion does not replace intelligence results or marketing decisions.
Evaluate data onboarding within the correct integration boundary.
C32 explains which confirmed ingestion paths can bring data into Pika's decision chain.
Related Pika Layers & Use Cases
Frequently Asked Questions
Which core data domains can be brought into Pika?
C32's confirmed core data context is customer, product and transaction data. The actual field set depends on the usage scenario and source-system contract.
Does Pika support Excel and CSV data onboarding?
Yes. Documented batch-import flows cover Excel (.xlsx) and CSV files with a column-mapping approach.
How does Pika's REST ingestion work?
The documented /api/v1/ingest/ endpoint operates asynchronously and accepts a request for processing with a 202 Accepted response.
What is X-Idempotency-Key used for?
In the REST ingestion contract it provides idempotency protection that helps control duplicate-ingestion risk when the same request is repeated.
Does Pika provide a ready-made native connector for every ERP, CRM or e-commerce system?
C32 makes no such guarantee. Actual source-system connectivity is evaluated against the data contract, REST API or file-import path.
Does a campaign automatically start when data enters Pika?
No. Data ingestion, intelligence, opportunity, audience and Campaign/Journey decisions remain separate product responsibilities.
Define the data scope. Choose the right ingestion path. Establish Pika's intelligence foundation.
Evaluate how your customer, product and transaction data can enter Pika through Excel, CSV or REST API using your own source system and usage scenario.