Can BigCommerce and Eloqua sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the BigCommerce and Eloqua initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the BigCommerce account, edition, environment, and business objects the integration must access. Identify the Eloqua account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the BigCommerce to Eloqua sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map BigCommerce fields to Eloqua?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a BigCommerce and Eloqua integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the BigCommerce and Eloqua pilot start with?

Start by reviewing Customers in BigCommerce and Accounts in Eloqua. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

E-commerce / Marketing

BigCommerce and Eloqua integration

Plan how BigCommerce and Eloqua should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

BigCommerce

Eloqua

Review the integration scope

Teams building with Stacksync

Plan the connection your business needs

Explore a BigCommerce and Eloqua integration with a Stacksync engineer. Stacksync support for BigCommerce and Eloqua is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

01 / Business process

Start with one meaningful update

Identify the record that changes in BigCommerce or Eloqua, where it needs to appear, and which team depends on it.

02 / Data access

Establish the available connection

Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.

03 / Success criteria

Define a result you can verify

Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.

Explore the technical references

Technical referenceAvailable documentation, candidate record relationships, and questions for your technical review.

What records can you sync?

Explore the record types and read/write requirements for each system.

BigCommerceConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Products	Confirm support for this record type and the direction you need.
Variants and SKUs	Confirm support for this record type and the direction you need.
Orders	Confirm support for this record type and the direction you need.
Customers	Confirm support for this record type and the direction you need.
Categories	Confirm support for this record type and the direction you need.
Brands	Confirm support for this record type and the direction you need.

Discuss BigCommerce requirements

EloquaConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Contacts	Confirm support for this record type and the direction you need.
Accounts	Confirm support for this record type and the direction you need.
Custom Data Objects	Confirm support for this record type and the direction you need.
Activities	Confirm support for this record type and the direction you need.
Campaigns	Confirm support for this record type and the direction you need.
Emails	Confirm support for this record type and the direction you need.

Discuss Eloqua requirements

Connection requirements and limits

BigCommerce

Integration interface: REST Management API (V2 and V3), plus GraphQL Storefront and Admin APIs
Authentication: Confirm the credentials, API plan, and permissions required for BigCommerce.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for BigCommerce and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Technical documentation

BigCommerce vendor API documentation

Eloqua

Integration interface: Bulk API 2.0 (contacts, accounts, custom data objects, activities) plus Application REST API (campaigns, emails, forms, lists)
Authentication: Confirm the credentials, API plan, and permissions required for Eloqua.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Eloqua and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare your technical review

Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.

Implementation reference

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet

CSV · No email required · Record matching, ownership, and test cases

Customer identityCustomers Accounts

Before linking BigCommerce Customers to Eloqua Accounts, check whether the customer is an individual or a company. Match the correct record type in each system.

BigCommerce: Object support to establish
Eloqua: Object support to establish

Record identity

Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.

Field ownership

Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

References: BigCommerce: Customers documentation

Customer identityCustomers Contacts

Before linking BigCommerce Customers to Eloqua Contacts, check whether the customer is an individual or a company. Match the correct record type in each system.

BigCommerce: Object support to establish
Eloqua: Object support to establish

Record identity

Field ownership

Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

References: BigCommerce: Customers documentation

Architecture decision

Choose how to connect your systems

Choose a method around one example record and the update your business needs. Use Customers / Accounts to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your BigCommerce and Eloqua record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Customers / Accounts, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when BigCommerce and Eloqua need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time BigCommerce / Eloqua migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow reference

From a business event to the right update

Open a workflow to see its trigger, record relationships, and expected result.

Customer sync test

Starting event: A change to the selected Customers or Accounts record needs a defined result in the other system.

Start with BigCommerce Customers and Eloqua Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer sync test

Starting event: A change to the selected Customers or Contacts record needs a defined result in the other system.

Start with BigCommerce Customers and Eloqua Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Coordinate BigCommerce commerce data with Eloqua

Starting event: A catalog, order, or fulfillment change in BigCommerce matters to Contacts or Accounts.

Choose the commerce entity from Products or Variants and SKUs; separate products, variants, orders, and fulfillments.
Preserve order and line references through the Eloqua process. Define many-to-one or one-to-many relationships explicitly.
Assign separate ownership for commercial approval, inventory, and fulfillment, including partial cancellations or returns.

Expected result: A split fulfillment and repeated request preserve line quantities without duplicate orders or shipments.

If it fails: Look up existing downstream records before retrying creation; reconcile current order and fulfillment states.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect BigCommerce Customers and Eloqua Accounts, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer change

Investigate

Inspect BigCommerce Customers and Eloqua Contacts, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

A record type or update is unavailable

Investigate

Check the BigCommerce and Eloqua connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

How updates move between BigCommerce and Eloqua

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

BigCommerce Eloqua Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Eloqua.

Eloqua BigCommerce Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in BigCommerce.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare BigCommerce and Eloqua access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

BigCommerce setup checklist

Identify the BigCommerce account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for BigCommerce, including read/write support, authentication, and initial-load limits.

Eloqua setup checklist

Identify the Eloqua account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Eloqua, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the BigCommerce and Eloqua planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Security and control for your integrations

Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.

Explore security controls

FAQ