Not on the AJO side, this needs to be monitored on the customer side to understand how frequently the authentication end point is being hit.

You can let the journey run daily and by using a condition activity, that will allow profiles to pass through only on specific days. Reference - https://experienceleague.adobe.com/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/condition-activity.html?lang=en#time_condition ...

You can take a look at these links to get an understanding of the ingestion and activation components.https://experienceleague.adobe.com/docs/platform-learn/getting-started-for-data-architects-and-data-engineers/ingest-batch-data.html?lang=en https://experienceleague.adobe.com/docs/journey-optimizer...

you will have to override all the three parameters, ensuring the appId and token are specific to fcm.   

Here are a couple of ways -  Data Access APIIt facilitates the access and egress of data within Adobe Experience PlatformReference - https://experienceleague.adobe.com/docs/experience-platform/data-access/api.html Export Datasets to Cloud storageNote - This functionality is available to customers wh...

If the user has both ios and android defined at the surface level, you will see the iOS section as default values in the push parameters section and this doesn't mean android devices won't be targeted.Two push messages will be sent (with a single push activity in the canvas) based on the (token + ap...

Audience qualification is for unitary journeys and read audience is for batch journeys. If you need only the delta records to enter the journey since the last execution, incremental read option needs to be toggled on. From your example, only 2 records will enter on the second execution in this scena...

In the current state, AJO Landing Pages are primarily meant to work in sync with subscription lists / ootb consent attributes only for existing users and capturing other attributes (as an acquisition) is not feasible at the moment.

Custom actions should ideally be used with unitary journeys where the volumes are discrete.This is basically to avoid overwhelming the REST API endpoints when an audience is used. In your case, you should  explore HTTP API for destinations to see if that meets your requirement https://experienceleag...

It looks like the merge policy for the look up schema is not created when the lookup schema was created. Kindly verify this by performing the below call and if it's missing, you may have to get the same created.POST /access/entities Ref - https://experienceleague.adobe.com/docs/experience-platform/p...