Troubleshooting
- Topics:
- Triggers
CREATED FOR:
- Intermediate
- Developer
Errors may be encountered while using the integration with Audience Manager or People core service.
In this case, make sure that the following elements are correctly configured:
-
External accounts
In Administration > Application settings > External accounts, make sure that the following external S3 accounts are correctly configured. The mentioned S3 servers should have been configured during provisioning.
- importSharedAudience: S3 account dedicated to importing audiences.
- exportSharedAudience: S3 account dedicated to exporting audiences.
-
Shared Data Sources
In Administration > Application settings > Shared Data Sources, check that the shared data source is set properly.
Priority is used when you have multiple data sources defined. Priority decides which data source will be used to match with alias received in the order defined. Priority is only needed for Triggers implementation.
Check that the reconciliation key is correct. It is the hashed/encrypted value of this field that is used to export and import audiences.
In case of hashing or encryption of the declared ID, check that the same parameters/encryption algorithms are used on your Website.
Only one encryption algorithm is supported: AES in CBC mode with a key size of 128, 192 or 256 bits, with PKCS padding.
If the AES encryption algorithm is selected, the following additional fields must be correctly set:
- Encryption Key for AES
- Encryption IV (Initialization Vector) for AES
- Channel (Email/SMS/Other): This field allows to directly decrypt email addresses and SMS numbers. Make sure that the reconciliation key matches the setting of the Channel field. If you select “Other”, this specific decryption will not happen and the reconciliation key will be used to reconcile the data.
Experience Cloud audiences might not be shared because the technical workflow has stopped or paused. Access the Import shared audience workflow by clicking directly the Show ImportShared Audience workflow option in your Data source.
It can occur that some data are missing when sharing an audience via People core service or when importing an audience. Only records of which the ID (‘Visitor ID’ or ‘Declared ID’) was able to be reconciled with the profile dimension are transferred. IDs from the People core service segments that are not recognized by Adobe Campaign are not imported.
Campaign
- Campaign Standard documentation
- 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
- Push Notification Channel changes
- 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