Difference between FAC Save profile and standard AEP Profile | Community
Skip to main content
Sneha-Parmar
Community Advisor
Sneha-ParmarCommunity Advisor
Community Advisor
October 7, 2025
Solved

Difference between FAC Save profile and standard AEP Profile

  • October 7, 2025
  • 1 reply
  • 348 views

Hi All,

Can anyone please suggest what is the difference between between profile attributes saved via FAC Save profile feature and standard AEP Profile by data ingestion ? What are the limitations of using FAC Save profile ? Is it possible to use save profile for profiles that does not exist in AEP?

Thankyou !

Best answer by Devyendar

Federated Audiences Composition - FAC

  • It allows us to design, enrich, and publish composed audiences from external source systems (currently supported AWS Redshift, Azure Synapse Analytics, Databricks, Google BigQuery, Microsoft Fabric, Oracle, Snowflake and Vertica Analytics) without fully ingesting the data into AEP.
  • The FAC audiences can be only used through RTCDP destinations
  • Enabling Federated Audiences also requires additional license it is not supported in standard AEP/RT-CDP licenses.
  • FAC allows AEP to create segments based on data present only in the company-internal databases, without sending any sensitive data to AEP.

AEP Standard Audiences

  • AEP has full control on this data and data ingestion process too is longer from Source Connectors > Schemas > Namespaces > Dataset > Profiles > Streaming/Batch Audiences > RTCDP Destination/JO/CJA/ Query Service allowing full utilization of the data based on orgs use cases.

Additionally, FAC is shorter for Go-to-Marketo and AEP Audiences are longer depending on amount of data that is needed.

Here is a good demo on FAC leveraging Microsoft Fabrics - https://business.adobe.com/summit/2025/sessions/turning-insights-to-gold-with-federated-audience-s712.html

1 reply

Devyendar
DevyendarAccepted solution
Level 6
October 9, 2025

Federated Audiences Composition - FAC

  • It allows us to design, enrich, and publish composed audiences from external source systems (currently supported AWS Redshift, Azure Synapse Analytics, Databricks, Google BigQuery, Microsoft Fabric, Oracle, Snowflake and Vertica Analytics) without fully ingesting the data into AEP.
  • The FAC audiences can be only used through RTCDP destinations
  • Enabling Federated Audiences also requires additional license it is not supported in standard AEP/RT-CDP licenses.
  • FAC allows AEP to create segments based on data present only in the company-internal databases, without sending any sensitive data to AEP.

AEP Standard Audiences

  • AEP has full control on this data and data ingestion process too is longer from Source Connectors > Schemas > Namespaces > Dataset > Profiles > Streaming/Batch Audiences > RTCDP Destination/JO/CJA/ Query Service allowing full utilization of the data based on orgs use cases.

Additionally, FAC is shorter for Go-to-Marketo and AEP Audiences are longer depending on amount of data that is needed.

Here is a good demo on FAC leveraging Microsoft Fabrics - https://business.adobe.com/summit/2025/sessions/turning-insights-to-gold-with-federated-audience-s712.html

    Terms & ConditionsAccessibility statement

    Loading footer...