Skip to content
Marketing ⇄ ERP

Eloqua to TikTok Shop integration — real-time, two-way sync

Keep Eloqua and TikTok Shop 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 Eloqua and TikTok Shop

Feed the real customer, order, and revenue records from TikTok Shop into Eloqua so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. TikTok Shop holds exactly that: Promotions, Shops, Products, SKUs that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Promotions, Shops, Products, SKUs in TikTok Shop with Emails, Forms and Form Submits, Contact Lists and Segments, Contacts in Eloqua in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Eloqua works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Eloqua flow back onto the record in TikTok Shop.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Write tracking numbers and fulfillment status back to TikTok Shop when orders ship
  • 02 Reconcile refunds and returns into accounting systems alongside other sales channels
  • 03 Add or remove Contacts from shared Contact Lists and Segments based on lifecycle stage computed downstream in a database.
  • 04 Two-way sync Contacts between Eloqua and a Postgres or warehouse table, matched on email, so ops teams query and update marketing profiles in SQL while marketers keep working in Eloqua.

Common sync patterns

Where Eloqua captures new people: signups become customer records

Registrations, form fills, or new subscribers in Eloqua create or update the corresponding record in TikTok Shop, so the back office sees them without anyone re-keying.

Consent and contact changes travel

Email, address, or subscription-status changes stay aligned across both systems, so a customer who updates their details or opts out is respected everywhere.

Purchase history drives segmentation

Orders, invoices, and revenue totals from TikTok Shop land on the matching contact or account in Eloqua, so audiences are built from what customers actually bought and spent rather than from guesses.

What you can sync between Eloqua and TikTok Shop

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.

Eloqua objects TikTok Shop objects How this pairing syncs
Accounts Company records linked to Contacts via the account-linkage field; moved through the Bulk API and typically mastered in a CRM or ERP and written into Eloqua. Shops The seller storefront; API access is authorized and scoped per shop. Accounts is specific to Eloqua and Shops to TikTok Shop — each maps to any object or custom field on the other side.
Custom Data Objects Auxiliary data tables (CDOs) linked to Contacts for records like event registrations or purchases; synced via the Bulk API so nurture campaigns can branch on them. Products Listings synced from a PIM or ERP catalog, subject to platform review. Custom Data Objects is specific to Eloqua and Products to TikTok Shop — each maps to any object or custom field on the other side.
Activities Engagement events (email opens, clicks, form submits, bounces, page views, subscribes/unsubscribes) exported through the Bulk API activities export; read-only feed for scoring and attribution. SKUs The purchasable variants under a product; inventory and price live at this level. Activities is specific to Eloqua and SKUs to TikTok Shop — each maps to any object or custom field on the other side.
Campaigns Multi-step campaign-canvas assets managed through the Application REST API; campaign membership and response data read out for attribution reporting. Orders Purchases pulled into an OMS or ERP for fulfillment and accounting. Campaigns is specific to Eloqua and Orders to TikTok Shop — each maps to any object or custom field on the other side.
Emails Email creative and email-group assets managed via the Application REST API; usually read for reporting rather than written by a sync. Fulfillment packages Shipment units where tracking numbers and carrier data are written back. Emails is specific to Eloqua and Fulfillment packages to TikTok Shop — each maps to any object or custom field on the other side.
Forms and Form Submits Form definitions and their submission data, accessed through the Application REST API; submissions read out into a warehouse for lead capture and analysis. Inventory Stock quantities per SKU, updated from the warehouse or ERP to prevent oversells. Forms and Form Submits is specific to Eloqua and Inventory to TikTok Shop — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and TikTok Shop

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.

Eloqua TikTok Shop Interval-based propagation

DetectionStacksync polls Eloqua for changes on an incremental schedule, reading only records changed since the previous pass. Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax.

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

TikTok Shop Eloqua Sub-second propagation

DetectionTikTok Shop notifies Stacksync of record changes through webhook events. Webhook push notifications for order and product status changes, with polling for reconciliation.

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

Rate-limit considerations

  • Eloqua: Per-instance soft limits by sync type (Export 2,000/hr, Import 2,000/hr, Sync Action 4,000/hr); 32 MB cap per POST to a staging area and 50,000 records per retrieve batch.
  • TikTok Shop: Subject to the platform's per-app API rate limits.
What ships with Eloqua ⇄ TikTok Shop

Connect Eloqua and TikTok Shop for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Eloqua–TikTok Shop connection.

Real-time

Two-way sync

Changes in Eloqua or TikTok Shop instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Eloqua or TikTok Shop 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 Eloqua or TikTok Shop record.

Observability

Monitoring

Track your Eloqua ⇄ TikTok Shop sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Eloqua and TikTok Shop.

How the Eloqua and TikTok Shop connectors work

Eloqua

Integration surface
Bulk API 2.0 (contacts, accounts, custom data objects, activities) plus Application REST API (campaigns, emails, forms, lists)
Authentication
OAuth 2.0 (Authorization Code or Resource Owner Password Credentials grant; Client Credentials not supported) or HTTP Basic Auth with siteName + username + password; the instance base URL must first be discovered via the login.eloqua.com/id endpoint
Change detection
Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax; no general-purpose record-change webhook
Capabilities
read · write
Rate limits
Per-instance soft limits by sync type (Export 2,000/hr, Import 2,000/hr, Sync Action 4,000/hr); 32 MB cap per POST to a staging area and 50,000 records per retrieve batch

TikTok Shop

Integration surface
REST API (TikTok Shop Open Platform)
Authentication
App key and secret with shop-scoped access tokens; requests carry a signature
Change detection
Webhook push notifications for order and product status changes, with polling for reconciliation
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's per-app API rate limits
How it works

How to connect Eloqua to TikTok Shop — 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 Eloqua and TikTok Shop 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
    Eloqua connected
    TikTok Shop connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Eloqua and TikTok Shop 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 · Eloqua ⇄ TikTok Shop
    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
    Eloqua TikTok Shop
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Eloqua and TikTok Shop 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 463 integrations available for Eloqua and TikTok Shop.

Popular · 7 of 463
All Eloqua integrations All TikTok Shop 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