Preliminary setup for closed-loop reporting
Before implementing closed-loop reporting with Salesforce, you must perform the following in Oracle Eloqua:
Creating campaign fields
Custom campaign fields allow you to mimic the campaign structure in your Salesforce system. When a campaign is created in Oracle Eloqua, the custom campaign fields are synchronized to Salesforce. Similarly, changes to the campaign fields in Salesforce are synchronized into Oracle Eloqua.
The following table lists the default campaign fields for Oracle Eloqua campaigns and their data types. An asterisk (*) denotes required fields in Oracle Eloqua.
| Default campaign fields | Data type |
|---|---|
| Campaign Name* | Text |
| Start Date* | Date |
| End Date* | Date |
| SFDC Campaign ID | Text |
| Budgeted Cost | Currency |
| Actual Cost | Currency |
| Region | Picklist |
| Product | Picklist |
| Campaign Type | Picklist |
Creating external assets and activities
External activities are those activities that are not tracked by Oracle Eloqua. For example, trade show attendance is not tracked by Oracle Eloqua, while an email open is. External activities help give your organization a full view of all marketing activities within Oracle Eloqua.
For your Salesforce integration, take some time to identify the external activities you want to leverage as part of closed-loop reporting. External activities can be attributed to Oracle Eloqua campaigns and shared with sales.
List the activities that you want to track using a table like the one below.
| External asset type | External activity type |
|---|---|
| Trade show | Visited booth |
| Viewed a demo | |
| Webinar | Registered |
| Attended | |
| Registered - did not attend |