Data availability and sync timing data-availability
Use this topic to understand how quickly data changes appear in your Adobe Journey Optimizer B2B Edition journeys and which timelines are normal. Knowing the expected timing helps you design journeys accordingly and recognize when a delay is expected behavior.
Expected wait times
Audience and relationship data daily-refresh
Journey Optimizer B2B Edition evaluates account and person audience membership once per day, triggered by a batch job scheduler. As a result:
- Accounts or people who newly qualify for an audience become eligible to enter a journey within 24 hours of qualifying.
- Changes to audience criteria take effect in the next daily evaluation cycle.
- If an account qualified for an audience today but has not entered the journey yet, wait until the next daily cycle completes before investigating.
- When a person’s account association changes, for example when a contact moves to a different account, the relationship update propagates within 24 hours through the daily sync cycle. Journeys that depend on account membership reflect the updated relationship after the next daily cycle. No action is needed.
Data sync with Experience Platform platform-sync
Experience Platform is the primary data store for accounts, people, and opportunities, and Journey Optimizer B2B Edition owns journeys, buying groups, and buying group roles. Learn more about the architecture.
Data moves between the two systems in each direction at a different pace:
- Experience Platform to Journey Optimizer B2B Edition - Data syncs in near real time and can take up to 30 minutes.
- Journey Optimizer B2B Edition to Experience Platform - Data syncs in micro-batches and can take up to 4 hours.
Activity events and journey actions activity-and-actions
Timing for activity data and journey actions depends on how the data moves between systems:
- Activity data - Person activity records, such as email opens, link clicks, and form fills, can take approximately four hours to appear in Journey Optimizer B2B Edition. This timing applies to batch activity data; Experience Platform Experience Event triggers use streaming data and can react in near real time.
- Marketo Engage actions - Journey actions that call Marketo Engage are near real time because they are API calls. For example, when a journey step adds or removes a person from a Marketo list, the action typically completes within 30 minutes. Learn more about journey actions.
- Actions that go through Experience Platform - Any action that returns to Experience Platform first is batched, so it is subject to batch timing rather than near-real-time timing.
- Events generated by Journey Optimizer B2B Edition - Events that Journey Optimizer B2B Edition generates in Experience Platform can only be used in batch audiences.
LinkedIn audience destinations linkedin-timing
If your journey includes a LinkedIn destination action, expect the following timeline after you publish the journey.
LinkedIn audience counts might not update immediately. This lag is an expected delay while Experience Platform processes and delivers the audience file to LinkedIn. If the audience count is still 0 after 48 hours, investigate. Learn more about LinkedIn Account Matched Audiences.