As PCO does not store PII data, it only has the Eloqua Contacts IDs. When the user wants to see the contacts involved in an Email instance on the Email Detailed View, PCO uses these Eloqua Contact IDs and creates a Shared List on-demand and creates a quick view as below using the Contact View created earlier.
This shared list will be deleted right after the contact details are fetched.
PCO creates assets while making predictions of future email deployments for scheduled campaigns. The following section explains the assets created in this process.
Email sends are the basic data points that construct an email card on the board. They are used to populate instance and instance groups on Board View / Live View. They are exported using bulk API and stored in PCO.
Following data points are stored against Email Sends
Accounts are being used to map the contacts and are displayed on the campaign and email cards.
Following data points are stored against Account.
Eloqua Account ID
Domain
Company Name
Account Created
Account Modified
Why does PCO require to store username and password? #
PCO gives an air-traffic-controller-view of the campaigns running in Eloqua instance. Hence, it requires making several parallel calls into Eloqua, but the industry standard OAuth 2.0 might fail in some scenarios. In cases of such failures, to provide an uninterrupted experience, PCO is required to store username and password which can act as the backup mechanism in case of the OAuth failure.
Is there any way to skip storing the username and password? #
Yes, but it comes with a cost. In case of OAuth failure, PCO stops synchronizing its data with Eloqua. We must monitor it daily to catch the failures.
In the future, in such scenarios, a notification will be sent to the Eloqua administrator, and it is required to be reinstalled. Once reinstalled the application will cover the stop gap.
XWe use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies. . Read MoreDENYACCEPTCookie settings
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
elementor
never
This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time.
Portqii
1 year 1 month
First Party Cookie
viewed_cookie_policy
1 year
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
Cookie
Duration
Description
_calendly_session
21 days
No description available.
_lfa
2 years
This cookie is set by the provider Leadfeeder. This cookie is used for identifying the IP address of devices visiting the website. The cookie collects information such as IP addresses, time spent on website and page requests for the visits.This collected information is used for retargeting of multiple users routing from the same IP address.
AnalyticsSyncHistory
1 month
No description
li_gc
2 years
No description
UserMatchHistory
1 month
Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
bscookie
2 years
This cookie is a browser ID cookie set by Linked share Buttons and ad tags.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_gat_gtag_UA_146403593_1
1 minute
This cookie is set by Google and is used to distinguish users.
_gid
1 day
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Google Analytics
2 years
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
bcookie
2 years
This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.
lang
session
This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.
linkedin
1 day
This cookie is set by LinkedIn and used for routing.