FAC + AJO real-time entry with Snowflake as SoR how are you handling this without ingesting everything into AEP? | Community
Skip to main content
Level 2
July 29, 2026
Question

FAC + AJO real-time entry with Snowflake as SoR how are you handling this without ingesting everything into AEP?

  • July 29, 2026
  • 0 replies
  • 4 views

Hello Folks, I am looking for a sanity check from anyone who has done this in production.

My current setup

  • Snowflake is our SoR for transactional/behavioral data (can't fully ingest into AEP due to cost + governance)

  • AEP RTCDP holds identity, consent, streaming web/mobile events

  • FAC federates the heavy Snowflake attributes (RFM, ownership, propensity)

  • AJO for orchestration, Data Distiller for computed attributes

  • There are around 80M profiles

Currently the problem is :

Business wants a Lapsed High-Value Reactivation journey that:

  • Qualifies on a 180-day look-back in Snowflake (via FAC)

  • Enters within approx. 30 min of a real-time cart-abandon event

  • Personalizes with Snowflake attributes that can change intra-day

The conflict: FAC audiences are batch-only, so they can't drive real-time journey entry. If I materialize everything into AEP via Data Distiller, I blow the profile budget and lose Snowflake as SoR.

I would like to know : 

  1. Has anyone made a pattern work where FAC provides the qualifier but a streaming AEP event provides the trigger without duplicating warehouse data into Profile?

  2. For send-time personalization from Snowflake, are you using AJO custom actions to warehouse API, or biting the bullet and syncing via Data Distiller? Any real-world latency / cost numbers appreciated.

Happy to go deeper if needed.

Thanks in advance!