Skip to content
Marketing ⇄ Accounting and finance

Iterable to Logisense integration — real-time, two-way sync

Keep Iterable and Logisense in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Iterable and Logisense

Put revenue reality behind every campaign: Logisense and Iterable share the same customers, contacts, and billing status in real time, in both directions.

Logisense records the money — who pays, how much, and whether they are current; Iterable decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.

Stacksync syncs Account Service, Usage, Invoice, Payment in Logisense with Users, Events, Campaigns, Templates in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Act on Payment Status Updated webhooks to update entitlements or dunning status in an operational database in near real time.
  • 02 Write new signups from a product database into LogiSense as Accounts with the correct Package and Account Services.
  • 03 Track product and revenue Events (custom events, trackPurchase, updateCart) into Iterable from an app or database so journeys trigger on live behavior.
  • 04 Export Iterable engagement data (emailSend, emailOpen, emailClick, emailBounce, purchase) into a warehouse for deliverability and campaign reporting.

Common sync patterns

Where Logisense tracks lifecycle state: keep Iterable current

Trial, renewal, churn, or payment state from Logisense updates the contact in Iterable, so lifecycle campaigns and audience suppression run on current billing reality.

Consent and contact details stay aligned

Email, phone, address, and opt-out flags kept in either system stay consistent in the other, so every send and record honors the latest preferences.

Revenue and billing signals reach the audience

Plan tier, spend, or payment status from Logisense lands on the matching record in Iterable, so segments and targeting reflect who actually pays and how much.

What you can sync between Iterable and Logisense

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Iterable objects Logisense objects How this pairing syncs
Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Payment Payment records whose status changes emit webhooks; read for cash reconciliation and to drive dunning and provisioning workflows. Lists is specific to Iterable and Payment to Logisense — each maps to any object or custom field on the other side.
Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Extension Attribute Custom fields on entities via Extension/Attribute/Entity; discoverable so field mappings extend to org-specific data. Catalogs is specific to Iterable and Extension Attribute to Logisense — each maps to any object or custom field on the other side.
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Account Customer or partner records holding billing settings; hierarchical parent-child, synced two-way with CRM and warehouse customer tables. Commerce / Purchases is specific to Iterable and Account to Logisense — each maps to any object or custom field on the other side.
Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Contact People attached to an Account (billing, technical); synced two-way with CRM contacts and warehouse person records. Export data is specific to Iterable and Contact to Logisense — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Package and Service Product catalog of offerings and their chargeable services (one-time, recurring, usage-based); read for reporting or written from a catalog source. Users is specific to Iterable and Package and Service to Logisense — each maps to any object or custom field on the other side.
Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. Account Service Billable line item of a Package assigned to an account; written when provisioning or changing a subscription, read for entitlement checks. Events is specific to Iterable and Account Service to Logisense — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Logisense

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Iterable Logisense Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is written to Logisense through its API, with automatic retries and rate-limit backoff.

Logisense Iterable Sub-second propagation

DetectionLogisense notifies Stacksync of record changes through webhook events. Webhook event subscriptions push near-real-time notifications on record status changes (e.g.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
  • Logisense: No publicly documented fixed request cap; JWT access tokens are short-lived, and high-volume usage is ingested through mediation feeds rather than per-record API writes.
What ships with Iterable ⇄ Logisense

Connect Iterable and Logisense for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Logisense connection.

Real-time

Two-way sync

Changes in Iterable or Logisense instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Logisense data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Iterable or Logisense record.

Observability

Monitoring

Track your Iterable ⇄ Logisense sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Logisense.

How the Iterable and Logisense connectors work

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

Logisense

Integration surface
REST API (versioned, e.g. v9/v10)
Authentication
JSON Web Token (JWT) bearer tokens obtained via the API and refreshed before expiry
Change detection
Webhook event subscriptions push near-real-time notifications on record status changes (e.g. Payment Status Updated), with a Webhook Monitor for retries; entities without webhook coverage are polled via filtered REST queries
Capabilities
read · write · webhooks
Rate limits
No publicly documented fixed request cap; JWT access tokens are short-lived, and high-volume usage is ingested through mediation feeds rather than per-record API writes.
Logisense setup guide
How it works

How to connect Iterable to Logisense — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Iterable and Logisense with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Iterable connected
    Logisense connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Logisense objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Iterable ⇄ Logisense
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Iterable Logisense
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Logisense integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 359 integrations available for Iterable and Logisense.

Popular · 8 of 359
All Iterable integrations All Logisense integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own