Frequently asked questions faq
Overview overview
This document provides answers to frequently asked questions about Adobe Experience Platform destinations. For questions and troubleshooting related to other Platform services, including those encountered across all Platform APIs, please refer to the Experience Platform troubleshooting guide.
General destinations questions general
Why am I seeing different profile counts in the Experience Platform UI and in the exported CSV files?
This is a normal behavior due to the way Experience Platform performs segmentation.
Streaming segmentation updates the profile count for streaming audiences throughout the day, while batch segmentation updates the profile count for batch audiences once every 24 hours.
When the audience export schedule differs from the segmentation schedule, the profile counts between the UI and the exported CSV file will be different, especially when it comes to streaming audiences.
See the Segmentation Service documentation for more details.
Why do I see low match rates upon de-activating and re-activating an updated audience to the same destination?
The de-activation and of an audience from a streaming destination does not trigger a backfill upon audience re-activation to the same streaming destination.
Example
You activated an audience consisting of 10 profiles to a streaming destination.
After activating the audience, you realize you want to change the audience configuration, so you de-activate the audience and change its population criteria, leading to an audience population of 100 profiles.
You re-activate the updated audience to the same destination, but since there is no backfill triggered, your destination does not receive the additional 90 profiles.
Solution
To ensure all the profiles are sent to your destination, you must create a new audience with the new configuration, and then activate it to your destination.
Facebook Custom Audiences facebook-faq
What do I need to do before I can activate audiences in Facebook Custom Audiences?
Before you can send your audiences to Facebook, make sure you meet the following requirements:
-
Your Facebook user account must have the Manage campaigns permission enabled for the Ad account that you plan to use.
-
The Adobe Experience Cloud business account must be added as an advertising partner in your Facebook Ad Account. Use
business ID=206617933627973. See Add Partners to Your Business Manager in the Facebook documentation for details.note important IMPORTANT When configuring the permissions for Adobe Experience Cloud, you must enable the Manage campaigns permission. This is required for the Adobe Experience Platform integration. * Read and sign the Facebook Custom Audiences Terms of Service. To do this, go to `https://business.facebook.com/ads/manage/customaudiences/tos/?act=[accountID]`, where `accountID` is your Facebook Ad Account ID.
Do I need to add any apps or pixels to my Facebook advertiser account?
How long does Facebook take to process information from Adobe Experience Platform?
Can I use Facebook Custom Audiences for audience targeting in other Facebook apps, like Instagram?
What is the difference between the Facebook Custom Audiences connection and Facebook Pixel extension?
The Facebook Custom Audiences connection uses Platform identities when sending audiences to Facebook, while the Facebook Pixel connection uses the Facebook pixel integrated in a website.
These two integrations are complementary; you can use both to ensure better audience coverage. As an example, you can use the Facebook Pixel extension for prospecting website visitors who have not created an account, whereas Facebook Custom Audiences can help you target existing customers, based on Platform identities.
Does the Adobe Experience Platform integration with Facebook Custom Audiences support disqualifying users from an audience when they no longer qualify for it?**
How should I hash the audience data before sending it to Facebook?
Facebook requires that no personally identifiable information (PII) is sent in clear. Therefore, the audiences activated to Facebook can be keyed off hashed identifiers, such as email addresses or phone numbers.
For detailed explanations on the ID matching requirements, see ID matching requirements.
What kind of identities can I activate in Facebook Custom Audiences?
Can I create multiple Facebook destinations in the Platform UI for separate Facebook accounts?
Google Customer Match google-customer-match
When exporting audiences to Google Customer Match, why am I seeing extra numbers appended at the end of the audience names in the Google interface?
LinkedIn Matched Audiences linkedin
Do I need to add any apps or pixels to my LinkedIn advertiser account?
What do I need to do before I can activate audiences in LinkedIn Matched Audiences?
Before you can use the LinkedIn Matched Audience destination, make sure your LinkedIn Campaign Manager account has the Creative Manager permission level or higher.
To learn how to edit your LinkedIn Campaign Manager user permissions, see Add, Edit, and Remove User Permissions on Advertising Accounts in the LinkedIn documentation.
How should I hash the audience data before sending it to LinkedIn?
LinkedIn requires that no personally identifiable information (PII) is sent in clear. Therefore, the audiences activated to LinkedIn can be keyed off hashed identifiers, such as email addresses or phone numbers.
For detailed explanations on the ID matching requirements, see ID matching requirements.
What kind of identities can I activate in LinkedIn?
Same-page and next-page personalization through the Adobe Target and Custom Personalization destinations same-next-page-personalization
Do I need to use the Experience Platform Web SDK to send audiences and attributes to Adobe Target?
No, Web SDK is not required to activate audiences to Adobe Target.
However, if at.js is used instead of Web SDK, only next-session personalization is supported.
For same-page and next-page personalization use cases, you must use either Web SDK or the Edge Network Server API. See the documentation on activating audiences to edge destinations for more implementation details.
Is there a limit on the number of attributes that I can send from Real-time Customer Data Platform to Adobe Target or a Custom Personalization destination?
What types of attributes are supported for activation (e.g. arrays, maps, etc.)?
person.name.firstName. Array attributes are currently not supported.After I create an audience in Experience Platform, how long will it take for that audience to be available for edge segmentation use cases?
Where can I see the activated attributes in Adobe Target?
Can I create a destination without a datastream and then add a datastream to the same destination at a later point?
What happens if I delete an Adobe Target destination?
Does the integration work using the Edge Network Server API?
I can only have one merge policy that is active-on-edge. Can I build audiences that use a different merge policy and still send them to Adobe Target as streaming audiences?
Are Data Usage Labeling and Enforcement (DULE) and Consent Policies enforced?
Are the Adobe Target and Custom Personalization destinations HIPAA-compliant?
Adobe Target is not HIPPA-compliant with Adobe Healthcare Shield. Customers should check with their own legal teams regarding HIPPA-readiness for custom optimization channels before using edge personalization via Adobe Target or the Custom Personalization destinations.
For use cases where consent policy management needs to be applied at scale, customers must purchase Adobe Privacy & Security Shield. Adobe Privacy & Security Shield features are sold as an advanced suite of capabilities and may not be purchased separately.
This service includes customer-managed keys and elevated thresholds to manage the customer data lifecycle.
The Adobe Target and Custom Personalization destinations are integrated with the Experience Platform Data Usage Labels and the Consent Policy Enforcement Service. These features are available for all customers.