Adobe Commerce (Magento)
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Adobe Commerce (Magento) to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your Adobe Commerce (Magento 2) store URL and API credentials to pull your store data into the PostHog Data warehouse.
The recommended way to connect is an integration access token: in the admin go to System > Extensions > Integrations, create an integration, grant it read access to Sales, Catalog, Customers and Carts, then activate it and copy the Access Token.
On Magento 2.4.4 and later, integration tokens are rejected as bearer tokens until you set Stores > Configuration > Services > OAuth > Access Token Expiration > Allow OAuth Access Tokens to be used as standalone Bearer tokens to Yes. If you can't change that setting, connect with an admin username and password instead and PostHog will mint a short-lived admin token for each sync.
Configuration
| Option | Type | Required |
|---|---|---|
Store URL | text | Yes |
Store code (optional) | text | No |
Authentication method | select | Yes |
Linking Adobe Commerce (Magento) to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Adobe Commerce (Magento)
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
orders | Sales orders placed in the store, with their totals, status, addresses, payment and line items. | Incremental, Full refresh | updated_at | — |
invoices | Invoices issued against orders, recording the amounts captured for a set of order line items. | Incremental, Full refresh | updated_at | — |
shipments | Shipments dispatched against orders, with their packages, tracking numbers and shipped items. | Incremental, Full refresh | updated_at | — |
creditmemos | Credit memos (refunds) issued against orders, recording refunded amounts and returned items. | Incremental, Full refresh | updated_at | — |
transactions | Payment gateway transactions recorded against order payments (authorization, capture, refund, void). | Incremental, Full refresh | created_at | — |
products | Catalog products with their type, price, status, attribute set, custom attributes and media. | Incremental, Full refresh | updated_at | — |
categories | Catalog categories, one row per category in the tree, with its position, level and path. | Incremental, Full refresh | updated_at | — |
customers | Registered customer accounts with their identity, group, store scope and addresses. | Incremental, Full refresh | updated_at | — |
carts | Shopping carts (quotes), including active carts and the abandoned ones left behind at checkout. | Incremental, Full refresh | updated_at | — |
coupons | Coupon codes attached to cart price rules, including auto-generated codes and their usage limits. | Incremental, Full refresh | created_at | — |
customer_groups | Customer groups used for pricing, tax classes and cart price rule targeting. | Full refresh | — | — |
product_attributes | Product EAV attribute definitions, describing every field the catalog can store on a product. | Full refresh | — | — |
tax_classes | Tax classes that products and customer groups are assigned to when calculating tax rules. | Full refresh | — | — |
store_views | Store views configured on the instance — the storefront scope that localizes catalog and prices. | Full refresh | — | — |
store_groups | Store groups, the middle scope that binds a root category to a set of store views. | Full refresh | — | — |
websites | Websites configured on the instance — the outermost scope, owning customer accounts and base currency. | Full refresh | — | — |
countries | Directory of countries the instance knows about, with their ISO codes, locale names and regions. | Full refresh | — | — |