Binary CipherChoose the right orchestration primitive.
Explain when to use a journey, campaign, orchestrated campaign, decision, or external system—and what each choice owns.
Available in production · $129 one-time
AJO Master Pack
The Journey Optimizer Operator Academy.
Master the whole operating system—from profile and event contracts to orchestration, content, delivery, decisioning, governance, measurement, and incident response. Then prove your judgment in a hands-on launch playground.
This review environment does not accept payment. The AJO Master Pack is available on the production site for $129 one-time.
Start here in 15 minutes
Get oriented before touching the canvas.
- 01Choose journey or campaign.
- 02Name the eligibility and consent contract.
- 03Define delivery proof and success evidence.
Operator outcomes
Build systems that are explainable before they are activated.
The pack trains the decisions that determine whether an AJO implementation is safe, observable, reusable, and measurable.
Connect every production contract.
Trace identity, profile, audience, event, content, consent, channel, decision, and measurement dependencies end to end.
Find the first failed handoff.
Diagnose non-entry, suppression, personalization, delivery, and reporting failures with evidence instead of guesses.
Run a defensible launch review.
Assign owners, capture approvals, rehearse rollback, and communicate residual risk across business and technical teams.
Three ways to learn
See the AJO operating model before you build it.
Use the field notes to remember the sequence, the sticky board to run a launch review, and the system map to trace a journey from signal to evidence.
Operator field notes
AJO · production sequence
Start with entry, exit, and evidence — not activities.
1 · Choose the primitive
Use a journey for individual state over time. Use a campaign when the work is scheduled, batch-oriented, or does not need a journey canvas.
2 · Treat entry as a contract
Name the event, audience, or schedule. Then settle identity, deduplication, re-entry, and exit rules before adding branches.
3 · Build the safe path
Every personalized message needs an eligible profile, approved content, a usable fallback, and a configured channel.
4 · Govern before send
Consent, suppression, frequency, quiet hours, and priority belong in the design review, not the launch-day checklist.
5 · Separate two kinds of proof
Operational evidence proves that entry, qualification, and delivery worked. Outcome evidence shows whether the experience changed behavior.
6 · Design the stop button
Name the person who can pause the work, the signals that trigger a pause, and the recovery path before production activation.
If a reviewer cannot explain why a person entered, qualified, received, and exited, the design is not ready.
Best for: learning the operator sequence and reviewing a design without opening AJO.
What starts this?
Document the trigger, identity, deduplication, re-entry, and exit behavior.
Who must not receive it?
Make consent, suppression, contact policy, and conflict rules testable.
Can it be delivered?
Verify configuration, addressability, authentication, and deliverability ownership.
What happens when data is missing?
Proof personalization, locale handling, required tokens, and the fallback experience.
Why this experience?
Record eligibility, ranking, caps, placements, and the no-offer fallback.
Who pauses and recovers?
Name monitoring signals, a pause owner, rollback steps, and the incident handoff.
Best for: a cross-functional launch review. Each note should have one owner and one piece of evidence.
From signal to measurable experience
Read left to right. When a journey fails, find the first handoff that lacks evidence instead of debugging every AJO object at once.
- 01SignalEvent, audience qualification, API request, or schedule.
- 02EligibilityIdentity, profile state, consent, suppression, and contact policy.
- 03OrchestrationJourney or campaign logic, waits, conditions, re-entry, and exits.
- 04Decision + contentEligible experience, ranking, personalization, locale, and fallback.
- 05Channel deliveryEmail, SMS, push, web, in-app, code-based, or custom action.
- 06Feedback + measureDelivery status, success events, reports, experiments, and CJA handoff.
Consent + contact policyApplies before every delivery decision.
Proof + test profilesExercises the path without widening production eligibility.
Monitoring + rollbackKeeps the system controllable after activation.
Best for: architecture reviews, troubleshooting, and explaining ownership across data, orchestration, channel, and measurement teams.
Handwritten field notes selected.
Complete curriculum
Every AJO domain, ordered by dependency.
Filter by the work you own. Each module includes a concept map, operator guide, implementation checklist, lab, failure patterns, official references, and review questions.
01
55 min
AJO architecture & operating model
Place AJO on the AEP foundation. Separate profiles, audiences, orchestration, delivery, decisioning, and measurement ownership.
ArchitectureUse casesRolesGuardrailsSandboxes
02
75 min
Profiles, audiences & identity
Design the audience and identity contracts that determine who can enter, qualify, personalize, and receive.
ProfilesNamespacesAudiencesEnrichmentTest profiles
03
90 min
Events, data sources & custom actions
Model unitary and business events, external lookups, timeouts, payloads, authentication, and action responses.
EventsData sourcesCustom actionsContextAPIs
04
120 min
Journey orchestration
Build entry, conditions, waits, reads, reactions, exits, re-entry, supplemental IDs, schedules, and journey lifecycle safely.
CanvasConditionsWaitsRead audienceLifecycle
05
95 min
Campaigns & Campaign Orchestration
Choose API-triggered, scheduled, recurring, transactional, or brand-initiated batch orchestration with clear eligibility and execution semantics.
CampaignsSchedulesAPI-triggeredOrchestratedApprovals
06
135 min
Channel configuration & delivery
Configure and QA email, SMS, push, in-app, web, code-based experiences, direct mail, and landing pages.
EmailSMSPushIn-appWebCode-based
07
110 min
Content, personalization & AI
Create templates, fragments, dynamic content, multilingual variants, expressions, helper functions, and governed AI-assisted content.
TemplatesFragmentsPersonalizationLocalizationAI Assistant
08
100 min
Decisioning & offers
Design items, placements, eligibility rules, strategies, rankings, caps, fallbacks, policies, and channel surfaces.
ItemsEligibilityRankingPoliciesFallbacks
09
80 min
Consent, governance & conflict
Enforce consent and data policies, frequency rules, quiet hours, priority, deduplication, and conflict management before send.
ConsentPoliciesFrequencyPriorityQuiet hours
10
85 min
Testing, proofs & approvals
Use test profiles, proofs, seed lists, simulations, experiments, holdouts, approvals, and preflight evidence.
Test modeProofsExperimentsApprovalsPreflight
11
90 min
Reporting, experimentation & optimization
Read live and global reports, channel metrics, journey performance, experiment lift, operational health, and CJA handoffs.
Live reportsGlobal reportsExperimentsCJAKPIs
12
120 min
Administration, APIs & run operations
Operate permissions, packages, labels, schemas, datasets, APIs, monitoring, troubleshooting, releases, and incident handoffs.
PermissionsAPIsMonitoringTroubleshootingReleases
End-to-end scenario
Recover an abandoned cart without creating a contact-policy incident.
A purchase-intent event arrives with an identity. A journey checks the profile, consent, cart state, recent communications, and audience context. Decisioning selects the best eligible incentive. The channel renders personalized content, delivery feedback returns, and reporting separates orchestration health from business lift.
Build this launch in the simulatorEventEligibilityDecisionDeliveryMeasure
Interactive launch playground
Can this journey launch safely?
Configure the scenario, run the review, and inspect the exact handoffs that are ready, risky, or blocked. The simulator is deterministic and stores nothing on the server.
Waiting for your configuration
The review will score eight production contracts and produce a prioritized remediation plan.
Inside the paid pack
Learn, build, test, and run.
The curriculum is paired with reusable artifacts so the work survives beyond a course session.
Operator modules
Foundation through production operations, with official-source maintenance notes.
Hands-on labs
Journey entry, actions, channels, personalization, decisioning, consent, proofs, reporting, and recovery.
Reusable templates
Event contract, journey brief, channel checklist, launch gate, incident pack, and measurement plan.
Interview questions
Role-aware answers from foundations through architecture and troubleshooting.
Practice questions
Scenario drills and a separate timed mock with rationale and domain diagnostics.
Launch workbench
The expanded simulator with saved scenarios, evidence export, and failure injection.
Portable artifact
AJO launch review board
Keep the core contracts visible during design reviews, proofing, go-live, and incident response.
Download the SVG boardShared language
Terms that prevent expensive misunderstandings.
Journey
A stateful orchestration that reacts to events, audiences, conditions, time, and actions for an individual.
Campaign
A scheduled or API-triggered communication execution; use it when a journey canvas is unnecessary.
Action
A native channel delivery or custom outbound call performed from a journey.
Surface
The channel and placement address where a decisioned experience can render.
Decision policy
The selection logic that narrows, ranks, and returns eligible items for a placement.
Test profile
A marked profile used to exercise journeys and messages without opening production eligibility.
Proof
A rendered message sent to reviewers so content, personalization, and configuration can be checked.
Conflict rule
A policy that arbitrates competing communications using priority, caps, and related constraints.
Primary sources
Use the academy for judgment. Use Adobe for current capability truth.
Official documentation
AJO complete guide
The maintained source for capabilities, setup, guardrails, channels, orchestration, governance, and releases.
Open Adobe guide Best first resourceWhat is Journey Optimizer?
Adobe's current product orientation, architecture frame, use cases, and licensing caveat.
Open orientation MaintenanceRelease notes
Validate availability, behavior changes, deprecations, and rollout timing before implementation.
Check current releaseIndividual license
$129 USD
One-time price for the permanent offline academy, private hosted 1.x access, curriculum corrections, and operator tools.
- Complete 12-domain AJO academy
- Interactive launch workbench
- 10 labs, 14 templates, 150 interview answers, and 100 practice questions
- Maintained official-reference map
Available in production
Operate AJO as a connected system.
Production purchase and delivery are available for $129 one-time. This review environment keeps checkout closed.
Review product detailsQuestions? support@binarycipher.devCommon questions
Clear scope before purchase.
Is this an Adobe certification course?+
No. It is independent operator education. It supports implementation and certification reasoning, but Adobe controls exam objectives, policies, names, and credentials.
Does “all topics” mean every changing screen and beta?+
No static course can promise every tenant-specific or pre-release screen. The pack covers the complete durable operating model and current documented capability families, then maps time-sensitive details to maintained Adobe sources and release notes.
Who is it for?+
Marketers, administrators, developers, campaign operations specialists, consultants, and architects who need a shared production model rather than isolated role training.
What is included with updates?+
The individual license includes the permanent downloaded edition plus corrective and curriculum updates within the hosted 1.x line. The reviewed license and support terms are included in the package and will also be displayed before checkout opens.
What are the license and support boundaries?+
One purchaser may use the pack for personal learning and their own internal or client implementation work, but may not share, resell, sublicense, or redistribute the pack or source assets. Email support covers delivery, access, corrections, and product defects; it does not include tenant implementation, consulting, or a response-time SLA.
What is the refund policy?+
The original purchaser may request a full refund within 14 calendar days of purchase by emailing support@binarycipher.dev from the purchase address and including the Gumroad order number. A timely, good-faith request that identifies the purchase is eligible; there is no minimum product-usage requirement. After refund, hosted access is revoked and the license to retained offline copies ends; delete those copies. Non-waivable consumer rights still apply.
Is checkout available now?+
Yes, on the production site. This review environment does not expose a purchase link.
A Binary Cipher product
From first event to last-mile evidence.
Independent of Adobe. Adobe Journey Optimizer and related marks belong to Adobe.