Overview
Customers sometimes ask for an example JSON file showing how data moves from Magento into Amperity.
This article explains how the Magento → Fivetran → Snowflake → Amperity data flow works, why a JSON example is not available, and why Fivetran is included in this integration.
How Data Flows into Amperity
When Magento is used as a data source, Amperity does not receive JSON files.
Data flows as follows:
Magento stores data in database tables
Fivetran connects directly to those tables and syncs the data
The synced data is loaded into Snowflake
Amperity reads the data from Snowflake tables
At no point does Magento send JSON payloads as part of this integration.
Why Fivetran Is Used
Fivetran is a service Amperity uses to transport data when a native Amperity connector for a source (like Magento) is not available.
Fivetran securely syncs data from Magento database tables into Snowflake so that Amperity can ingest it.
Customers do not need to manage Fivetran pipelines themselves—this is part of the Amperity-managed ingestion process.
Why a JSON Example Is Not Available
The Magento integration uses direct database synchronization, not file-based transfers.
Because no JSON files are created or transmitted, Amperity cannot provide a sample JSON file for this data flow.
Where to Review Sample Data
To understand the structure and content of the data Amperity ingests, review:
Magento database tables
Tables synced into Snowflake by Fivetran
These sources reflect the exact data Amperity consumes.
Key Takeaway
Amperity ingests Magento data from Snowflake tables, not from JSON files.
Fivetran is included as a managed data transport service used by Amperity when a native connector is not available.
Applies To
Magento data sources
Fivetran-managed integrations
Snowflake-backed Amperity environments