4Set Up and Administer Oracle Engagement Cloud Powered by Oracle DataFox

Integrate with Oracle Engagement Cloud

Integrate Oracle Engagement Cloud with Oracle DataFox to enrich your accounts, find and prioritize target companies, and source more opportunities.

Before You Start

Before you integrate Oracle Engagement Cloud with Oracle DataFox, complete these steps:

  • Contact Oracle Support to match all your Oracle Engagement Cloud accounts with the corresponding companies in Oracle DataFox. This action ensures you match each account with the right company.

  • Create a user account in Oracle Engagement Cloud with the sales administrator job role. This task is optional, but Oracle recommends that you create this user before you begin.

Connect to Oracle Engagement Cloud

  1. Sign in to Oracle DataFox.

  2. Click your user name, and then click Settings.

  3. Click Oracle Engagement Cloud under Integrations.

  4. Enter the URL instance and credentials for the sales admin account you just created.

  5. Click Next.

  6. On the Set Field Mappings page, map the Oracle DataFox fields to the corresponding Oracle Engagement Cloud fields. Mapping ensures you control the data that you want to enrich in your Oracle Engagement Cloud accounts.

    Field Mapping

    While you’re mapping your fields, note these important points:

    • Click the Refresh icon next to Oracle Engagement Cloud field to get the most updated list of Oracle Engagement Cloud fields.

    • If you don’t find a corresponding field mapping, create a new Oracle Engagement Cloud custom field and map it to the Oracle DataFox field. See Adding Objects and Fields in Application Composer for information on how to create new fields.

      Note: If you’re creating a custom field, make sure you use the same name as the corresponding Oracle DataFox field. This approach ensures consistency in field names.
    • The Overwrite Existing Data field is selected by default. When you save the field mappings, all the selected Oracle Engagement Cloud fields are overwritten by Oracle DataFox fields.

    For a list of field mappings, see Field Mappings.

  7. Click Done.

  8. You’re almost done. Contact Oracle Support to complete the rest of the setup.

Congratulations! Now you’re ready to do more with your Oracle DataFox account.

Field Mappings

Here's the full list of standard Oracle DataFox fields available for mapping.

Note: Fields unavailable in Oracle Engagement Cloud fields are marked as NA. For these fields, create a custom field and map it to the Oracle DataFox field.

See Adding Objects and Fields in Application Composer for information on how to create new fields.

Oracle DataFox Field Oracle Engagement Cloud Field Description
Registry ID Registry ID System-generated ID that uniquely identifies the record in Oracle Engagement Cloud. These fields are mapped automatically.
DataFox ID NA

It is recommended you create a custom field named DataFoxID.

Oracle DataFox company ID sent by Oracle DataFox to Oracle Engagement Cloud.
Name OrganizationName Name of the company.
Legal Name Name The legal name of the company. Oracle DataFox doesn’t always have data for this attribute.
URL URL Company's website.
Street1 AddressLine1 The first part of the street address.
Street2 AddressLine2 The second part of the street address.
City City The city where the company operates from.
State State The state where the company operates from.
Country Country The country where the company operates from.
Zipcode PostalCode The postal code of the company’s address.
Description NA A short description of the company.
Number of Employees EmployeesTotal An estimate of total employees in the company.
Revenue Estimate

CurrentFiscalYearPotentialRevenueAmount

PreferredFunctionalCurrency

An estimate of the company’s annual revenue.
Stock Ticker StockSymbol The company’s stock symbol.
Keywords NA An array of the company’s top keywords.
Industry Category NA The industry category of the company.
Industry Code NA The industry category code of the company.
NAICS Category NA The NAICS (North American Industry Classification System) category to help fine-tune prospect searching.
NAICS Code NA The NAICS (North American Industry Classification System) code.
DataFox URL NA The URL of enriched company displayed in Oracle DataFox.
Linkedin URL NA The company’s LinkedIn ID number.
Crunchbase URL NA The company’s Crunchbase slug.
Twitter Profile URL NA The company’s Twitter handle.
Account Score NA The numeric value indicating score for an account, enabling you to prioritize your accounts.
Account Scoring Tier NA The numeric value that tiers accounts into groups. A tier is an admin-defined grouping of scores. The admin can set threshold for Tier 1, 2, etc. so that all of sales and marketing have a shared understanding of account priority.
EIN TaxpayerIdentificationNumber The unique identifier for IRS (US only).
CIK NA The unique identifier for SEC (US only).
UK Companies House Registration ID NA The unique identifier for Companies House (United Kingdom's registrar of companies).
Last Synced Date LastEnrichmentDate The most recent date when the accounts were last enriched or synced.
Enrichment Status DataCloudStatus The status of data sync.

Bulk Sync Accounts

You can update thousands of accounts each day in Oracle Engagement Cloud with the latest company data from Oracle DataFox. By default, up to 10,000 accounts are updated each day, but you can adjust the account limit and frequency. You can set up the sync account limit and frequency using bulk syncs.

To set the bulk-sync frequency for your accounts, navigate to Settings > Integrations > Oracle Engagement Cloud > Bulk Syncs.

Bulk Sync Frequency

It’s recommended you set the frequency based on the number of accounts in your Oracle Engagement Cloud to ensure all the accounts are synced on a regular basis.

For example, let’s say you have 60,000 Oracle Engagement Cloud accounts and you set the bulk sync frequency to sync 10,000 accounts each day. This means that all your accounts are synced at least once a week.

You could also set the frequency to 5000 accounts per day to sync data only once in two weeks.