@Jorge_RogelioZe It's complaining about the contextual data being used in the URL advanced function. The function was looking for a domain name and couldn't recognize that from the contextual data.    

No. Use the audience builder "build rule" option if that works for your needs.

@Pradeep-Jaiswal You have two options. First you mentioned using the FAC combine audience option. Another thing is that AJO can't combine audiences like FAC, so instead, use the audience builder's Build rule option to include the audiences (audience of audiences).

@Daniel_cardoso Take a look at the custom audience upload approach to see if that works for your use cases. https://experienceleague.adobe.com/en/docs/journey-optimizer-learn/tutorials/profiles-audiences-subscriptions/import-and-activate-an-audience-by-uploading-a-csv-file https://experienceleague.a...

@HardikJa3 I recommend looking through the Email Tracking Experience Event Dataset via query service tracking dataset to figure out where these click data coming from or else look at the CJA to figure out the sources.

@Silvio6 If you have a CJA you can setup these custom alerts but there will be a delay in getting the alerts.

@Selliers You don't necessarily need to render it from an email rather you can see the landing page with the test profile. Would it be possible for you to share the screenshot of the landing page setup?

Ideally, the count between the profile snapshot and the audience should stay the same after the evaluation. Try a couple of different by splitting the criteria into two different audiences and see how that works. Also, run a query against the last criteria that you mentioned in the audience. If you ...

That's weird. I wanted to confirm that the behavior is consistent if you change the criteria the other way around. One more thing did you try with the specific date range to see if that excludes intended profiles?

@chrisyan Did you try the other way around? registration_date + 3 months <= expect_date