Marketing automation and web analytics
Personalizes dynamic cross-channel marketing campaigns so you can filter and target audiences based on location, behavior, or interest
Supports drag-and-drop dashboard so marketers can explore user flow and segmentation
Scores leads so marketers can identify which segments to target or which will likely make a purchasing decision soon, and notifies of lead score changes
Identifies campaign engagement, web activity, email opens, form submits, and social activity and focuses on channels that generate high interest, engagement, and conversion
Provides web analytics tool so marketers can see detailed information about audience like location, interests, gender, page view, and page time
How Eloqua works
Eloqua is Oracle’s B2B Cross-Channel Marketing solution, and it operates by tracking the identities and event actions of users that interact with your properties.
Eloqua can only automatically track identifying information of users that submit via an Eloqua form that you configure on your site. If you want to identify users who don’t interact with an Eloqua form, you will need to use Eloqua’s REST API to code and relay the relevant information.
To track user actions, Eloqua packages properties that you specify into data objects that are then attached to user records. The events and properties you would like to track need to be configured manually in your code, according to various specifications in Oracle’s documentation.
Get more out of Eloqua with Segment
To make user identification easier, Segment integrates with Eloqua’s REST API to provide the ability to create or update contacts in Eloqua following events that do not use an Eloqua form. This means you can identify your users simply using Segment’s `identify` call, rather than the Eloqua API.
For `track` events, all you need to do is provide Segment with a mapping in your integration settings specifying the Segment event names with the corresponding Custom Object you would like to associate them with in Eloqua. The Segment integration does a case and formatting insensitive match, so that if you have a field called `Account Type` in Eloqua and a property called `accountType` in your Segment event, the mapping will get handled properly.