During the export of audiences to the MFT location, some identities are being excluded. What could be causing this | Community
Skip to main content
R
ReshmikaPu2
Level 2
June 12, 2026
Question

During the export of audiences to the MFT location, some identities are being excluded. What could be causing this

  • June 12, 2026
  • 2 replies
  • 52 views

Hi ​@Asheesh_Pandey , ​@jachlt , ​@Parvesh_Parmar , ​@SantoshRa5 

I’m looking for guidance on how to backtrack and analyze excluded identities during exports in  AEP. Currently, we don’t have any mandatory fields or consent labels configured, so I’m unsure what might be causing these exclusions.

Are there other factors or checks we should be considering that could lead to identities being excluded? Additionally, how can we effectively trace back and understand why certain identities are not included in the export?

Any insights or suggestions would be greatly appreciated



https://experienceleague.adobe.com/en/docs/experience-platform/dataflows/ui/monitor-destinations#dataflow-runs-for-batch-destinations

Thak​​​

    2 replies

    Asheesh_Pandey
    Community Advisor and Adobe Champion
    Asheesh_PandeyCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    June 13, 2026

    ​@ReshmikaPu2 for file-based destinations, AEP exports rows based on identities, not just audience membership. that means 1. profile that qualifies for audience but has no mapped identity will be excluded, 2. profile that has multiple identities but mapped namespace missing will be excluded, 3. profile exists but activation namespace is null will be excluded.

    Steps to check foundation :

    1. Check what identity namespace is configured for export? 
    2. Profiles don't have that namespace populated, they'll be excluded.
    3. Check if identity namespace not marked as primary or not available on merged profile
    4. If audience built on anonymous profiles identity but MTF expert expect other id, anon profile will be excluded.

    Validation steps:

    1. use Query Service query to check missing identity have correct namespace
    2. Check if MFT export configured as profile export or dataset export. For profile export missing identities will be excluded, for dataset export rules are not same.

    3. To monitor it go to destinations > Your MFT > Dataflow Runs > Most Recent Run - you may see exclusion details in the activation details.

    - Asheesh
    R
    ReshmikaPu2Author
    Level 2
    June 18, 2026

    ​@Asheesh_Pandey 
    Thank you for the insights 
    that helped 
    Would need more suggestions on my analysis 

     

    Steps to check foundation :

    1. Check what identity namespace is configured for export?  
        when I open the dataflow it shows empty 
      but inside mapping we have identitymap primary identity mapped
    2. Profiles don't have that namespace populated, they'll be excluded.
      we have our primary identity cross device ID as namespace inside mandatory fileds 
    3. Check if identity namespace not marked as primary or not available on merged profile
        it is primary and available on merged profile
    4. If audience built on anonymous profiles identity but MTF export expect other id, anon profile will be excluded.
      Is there a way to check this via QS could you please elaborate 


      ValidationSteps :
    5. use Query Service query to check missing identity have correct namespace
      we have 4 name spaces in identity map ( no missing name spaces)

      with default timestamp based merge policy 
      we have below numbers
      with default time basedmerge policy


      with NoID stitching merge policy
       


    6. Check if MFT export configured as profile export or dataset export. For profile export missing identities will be excluded, for dataset export rules are not same.
      it is profile export 
      is there a way to confirm on this 
      I have checked the type of export is audiences export (which shows profile count )

    7. To monitor it go to destinations > Your MFT > Dataflow Runs > Most Recent Run - you may see exclusion details in the activation details.


     

    I would appreciate additional guidance on this. I suspect that a higher number of profiles are being qualified using ECID compared to our cross-device ID for the audience, which may be causing them to be excluded.

    To validate this using Query Service (QS), could you please advise on the appropriate approach?

    Thank you for your guidance.

    R
    ReshmikaPu2Author
    Level 2
    June 26, 2026

    ​@Asheesh_Pandey  ​@Gokul_Agiwal  ​@Ritesh_Gupta 
    Any suggestions would be helpful thank you 

    Devyendar
    Devyendar
    Level 6
    June 14, 2026

    ​@ReshmikaPu2 yes all the profiles being export to the file export destination should have the identity mapped during the destination configuration any profile that doesn’t have the identity will be excluded, if any profiles even with identity is being excluded mostly likely it would be due to the Dule policies that might have been setup (if you are using it).

    Terms & ConditionsAccessibility statement

    Loading footer...