Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Event best practices
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Data · Integrations & data sources

Magento

Connect a Magento store as a data source: the integration credentials it needs, the customers and orders it syncs, how its fields map to Instasent attributes, and how to map its marketing status to consent.

On this page▾
  • How to connect
  • What it syncs
  • The events it brings in
  • Field mapping
  • Consent mapping

Magento is the native connector for Magento stores. Once connected, it syncs your store's customers and orders into Instasent so your audience and purchase events stay current.

Only Magento Community Edition 2.x is supported.

How to connect

Magento connects with an API key: you create an integration in your store first and paste its credentials into Instasent, along with your store domain. A Magento integration hands you four values — a Consumer Key and Consumer Secret, and an Access Token and Access Token Secret.

Create the integration in Magento before connecting. The panel won't let you continue without valid credentials.

  1. 1

    Create an integration in Magento

    In your Magento admin, go to System → Integrations → Add New Integration. Grant access to all resources, and leave the Callback URL and Identity Link URL empty. Activate the integration to get the tokens — Magento then shows you the Consumer Key, Consumer Secret, Access Token and Access Token Secret.

  2. 2

    Add the data source

    In Data sources, select Add data source and choose Magento from the Integrations section.

  3. 3

    Enter your credentials and connect

    On the Connect step, fill in your Shop domain, the Store Code (usually default — you'll find it under Stores → All Stores), and the four integration values: Consumer Key, Consumer Secret, Access Token and Access Token Secret. Then connect.

  4. 4

    Initial import

    The connector imports your existing customers and orders, then keeps syncing periodically.

After connecting, the wizard continues through Mapping, Merge and Tags, the same steps as a CSV import.

The Magento connector page: what it brings into Instasent and the contact fields it maps, with Connect Magento to start.

What it syncs

  • Contacts — your store's customers, with name, email and phone.
  • Orders — purchase events for use in segments and automations.

The direction is one-way, from Magento into Instasent, with a periodic sync that keeps contacts and orders current. Contacts unify by email and phone — see unification.

The events it brings in

The real value of the store connection is its events: each order and checkout moment Instasent receives becomes something you can segment on or trigger an automation from — a paid order to thank a buyer, a shipped order to keep them posted, an in-progress checkout to nudge. The connector covers order events (created, updated, paid, shipped) and checkout events (started, updated).

The store events Instasent receives from Magento — the order and checkout moments you can build segments and automations on to recover sales and react to purchase behaviour.

Field mapping

Magento customer fields map to the matching Instasent attributes (email to _email, phone to _phone_mobile, name fields to theirs), and order data arrives as ecommerce events. Confirm the mapping on setup; see field mapping.

Consent mapping

Map Magento's marketing status to Instasent's marketing-preference attribute (_accepts_marketing_*) following the consent golden rule:

Magento statusInstasent valueMeaning
Opted intrueAccepted marketing
No status recordednullNo preference
Opted outfalseActively declined marketing

Only an active opt-out becomes false. A customer with no recorded marketing status maps to no preference (null), never to false. See Consent.

Last updated October 8, 2026

PreviousPrestaShopNextHighLevel
  • How to connect
  • What it syncs
  • The events it brings in
  • Field mapping
  • Consent mapping

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational