Please note that this version of the Rev.Up ABX Eloqua Connector is being deprecated for a new connector. If you are onboarded after 2/1/2022, you will not have access to this connector. Customers currently using this connector can expect support until 6/30/2022.
More information about the new connector here.
Q1: If we have a contact that belongs to multiple (Atlas) segments, how can we avoid launching multiple emails across Eloqua campaigns to the same contact?
Lattice Eloqua app provides you an option to setup campaign priorities.
If you a contact (e.g. email@example.com) that is part of campaign1 and Campaign 2 in Eloqua and the Campaign priority is Campaign 1 and then Campaign 2, then the contact (firstname.lastname@example.org) will only enter Campaign 1 and not Campaign 2.
Note: If the same contact is part of Campaign 3, but not defined in the campaign priority, the contact will be sent to Campaign 3.
Q2: How does we identify if a contact was created or updated by Lattice?
There are probably many ways to do this
- If the contact is mapped to a lattice specific field such as Lattice score, the user can search for all contacts that have this field.
- In addition, Eloqua also provides functionality to search through all campaign activities. Customers should be able to create this report to get the data.
- Finally, the recommendation dashboard provides a high level summary of contacts and accounts created/updated for each campaign.
Q3: Is there a way to avoid the same contact going through the campaign flow multiple times?
We do not support incremental sync – meaning launching the same campaign multiple times does not only send new contacts and accounts to Eloqua, instead we send the full list. Here is a simple setup in Eloqua that can help address this issue
The default setting in Eloqua avoids sending the same contact through the campaign multiple times. This option can be turned-off explicitly though.
Q4: Is there a way to disable creating new contacts? If not, what are some of the guardrails against creating too many contacts?
No, there is currently no option to restrict / control the no of contacts created from Lattice.
Q5: Do we use any Eloqua API's that would trigger a quota limitation on our side?
There is currently no special configuration to restrict / control usage of Eloqua APIs.
Lattice Eloqua app use Bulk API from Eloqua to create / update contacts. Note each campaign in Eloqua uses the Eloqua bulk API to update contacts coming in from Lattice Campaign.
Q6. Can I run Eloqua LPI and Eloqua Atlas app together?
This is not recommended
But, Yes, you can run both of the apps in parallel, but which of these apps update the contact will not be deterministic.
Q7. What are some of the best practices of using the Eloqua App with Lattice?
Sync one Atlas Campaign with an Eloqua Campaign
While it is possible to use the Lattice Eloqua app to sync multiple atlas campaigns to the same Eloqua campaign, but we recommend one atlas campaign syncing with one Eloqua campaign.
Suggest creating atlas segments to represent audience journey stages. With this setup, you can setup Eloqua campaigns to pair with dedicated email campaigns in Eloqua.
Q8. I see contact & account attributes from Lattice in Eloqua. Is this configurable?
Yes, we automatically export a limited set of contacts and account attributes. However, you may want to include additional data (your data or 3rd party data) that's already in Atlas in Eloqua.
You can do so by enabling these attributes in Attributes
- Go to My Data -> Attribute Admin
- Select tab Enable & Disable Attributes
- Select tab Company Profile - Under Company Profile, you will see all the data categories. This includes your data as well additional 3rd party data providers through Lattice.
- Enable attributes that you would like to see in Eloqua
Note, once these attributes are enabled, these attributes are available immediately in Eloqua. You will need to close the feeder and open it again if you don't see it immediately.