PCO FAQs

1. What assets are created by PCO in Eloqua? #

PCO creates assets in Eloqua in a few scenarios. The following section explains the assets created and the reason behind them.

Contact View #

• Contact view is created in Eloqua manually during initial onboarding and it will be used while displaying the contacts involved in an email.
• This asset will not be deleted from Eloqua.

Shared List #

• 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.

Program #

• Eloqua programs are created to capture the flow of decision steps. Once the contact flow is successfully captured, the program is activated and subsequently deactivated.
• The temporarily created program aids PCO in predicting future email deployments for scheduled campaigns.
• The program PCO creates is not only deactivated, but also deleted upon the completion of the process.

Segment #

• Segments are created temporarily to track the flow of engagement-level steps, such as email clicks, sends, opens, and more.
• The segment created by PCO aids in predicting future email deployments for scheduled campaigns.
• The temporary asset is deleted upon the completion of the process.

Picklist #

• A temporary picklist is created and contacts are added to it. This picklist is utilized in segments, which allows the program to include the contacts in the picklist into the segment’s flow.
• The picklist created by PCO aids in predicting future email deployments for scheduled campaigns.
• This temporary picklist is deleted upon the completion of the process.

2. What data does PCO capture from Eloqua? #

PCO stores Eloqua data and Assets for its operation.

Assets (Metadata) #

Campaign #

• PCO stores all the campaigns that have the email sends for 1 month from the date of configuration.
• PCO keeps on taking the backup of the campaigns that send the emails.
• Following is the snippet of the data points captured by PCO.

Email Assets #

Email assets are used to display the email instance cards on the PCO.

• PCO stores all the emails that have been sent from 1 month from the date of configuration.
• PCO keeps on taking the backup of the new emails that are being sent.
• Following is the snippet of the data points captured by PCO.

Email Groups #

• Email groups are backed up along with the email assets from Eloqua so that PCO can provide better filtering on the board.
• Following is the snippet of the data points captured by PCO.

Segment #

• Segments are backed up along with the campaigns from Eloqua so that PCO can provide better filtering on the board.
• Following is the snippet of the data points captured by PCO.

Campaign Field Value #

• Campaign fields are backed up along with the campaigns from Eloqua so that PCO can provide better filtering on the board.
• Following is the snippet of the data points captured by PCO.

Email Sends #

• 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

Contacts #

• Contacts will be mapped to the email sends and will be used to group into accounts. They will be shown on the Email and Campaign Cards
• The following data points are stored against Contact.

Accounts #

• Accounts are being used to map the contacts and are displayed on the campaign and email cards.
• The following data points are stored against Account.

3. 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.

4. Is there any way to skip storing the username and password? #

Yes, but it comes at a cost. In case of an OAuth failure, without stored credentials, PCO cannot synchronize its data with Eloqua. One must constantly monitor this situation to catch such 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.