ÃÛ¶¹ÊÓƵ Campaign Managed Cloud Services
ÃÛ¶¹ÊÓƵ Experience Platform allows data to be ingested from external sources while providing you with the ability to structure, label, and enhance incoming data using Platform services. You can ingest data from a variety of sources such as ÃÛ¶¹ÊÓƵ applications, cloud-based storage, databases, and many others.
ÃÛ¶¹ÊÓƵ Campaign Managed Cloud Services provides a Managed Services platform for designing cross-channel customer experiences and provides an environment for visual campaign orchestration, real time interaction management, and cross-channel execution. Visit the ÃÛ¶¹ÊÓƵ Campaign v8 documentation for more information.
The ÃÛ¶¹ÊÓƵ Campaign Managed Cloud Services source allows you to bring ÃÛ¶¹ÊÓƵ Campaign v8 delivery logs and tracking logs data to ÃÛ¶¹ÊÓƵ Experience Platform.
Prerequisites
Before you can create a source connection to bring your Campaign v8 to Experience Platform, you must first complete the following prerequisites:
View delivery and tracking log data view-delivery-and-tracking-log-data
Log in to your Campaign v8 instance through the Client Console. Under the Explorer tab, select Administration and then select Configuration. Next, select Data schemas and then apply the broadLog
filter for name or label. In the list that appears, select the recipient delivery logs source schema with the name broadLogRcp
.
Next, select the Data tab.
Right-click/keystroke in the data panel to open the contextual menu. From here, select Configure list…
The list configuration window appears, providing you with an interface where you can add any desired fields to the pre-existing list to view the data in the data panel.
Now you can view your recipient delivery logs, including the configuration fields added in the previous step.
tracking
to view your tracking log data.
Create a schema create-a-schema
Next, create an XDM ExperienceEvent schema for both delivery logs and tracking logs. You must apply the Campaign Delivery Logs field group to your delivery logs schema and the Campaign Tracking Logs field group to your tracking logs schema. You must also define the externalID
field as the primary identity of your schema.
For detailed instructions on how to create a schema, read the guide on creating an XDM schema in the UI.
Create a dataset create-a-dataset
Finally, you must create a dataset for your schemas. For detailed instructions on how to create a dataset, read the guide on creating a dataset in the UI.
Create an ÃÛ¶¹ÊÓƵ Campaign Managed Cloud Services source connection using the Platform UI
Now that you have accessed your data logs in the Campaign client console, created a schema, and a dataset, you can now proceed to create a source connection to bring your Campaign Managed Services data to Platform.
For detailed instructions on how to bring your Campaign v8 delivery logs and tracking logs data to Experience Platfrom, read the guide on creating a Campaigned Managed Services source connection in the UI.
- This scenario is only active between the time a privacy request has been executed in Experience Platform and the time it has been executed in ÃÛ¶¹ÊÓƵ Campaign Classic. After the request is executed in Campaign, there is a check to ensure the record is not exported to Campaign. Please re-issue a GDPR request after 72 hours of the execution, to resolve this.