---
title: "Magento Integration Guide | Tajo"
description: "Connect Adobe Commerce (Magento) to Tajo through the Commerce REST API for customer, order, and product sync"
url: https://tajo.io/docs/ecommerce-platforms/magento/
markdown: https://tajo.io/docs/ecommerce-platforms/magento.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
---

# Magento Integration Guide

[Set Noa](https://tajo.io/set-noa/)

Tajo connects to Adobe Commerce (Magento 2) through the **Commerce REST API**. There is no Tajo extension to install in your Magento codebase — the connection uses an integration token, which keeps your store’s deploy pipeline untouched.

Magento is currently an **onboarding-built connection**: unlike Shopify and WooCommerce, it is not yet self-serve, and your Tajo team wires the sync as part of onboarding. The [connector implementation status](https://tajo.io/docs/connectors/magento/) tracks where it stands. The store-side preparation below is everything Magento needs from your end, and it works with stock Magento — no code changes.

## Prerequisites

- **Adobe Commerce / Magento Open Source 2.4+**
- Admin access to create an integration token
- HTTPS on your store (required for token auth)
- **Tajo account** with an active subscription

## Step 1: Create a Magento integration token

1. In Magento admin, go to **System → Extensions → Integrations → Add New Integration**.
2. Name it `Tajo`, set your admin password, and under **API** grant read access to **Customers**, **Sales**, and **Catalog** resources.
3. Save, then **Activate** the integration and copy the **Access Token**.

Tajo authenticates with `Authorization: Bearer <access token>` against your store’s REST base URL (`https://yourstore.com/rest/V1/`).

## Step 2: Hand the connection to your Tajo team

Share with your Tajo onboarding contact:

| Field | Value |
| --- | --- |
| **Store URL** | `https://yourstore.com` |
| **Access token** | The integration token from Step 1 |

The connection is validated with a read-only request before any sync starts. Rotate the token in Magento at any time to revoke access.

## What a Magento connection syncs

- **Customers** — identity fields and account metadata for contact resolution; marketing consent is never inferred from an account’s existence
- **Orders** — purchase history, totals, currency, status, and line items for lifecycle segmentation and win-back automations
- **Products and categories** — catalog structure for interest segmentation and product-aware campaigns

Historical import runs first, then incremental sync keeps Tajo current by polling modified records. Real-time storefront events (carts, checkouts in progress) require an in-store extension, which Magento does not get today — order-based automations remain fully supported through sync.

## Marketing automation

Automations (email, SMS, WhatsApp via Brevo and other providers) are configured in Tajo using the synced data — for example post-purchase follow-ups on new orders, win-back on lapsed customers, and product-interest campaigns from category history.

## Troubleshooting

| Symptom | Cause and fix |
| --- | --- |
| 401 from the store | The integration token was regenerated or the integration deactivated — reactivate and update the token in Tajo |
| Customers sync but orders don’t | The integration’s API grants are missing the **Sales** resource |
| Slow initial import | Large stores import in pages; your Tajo contact can report progress at any point |

## Next steps

- [Magento connector reference](https://tajo.io/docs/connectors/magento/) — implementation status and technical notes
- [Customer sync](https://tajo.io/docs/skills/data-sync/customer-sync/) — mapping Magento customers into your system of record