Eloqua + Microsoft Dynamics 365
Connect Eloqua and Microsoft Dynamics 365 to Unify Marketing and Sales
Automate lead handoffs, sync campaign data, and close the loop between marketing automation and your CRM — no manual effort required.
Why integrate Eloqua and Microsoft Dynamics 365?
Eloqua and Microsoft Dynamics 365 are two of the most capable platforms in the enterprise tech stack, but when they operate in silos, marketing and sales teams lose critical context at every stage of the funnel. Integrating Eloqua with Dynamics 365 keeps lead intelligence, campaign engagement, and contact records synchronized in real time, giving every team member a complete picture of the customer journey. With tray.ai, you can build automated workflows that bridge these platforms and eliminate the friction that slows revenue teams down.
Automate & integrate Eloqua & Microsoft Dynamics 365
Use case
Automated Lead Handoff from Eloqua to Dynamics 365
When a prospect reaches a qualifying score threshold in Eloqua, tray.ai automatically creates or updates a Lead record in Microsoft Dynamics 365 and assigns it to the right sales rep based on territory or round-robin rules. No hot lead goes unnoticed, and sales teams can act within minutes of qualification. The lead record arrives enriched with Eloqua campaign history, score breakdown, and engagement activity.
Use case
Bi-Directional Contact and Account Sync
Keep contact and account records consistent across Eloqua and Dynamics 365 by automatically syncing field-level changes in both directions. When a sales rep updates a contact's phone number, job title, or account in Dynamics 365, that change propagates to Eloqua right away, so marketing campaigns always target accurate personas. New contacts captured through Eloqua forms are automatically provisioned in Dynamics 365 as well.
Use case
Campaign Response and Engagement Sync to Dynamics 365
Automatically write Eloqua campaign activity — email opens, clicks, form submissions, and webinar registrations — back to corresponding contact and lead records in Dynamics 365. Sales reps can see exactly which emails a prospect engaged with and which campaigns influenced their decision-making, so outreach can be a lot more personal. This data also feeds Dynamics 365 dashboards for comprehensive marketing attribution reporting.
Use case
Closed-Loop Opportunity and Revenue Reporting
When an Opportunity in Dynamics 365 moves to Closed Won, tray.ai sends the deal data back to Eloqua to associate revenue with the originating campaigns and programs. This closed-loop feedback lets marketing leaders calculate true campaign ROI and make smarter spend decisions. It also lets Eloqua automatically suppress recently closed customers from prospecting campaigns.
Use case
Dynamic Segment and List Management
Use Dynamics 365 CRM data — industry, company size, lifecycle stage, or opportunity value — to dynamically build and update Eloqua segments and shared lists. When a contact's stage changes in Dynamics 365, tray.ai updates their Eloqua segment membership in real time so they receive the most relevant nurture content. This replaces error-prone manual list imports with always-current, logic-driven segmentation.
Use case
Event and Webinar Registration Sync
When a contact registers for a webinar or event through an Eloqua landing page, their registration is automatically logged as an activity on their Dynamics 365 contact or lead record. After the event, attendance status and follow-up campaign enrollment are written back to Dynamics 365, giving sales reps timely triggers for personalized outreach. The whole data flow happens without any post-event reconciliation work.
Use case
Lead Recycling and Re-Engagement Workflows
When a lead in Dynamics 365 is marked as disqualified, lost, or not ready by a sales rep, tray.ai triggers an automatic re-engagement nurture program in Eloqua tailored to that contact's persona and previous engagement history. Marketing can keep warming these leads until they meet qualification criteria again, with no manual handback required.
Get started with Eloqua & Microsoft Dynamics 365 integration today
Eloqua & Microsoft Dynamics 365 Challenges
What challenges are there when working with Eloqua & Microsoft Dynamics 365 and how will using Tray.ai help?
Challenge
Handling Duplicate Records Across Both Platforms
Eloqua and Dynamics 365 each manage contact and lead records independently, making it easy for duplicates to pile up when new records are created in one system without checking the other. The result is split engagement histories, inconsistent data, and leads being worked by multiple reps at once.
How Tray.ai Can Help:
tray.ai workflows include configurable deduplication logic that checks for existing records by email address or other unique identifiers before creating new ones. When a potential duplicate is detected, the workflow merges data intelligently or routes the record for human review rather than blindly creating another entry.
Challenge
Managing Field Mapping Complexity Between Platforms
Eloqua and Dynamics 365 use different field names, data types, and picklist values for similar data points such as lead status, industry, and lifecycle stage. Mapping these fields incorrectly can cause data loss, failed syncs, or records that end up in the wrong segments and queues.
How Tray.ai Can Help:
tray.ai's visual data mapper lets teams configure precise field-level mappings between Eloqua and Dynamics 365, including value transformation rules that convert picklist options and normalize data formats. These mappings can be updated without touching code, making it straightforward to accommodate schema changes on either platform.
Challenge
Avoiding Infinite Update Loops in Bi-Directional Syncs
When both Eloqua and Dynamics 365 are configured to push updates to each other, a change in one system can trigger an update in the other, which then triggers another update back — flooding both platforms with redundant API calls and erroneous data changes.
How Tray.ai Can Help:
tray.ai workflows include built-in loop prevention mechanisms, such as timestamp comparison and sync-source flags, that ensure each record update is only propagated once. When a change is detected, the workflow verifies that it didn't originate from the integration itself before triggering an outbound sync.
Challenge
Scaling Integrations Across High-Volume Lead Pipelines
Enterprise marketing teams using Eloqua can generate thousands of new leads and campaign responses per day. That puts real pressure on integrations to process high-volume event streams reliably without delays, data loss, or rate-limit errors from the Dynamics 365 API.
How Tray.ai Can Help:
tray.ai is built on a scalable, cloud-native architecture that handles high-throughput event processing with automatic queuing and retry logic. Dynamics 365 API rate limits are managed transparently within the platform, so large lead batches are processed completely and in order without manual intervention.
Challenge
Keeping Campaign Attribution Intact Through the Sales Cycle
As leads move through the Dynamics 365 pipeline over weeks or months, the original Eloqua campaign source data can become dissociated from the record — especially when leads are converted, merged, or reassigned. When that happens, it's hard to accurately attribute closed revenue back to the campaigns that generated it.
How Tray.ai Can Help:
tray.ai workflows are designed to preserve and carry campaign attribution data at each stage of the lead-to-opportunity journey. When records are converted or updated in Dynamics 365, the workflow checks for and retains the original campaign source fields from Eloqua, so attribution data survives the full sales cycle and is available for closed-loop reporting.
Start using our pre-built Eloqua & Microsoft Dynamics 365 templates today
Start from scratch or use one of our pre-built Eloqua & Microsoft Dynamics 365 templates to quickly solve your most common use cases.
Eloqua & Microsoft Dynamics 365 Templates
Find pre-built Eloqua & Microsoft Dynamics 365 solutions for common use cases
Template
Eloqua Lead Score Threshold to Dynamics 365 Lead Creation
Automatically create or update a Lead record in Microsoft Dynamics 365 whenever a contact in Eloqua reaches a defined lead score threshold, assigning the lead to the correct owner and populating all relevant fields including campaign source, score, and recent activity.
Steps:
- Monitor Eloqua for contacts that cross the configured lead score threshold
- Check Dynamics 365 to determine if a Lead or Contact record already exists for the email address
- Create a new Lead record or update the existing one in Dynamics 365 with enriched Eloqua data and assign to the appropriate sales owner
Connectors Used: Eloqua, Microsoft Dynamics 365
Template
Dynamics 365 New Contact to Eloqua Contact Sync
When a new Contact or Lead is created in Microsoft Dynamics 365 by a sales rep or through an integration, tray.ai automatically provisions a matching contact record in Eloqua and adds them to the appropriate nurture segment based on their lifecycle stage or industry.
Steps:
- Detect the creation of a new Lead or Contact record in Dynamics 365 via webhook or scheduled poll
- Map Dynamics 365 field values to corresponding Eloqua contact fields including custom fields
- Create the contact in Eloqua and enroll them in the appropriate segment or nurture campaign
Connectors Used: Microsoft Dynamics 365, Eloqua
Template
Eloqua Form Submission to Dynamics 365 Activity Log
Every time a contact submits a form in Eloqua — whether a gated content download, contact request, or event registration — tray.ai logs a timestamped Activity record on the corresponding Dynamics 365 contact or lead record, so sales has full visibility into inbound engagement.
Steps:
- Capture Eloqua form submission events including form name, contact email, and submission timestamp
- Look up the corresponding Lead or Contact record in Dynamics 365 by email address
- Create a new Activity or Task record in Dynamics 365 with form submission details and relevant campaign context
Connectors Used: Eloqua, Microsoft Dynamics 365
Template
Dynamics 365 Closed Won Opportunity to Eloqua Campaign Attribution
When an Opportunity is moved to Closed Won status in Dynamics 365, tray.ai sends the deal value and associated contact information back to Eloqua, linking the revenue to the originating campaign and removing the customer from active prospecting lists.
Steps:
- Trigger on Opportunity stage change to Closed Won in Dynamics 365
- Retrieve associated contact and campaign source data from the Opportunity record
- Update the Eloqua contact record with opportunity value and outcome, enroll in a customer onboarding program, and remove from prospecting segments
Connectors Used: Microsoft Dynamics 365, Eloqua
Template
Bi-Directional Contact Field Update Sync
Keep contact records consistent between Eloqua and Dynamics 365 in real time by detecting field-level changes in either system and pushing updates to the other, using conflict resolution logic to preserve data integrity and avoid overwrite loops.
Steps:
- Detect field-level contact updates in Eloqua or Dynamics 365 using timestamps or change event webhooks
- Apply conflict resolution logic to determine which system holds the most recent authoritative value
- Write the winning field values to the opposing system and log the sync event for audit purposes
Connectors Used: Eloqua, Microsoft Dynamics 365
Template
Dynamics 365 Disqualified Lead to Eloqua Re-Engagement Enrollment
When a sales rep marks a Lead as Disqualified or Lost in Dynamics 365, tray.ai evaluates the reason code and automatically enrolls the contact into the right Eloqua re-engagement or long-term nurture program, so the lead isn't simply abandoned.
Steps:
- Trigger on Lead status change to Disqualified or Lost in Dynamics 365 and capture the disqualification reason
- Look up the matching Eloqua contact and evaluate persona attributes to select the correct nurture program
- Enroll the contact in the chosen Eloqua campaign and update a custom field to reflect their re-engagement status in Dynamics 365
Connectors Used: Microsoft Dynamics 365, Eloqua