The External Data Intelligence application allows marketers to build a segment for the purposes of adding contacts to a canvas. As an example, the app can be used to feed contacts into an Oracle Eloqua campaign based on a segment definition against a Salesforce instance for a batch and blast campaign or for an always on nurture stream. The segment can connect to any external system configured by the administrator in the configuration section of the application. The user interface to build the segment looks similar to the segment builder inside of Oracle Eloqua to allow for a simple and seamless end user experience.
Drag the “External Data Intelligence” on to the canvas from the left frame.
External Segments are groups of contacts that are grouped together based on criteria you specify. A segment defined in the External Data Intelligence app is dynamic based on implicit or explicit information about the contact residing in an external system (e.g. Salesforce). After you create a segment it can be used to drop Contacts into a Campaign or a Program.
4. In the left pane click Add . Then click on the following options.
NOTE: Users will need advanced knowledge in writing SOQL queries. For more information on how to use Saelsforce.com Query language refer to:
https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_sosl_intro.htm
5. Choose to build your filter criteria condition using fields from the base table or from tables related to the base external object selected.
6.Name the segment providing a unique name and click Save once the filter criteria is defined.
After you save the segment, the External Data Intelligence app calculates the number of contacts in the segment once activated. You can click Refresh to see the latest totals.
Tip: The more criteria you add, the longer it can take to refresh the segment totals. Each criterion must be evaluated against the entire contact database. So, the fewer criteria, the faster the segment totals can be returned.
7. Customise Field Mapping (add/delete) for the segment or let the default Field Mapping apply to Import file. You can change the Unique Identifier or Update Rule using the dropdown provided.
8. Filter Criteria or SOQL Criteria can be switched to exclude/include. This will exclude/include the contacts from that criteria to be imported into Eloqua. Click Save once you have completed building the segment.
9.Once the Feeder Segment is built, you can get the overall query using the ‘View Query’ feature. Clicking on ‘Copy Query’ button copies the query where you can paste it on the Salesforce Workbench to check the query results.
You can use fields from the base object selected in your filter criteria to dynamically build your segment. For example, you can build a segment querying the Leads object where the Status is equal to ‘Qualified’.
3. Double-click the criteria you added to configure it. Click outside the window to close it.
4. Add additional filters as needed. When you add filter criteria, you join the filters using a Boolean AND or OR comparison. To switch between AND or OR, click the operator label on the canvas.
5. To group the filters, click on the filter that you want to group and press Ctrl key and the filter that you want to add to the group. They get highlighted. Click on Group.
6. Click Save
Adding Filter Criteria from Related External Object Fields
You can use fields from objects that are related to the base object selected in your filter criteria to dynamically build your segment. For example, you can build a segment querying the Leads objects where a Lead is associated to an Opportunity associated to an Account where Account Type = ‘Prospect’.
3.Double-click the criteria you added to configure it. Click outside the window to close it.
4. Navigate the tree view control to locate the field in the right object using the right relationship connectors.
5. You can group the criterias using Group feature. This is as explained in the previous section.
6. Click Save.
You can use the ‘Since Last Sync’ in conjunction with other filter conditions that will bring only delta contacts after the first sync whenever the frequency is set to run more than once.
If ‘Since Last Sync’ feature is not added to the Filter/SOQL Criteria then the segment pops up an alert to the user suggesting to use the feature.
You can use the advanced SOQL feature to create complex filter conditions that are not possible through the graphical user interface provided.
3. Insert the WHERE clause component of the SOQL statement in the text box provided.
4. Click Validate SOQL. If a valid SOQL statement was inputted, then the following message will be displayed.
After you create a segment it can be re-used to create a new Segment.
Screenshot shows a Segment
After applying Exclusion Criteria to an existing Segment, it appears as shown in the below screenshot:
When Exclusion Criteria is applied to a New Segment, it appears as shown below:
User can continue to build the New Segment with different criteria and click on Save. Exclusion Criteria will exclude the Contacts to be imported into Eloqua.
The External Data Intelligence app supports the use of the application in either a “batch and blast” campaign or an “always on” campaign (such as a nurture stream).
NOTE: If a process from the previous interval run is still executing then the current interval process will be skipped.
When we reactivate a campaign, the ‘Run Once’ feeder service used to automatically import the contact details into the campaign; this feature is now disabled.
If we want the contact details to be imported again, we now need to follow these steps:
2.Under the Actions tab click on Re-import Data.
NOTE: It used to be, that we had to deactivate the campaign to import contacts, but now we can import even when the campaign is active.
*There is one exception on the old active campaigns (campaigns which were active before this feature is made available) : Old campaigns will bring the contacts once again if they are reactivated; and after this import, any future campaign reactivations will no longer facilitate automatic import of contacts unless Re-importDataoption is chosen by the user.
*If the Re-import Data option is chosen when the campaign is deactivated, then it will be effective immediately after the campaign reactivation.
‘Re-import data’ feature release dates :
Duplicate contact rule is a helpful feature when users have multiple contacts in salesforce with matching query criteria and the same email address. Eloqua does not allow to import contacts with the same email address.
The Duplicate Contact Rule can be overwritten on EDI Feeder step
There are Four Duplicate Contact Rule
If the user has multiple contacts in Salesforce with matching query criteria and same email address, and the duplicate contact rule selected in EDI Admin or Feeder Level it will import contacts based on the selected Duplicate Contact Rule.
Search contact is a helpful feature when it comes to finding a contact in a larger volume. Users can view 100 contacts from salesforce in the feeder service for configured salesforce query, now we have added the search facility, where users can enter the email address and verify that this contact belongs to configured Salesforce query or not.
The Search Contact feature can be used in the following manner:
4. After the view contact popup is opened, the user has to enter an email that the user wants to search.
5.This search will return all records from salesforce based on configured salesforce query.
The following feature allows user to choose an Eloqua picklist to query the snowflake data. This will bring all the contacts from snowflake whose configured field value is in the selected Eloqua picklist. We are allowing the ‘in Eloqua picklist’ capability to Text and Number data types.
Below are the easy steps to configure this feature in your Feeder/Decision app. There is no Admin configuration needed, user can configure it directly on the Feeder/Decision app.
This selection will bring all the contacts from snowflake whose configured field value in the Eloqua picklist selected.
Snowflake has limitation of 16K values inside the ‘IN’ query. Hence the maximum number of picklist values allowed on the Eloqua picklist is less than 16k. For the picklists having option values beyond this limit will throw an error.
When creating a feeder or a decision service in EDI, there are times when we want to add a criterion that says: include only if the contacts are found in a certain Eloqua segment. EDI is now capable of doing that.
We can also use this feature to narrow an already existing Eloqua segment with data from Snowflake.
Note: This premium feature is license-based – please contact sales@portqii.com to purchase it.
This feature needs a working-folder where the app can cache it’s memory. Deleting this folder can result in malfunction of this feature. An Eloqua admin needs to select such a folder from the app’s admin-configuration page. Here’s how to do that:
Click on the edit icon to view and search the existing folders in Eloqua.
Folders can be expanded to show the child folders by clicking on the + sign. Select the desired folder and save it.
After the campaign activation, EDI processes the contacts by creating a copy of the chosen segments and related picklists. All the segments which will be created as a part of contact processing in EDI will be created in the working-folder and will be cleaned up frequently (every 2 days).
If the working-folder is not selected, then EDI will create its own folder named ‘Portqii_Segment_Do_Not_Delete’ and use that as the working-folder.
4. Clicking on the added ‘Use Eloqua Segment’ option will open the filter to add the Eloqua segment. Double click the filter to open a search box.
5.Search for the Eloqua segment by typing the search text and select the desired segment from the list; and then save the Feeder/Decision service.
Note: The contact-count visible on the feeder after the save is the count resulting only from the snowflake query. The actual contact count will be shown once the process of combining the EDI filter criteria with Eloqua segment happens (after the campaign activation).
When creating a feeder or a decision service in EDI, there are times when we want to add a criterion that says: include only if the contacts are found in a certain Eloqua segment. EDI is now capable of doing that.
We can also use this feature to narrow an already existing Eloqua segment with data from Salesforce.
Note: This premium feature is license-based – please contact sales@portqii.com to purchase it.
This feature needs a working-folder where the app can cache its memory. Deleting this folder can result in malfunction of this feature. An Eloqua admin needs to select such a folder from the app’s admin-configuration page. Here’s how to do that:
After the campaign activation, EDI processes the contacts by creating a copy of the chosen segments and related picklists. All the segments which will be created as a part of contact processing in EDI will be created in the working-folder and will be cleaned up frequently (every 2 days).
If the working-folder is not selected, then EDI will create its own folder named ‘Portqii_Segment_Do_Not_Delete’ and use that as the working-folder.
4. Clicking on the added ‘Use Eloqua Segment’ option will open the filter to add the Eloqua segment. Double click the filter to open a search box.
5.Search for the Eloqua segment by typing the search text and select the desired segment from the list; and then save the Feeder/Decision service..
Note: The contact-count visible on the feeder after the save is the count resulting only from the salesforce query. The actual contact count will be shown once the process of combining the EDI filter criteria with Eloqua segment happens (after the campaign activation on Sync reports).
The Salesforcefeeder service/decision service that uses this feature (Eloqua segment as a filter criterion) usually takes time to process the records. For example: Importing one million records using a feeder service takes about three hours, so we need to factor this into our planning.
Email alerts on product updates, new product announcements, special promotions and more!
