Profiles visible in queries but 0 results in Audience – how to activate and send them to AJO?

[OmarGo2]

Hi everyone,

I already have some test profiles in Adobe Experience Platform. I can clearly see them when I query the dataset and also in the Profile section, where the profiles contain email information.

My goal is to:

1. Convert these profiles into an audience

2. Send that audience to Adobe Journey Optimizer (AJO) to activate them in a campaign

However, when I try to create a very simple audience using the condition “Personal Email exists”, the audience returns 0 profiles, even though the email field is populated in the profiles.

I’d like to understand:

• What prerequisites must be met for profiles to qualify into an audience?

• Are there specific requirements around identity stitching, merge policies, or profile-enabled datasets that could cause this behavior?

• Is there any additional step required before audiences can be sent to AJO?

Any guidance or best practices would be greatly appreciated. Thanks in advance!

[Asheesh_Pandey]

@OmarGo2  At first, It may be related with Audience evaluation timing and backfill. i.e.

• For batch evaluation, newly ingested records may need a run of the segmentation job before counts appear.
• If using edge segmentation, ensure that your test profiles have gone through the necessary data flow and are visible in Profile with the latest ingestion time.

[OmarGo2]

Hi @Asheesh_Pandey , that segmentation job happens automatically? I'm not sure what the correct steps are. I just created the schema and dataset, then uploaded the JSON.

JSON:

[
  {
    "personID": "P001",
    "person": {
      "name": {
        "firstName": "Osmar",
        "lastName": "Perez"
      }
    },
    "mobilePhone": {
      "countryCode": "51",
      "number": "956601621"
    },
    "personalEmail": {
      "address": "aapp@gmail.com"
    }
  },
  {
    "personID": "P002",
    "person": {
      "name": {
        "firstName": "Ana",
        "lastName": "Perez"
      }
    },
    "mobilePhone": {
      "countryCode": "51",
      "number": "987654321"
    },
    "personalEmail": {
      "address": "ana.perez@testmail.com"
    }
  },
  {
    "personID": "P003",
    "person": {
      "name": {
        "firstName": "Carlos",
        "lastName": "Ramos"
      }
    },
    "mobilePhone": {
      "countryCode": "51",
      "number": "912345678"
    },
    "personalEmail": {
      "address": "carlos.ramos@testmail.com"
    }
  }
]

[Asheesh_Pandey]

Steps to create the audience 

• In Schemas:

  • Open your profile schema, confirm:

    • Class = XDM Individual Profile.

    • “Profile” toggle is on.

    • A primary identity field is configured.

    • The email field you care about is present (e.g., personalEmail.address).​

• In Datasets:

  • Open the dataset you query, confirm:

    • It uses that schema.

    • “Profile” is enabled.

    • The latest batches are after Profile was enabled.​

• In Profiles / Merge policies:

  • Pick one known test profile and look it up in Profiles; verify the email field appears under Attributes and is not empty.​

  • Check which merge policy is active for segmentation and ensure your dataset is included and not overridden by another dataset that lacks email.​

• In Audiences (Segment Builder):

  • Build a new audience with a single rule: drag the correct email field from the attribute tree, set operator to exists, save the audience.​

  • Let batch segmentation run, then check Qualified profiles or profile membership for your known test profile.​

Following those checks will take profiles you see in queries/Profile UI and ensure they are actually usable as a qualifying audience that you can later send to AJO.

[OmarGo2]

I think the issue is here:

How do you check if a merge policy is active for segmentation? and the dataset is included and not overriden by another data set that lacks email? I'd appreciate if you can share some screenshots.

Thank you.

[OmarGo2 · Accepted solution]

I found the issue: When creating an audience, what you should do is click the wheel and select the merge policy. The rule you use to build will use the merge policy to return results and it should be the same as the one you use when creating the profiles.