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.
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.
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 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.
Add the data source
In Data sources, select Add data source and choose Magento from the Integrations section.
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.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.
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).
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 status | Instasent value | Meaning |
|---|---|---|
| Opted in | true | Accepted marketing |
| No status recorded | null | No preference |
| Opted out | false | Actively 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.