PrestaShop
Connect a PrestaShop store as a data source: the webservice key it needs, the customers and orders it syncs, how its fields map to Instasent attributes, and how to map its marketing status to consent.
PrestaShop is the native connector for PrestaShop stores. Once connected, it syncs your store's customers and orders into Instasent so your audience and purchase events stay current.
How to connect
PrestaShop connects with an API key: you create a webservice key in your store first and paste it into Instasent, along with your store domain.
Create a webservice key in PrestaShop
In your PrestaShop admin, go to Advanced Parameters → Webservice → Add a new webservice key and grant it all VIEW (read) permissions. PrestaShop generates the key you'll use in Instasent.
Add the data source
In Data sources, select Add data source and choose PrestaShop from the Integrations section.
Enter your credentials and connect
On the Connect step, fill in the Connection name, your Shop domain, and the webservice key, 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 PrestaShop 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 new order to follow up on, an in-progress checkout to nudge. The connector brings in order events (created, updated) and checkout events (started, updated).
Field mapping
PrestaShop 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 PrestaShop's marketing status to Instasent's marketing-preference attribute
(_accepts_marketing_*) following the consent golden rule:
| PrestaShop 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.