- Campaign Standard documentation
- Latest Updates
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Get started with communication channels
- About communication channels
- Delivery best practices
- Email messages
- SMS messages
- Push notifications
- In-App messaging
- Direct mail
- Transactional messaging
- Landing pages
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- Get started with Campaign integrations
- Campaign and Experience Manager
- Campaign and Target
- Campaign and Analytics
- Campaign and Audience Manager or People core service
- Campaign and Analytics for Mobile
- Campaign and Triggers
- Campaign and Microsoft Dynamics 365
- Campaign and Adobe Experience Platform
- Managing processes and data
- Get started with data and processes management
- Workflow general operation
- Executing a workflow
- Calling a workflow with external parameters
- Targeting activities
- Execution activities
- Channel activities
- Data management activities
- Filtering data
- Importing and exporting data
- Use cases
- About workflow use cases
- Deliveries
- Creating deliveries with a complement
- Creating deliveries on profiles’ creation date
- Creating a weekly delivery
- Creating a cross-channel delivery
- Identifying duplicates before a delivery
- Birthday delivery
- Coupling email and direct mail deliveries
- Sending an email with enriched fields
- Personalizing an email with additional data
- Sending a recurring push notification
- Segmentation and targeting
- Data management
- Reconcile a File audience with the database
- Deduplicating the data from an imported file
- Enriching profile data with data contained in a file
- External signal activity and data import
- Updating the database with external data
- Updating data based on an automatic file download
- Data reconciliation using relations
- Data update using reconciliation
- Exporting profiles in an external file
- Updating multiple subscription statuses from a file
- Subscribing profiles from a file to a specific service
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- Audit Trail
- Configuration guidelines
- Users and security
- Configuring channels
- Configuring mobile channels
- Implementing Push tracking
- Adding images and videos iOS
- Understanding push notifications payload structure
- Implementing local notification tracking
- Tags in Adobe Experience Platform synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring tag rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- How to migrate your mobile application from SDK v4 to Adobe Experience Platform SDK
- Configuring SMS channel
- Application settings
- Working with APIs
- Get started with Campaign Standard APIs
- About Campaign Standard APIs
- Global concepts
- Interacting with custom resources
- Managing profiles
- Managing services and subscriptions
- Interacting with marketing history
- Privacy management
- Managing transactional messages
- Managing workflows
- Managing organizational units
- Managing geographical units
- Troubleshooting
- Campaign Control Panel
Mapping activation
Adobe Experience Platform Data Connector is currently in beta, which may be subject to frequent updates without notice. Customers are required to be hosted on Azure (currently in beta for North America only) to access these capabilities. Please reach out to Adobe Customer Care if you would like access.
When the mapping definition is completed, you can publish the mapping. After the deployment step, the data replication between Campaign Standard and Adobe Experience Platform is automatically started. At any time, you can stop the replication by clicking on the Stop button.
Depending on your mapping modifications, you can choose to resend all your records to Adobe Experience Platform.
From the deployment tile, you can access publication log and exports logs.
In the Export jobs tab, you can monitor the export job for the published mapping.
If you want to monitor all the data export jobs, go to Administration > Development > Platform > Status of data export to platform menu.
Data ingestion job statuses are:
- Created: A data ingestion job is created and data ingestion is in progress.
- Failed: A data ingestion job has failed. The reason field describes the reason for the failure. Failure can be transient or permanent. In case of transient failures, a new ingestion job is created after a configured interval. As a first step to troubleshooting, user can check the reason field of the failure. If the reason redirects a user to Adobe Experience Platform UI, user can login to Adobe Experience Platform and can check the batch status in the dataset to determine exact failure reason.
- Uploaded: A batch is first created in Adobe Experience Platform and data is then ingested to the batch. Batch ID field shows the batch id for the batch in Adobe Experience Platform. Adobe Experience Platform also performs a post validation on the batch. The batch is first marked as uploaded until Adobe Experience Platform completes the post validation step. A job keeps polling Adobe Experience Platform for the status of the batch after uploading. A batch can go either in Failed or in Success state post validation in Adobe Experience Platform.
- Success: After a batch is uploaded to Adobe Experience Platform, the status of the job (post validation in platform) is checked after a configured interval. A status ‘Success’ identified a successful ingestion of data in Adobe Experience Platform.
In some cases, you may get the validation error below when publishing your mapping.
This occurs when the XDM schema you are using has not been updated with the latest XDM field related to privacy management and still contains the deprecated “ccpa” XDM field.
To update the XDM schema, follow these steps:
-
Go to the dataset on Adobe Experience Platform using the link present on the XDM mapping page.
-
Navigate to your XDM schema.
-
Add the Profile Privacy mixin to the schema.
-
Save the schema, then retry publishing the mapping. The publication should now pass.
Business.Adobe.com resources
Resources
Adobe Account
