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.

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.

No, there is no dependency between the Experience Platform destination and the customer instance of the target system. On the receiving side, the only indication that the target system would see is that it stopped receiving that audience data.

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.

  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.

No. As this is not a pixel-based integration, there is no need to add any pixels to your advertiser account.

As of March 2021, Facebook Custom Audiences needs up to an hour to process information received from Platform.

You can use the Facebook Custom Audiences destination for audience targeting across Facebook’s family of apps that are supported by Facebook Custom Audiences, including Facebook, Instagram, Audience Network, and Messenger. Selection of the app which advertisers want to run campaigns on is indicated at the placement level in Facebook Ads Manager.

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.

Yes, the integration supports removing users from Facebook Custom Audiences when they no longer qualify.

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.

Facebook Custom Audiences supports the activation of the following identities: hashed emails, hashed phone numbers, GAID, IDFA, and custom external IDs.

Yes. A Facebook destination in Experience Platform is 1:1 to an ad account in Facebook. You can create a separate Facebook destination for each Facebook ad account in your company. Follow the destination connection tutorial and connect to a separate Facebook account for each new Facebook destination in the Platform UI. There is no limit on the number of Facebook ad accounts that you can connect to.

Google requires audience names to be unique. The numbers that you are seeing are UNIX timestamps and they are appended to keep the audience names unique, if you mapped the same audience to multiple Google destinations.

No. As this is not a pixel-based integration, there is no need to add any pixels to your advertiser account.

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.

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.

LinkedIn Matched Audiences supports the activation of the following identities: hashed emails, GAID, and IDFA.

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.

Yes, same-page and next-page personalization use cases support a maximum of 30 attributes per sandbox, when activating audiences to Adobe Target or Custom Personalization destinations. See more information about activation guardrails in the guardrails documentation.

Currently, only static, single-value attributes are supported, such as person.name.firstName. Array attributes are currently not supported.

Audience definitions are propagated to the Edge Network in up to one hour. However, if an audience is activated within this first hour, some visitors who would have qualified for the audience could be missed.

Attributes will be available to use in Target in JSON and HTML offers.

This is currently not supported through the Destinations UI. If you need assistance in this case, please reach out to your Adobe representative.

When you delete a destination, all audiences and attributes mapped under the destination are deleted from Adobe Target and they are also removed from the Edge Network.

Yes, the Edge Network Server API works with the Custom Personalization destination. Since profile attributes may contain sensitive data, in order to protect this data, the Custom Personalization destination requires you to use the Edge Network Server API for data collection. Furthermore, all API calls must be made in an authenticated context.

No. All audiences that you want to activate to Adobe Target must use an active-on-edge merge policy.

Yes. The Data Governance and Consent Policies created and associated with the selected marketing actions will govern the activation of the selected attributes.

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.