My Oracle Support Banner

CED: Workaround for Lack of CUSTOMER_ID in Holdout CED feed, Using the Get Data Stage (Doc ID 2551365.1)

Last updated on APRIL 29, 2020

Applies to:

Oracle Responsys Marketing Platform Cloud Service - Version 6X to 6X [Release 6x]
Information in this document applies to any platform.

Symptoms

In Program, you can use the Holdout group stage to contain a random group of contacts that will not receive a campaign. This group is populated by sending a percentage of contacts to it through an Allocation switch. This allows you to compare performance of customers who received a campaign to those who did not. Program sends the RIID_ of enactments in the holdout group to the event table. The RIID_ values of the contacts are stored in the source table for the Holdout CED feed. However, the event raised from Holdout stage to Event database does not contain CUSTOMER_ID_ value. Therefore, the Holdout CED feed doesn't contain the CUSTOMER_ID_ value.

This bulletin is intended for Oracle Responsys customers who want to use the Get Data program stage in Program to work around the issue of the Holdout CED feed not providing the CUSTOMER_ID. This document assumes that you are familiar with creating program orchestrations in Responsys and with creating SQL views.

IMPORTANT: This workaround is intended only for customers whose accounts are:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 Workaround:
 References:

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.