Binary CipherSeparate the contracts.
Place browser state, SDK configuration, datastream routing, service processing, and customer experience in distinct testable boundaries.
Available now · individual licenseWeb SDK
Web SDK
Master Pack
The Edge Collection Operator Academy.
Design, migrate, validate, and debug the browser-to-Adobe Edge contract—from configuration, consent, identity, XDM, and routing through personalization responses and downstream evidence. Then pressure-test the implementation in a local-only Payload Explorer.
One-time purchase · permanent offline edition · hosted 1.x updates
Start here in 15 minutes
Write the event contract before calling sendEvent.
- 01Name the business event, consent state, and expected proof.
- 02Choose xdm or data, identity, event type, and service route.
- 03Validate the request, Edge response, render, and downstream result.
Operator outcomes
Make every edge request explainable.
The pack trains the design choices and evidence behind reliable collection and personalization—not merely the clicks needed to publish a tag.
Construct valid intent.
Choose xdm or data intentionally, model event and identity semantics, and handle responses without accidental duplication.
Debug from evidence.
Inspect browser, Edge, routing, render, and destination proof before changing code or configuration.
Migrate with parity.
Inventory AppMeasurement and at.js behavior, measure meaningful differences, and preserve a tested rollback path.
Animated mental model
Collection is a request-response loop.
Browser context becomes a command. Consent gates the request. The datastream routes accepted data. Responses can drive personalization, while evidence from each stage feeds the next release decision.
Follow the edge path
2026 capability watch
Moving behavior, clearly labeled.
The durable curriculum stays stable while the source trail flags version, entitlement, propagation, routing, and browser-support boundaries.
alloy.js lifecycle
Version-specific commands and modules are checked against release notes; custom builds must retain required dependencies.
Datastream changes
Configuration changes can take time to propagate. Test the intended environment and preserve before-and-after evidence.
Dynamic routing
Dynamic rules are first-match. An explicit client override takes precedence and can bypass the dynamic rule path.
Downstream outcomes
Analytics, Target, AJO, CJA, RT-CDP, Platform, and event forwarding depend on entitlement and datastream configuration.
Complete curriculum
Every durable Web SDK domain, ordered by dependency.
Filter by the work you own. Every module combines a mental model, operator workflow, release checks, failure patterns, a scenario, interview reasoning, and maintained official references.
Showing all 15 domains
01
60 min
Architecture & operating model
Place alloy.js, Tags, Edge Network, datastreams, and licensed Adobe services in one browser-to-outcome operating model.
alloy.jsEdge NetworkDatastreamsOwnership
02
75 min
Measurement design & event taxonomy
Turn business decisions into governed page, interaction, commerce, identity, consent, and decisioning event contracts.
Event taxonomyData layereventTypeAcceptance
03
110 min
XDM & payload contracts
Choose xdm or data intentionally; model hierarchy, arrays, required values, event meaning, payload size, and schema evolution.
xdmdataSchemas64 KB
04
90 min
Datastreams & environments
Keep development, staging, and production routing explicit across sandboxes, datasets, report suites, properties, and enabled services.
EnvironmentsServicesPropagationAudit
05
85 min
Installation & library lifecycle
Compare the Tags extension, Adobe CDN, and NPM approaches; operate asynchronous base code, instances, versions, CSP, and custom builds.
TagsCDNNPMVersioning
06
100 min
Tags implementation engineering
Build variable data elements, ordered rules, Update Variable and Send Event actions, libraries, and publishing evidence.
VariablesRulesLibrariesPublishing
07
100 min
SDK configuration & context
Operate configure, orgId, datastreamId, edgeDomain, context collection, click collection, and onBeforeEventSend safely.
configureContextClicksCallbacks
08
120 min
Event collection patterns
Implement sendEvent, promises, responses, page and SPA views, links, forms, commerce, unloading, and duplicate control.
sendEventCommerceSPAResponses
09
115 min
Identity operations
Design ECID, identityMap, primary identity, authenticated transitions, FPID, cross-domain sharing, and legacy ID migration.
ECIDidentityMapFPIDLogin state
10
110 min
Consent, privacy & governance
Connect defaultConsent and setConsent to a CMP, model pending/in/out behavior, minimize fields, and preserve audit evidence.
CMPsetConsentMinimizationGovernance
11
95 min
Data Prep & transformation
Transform legacy data-layer values into XDM, test arrays and required targets, and protect intended identityMap behavior.
MappingCalculated fieldsArraysFixtures
12
105 min
Edge routing & service activation
Choose static datastreams, client overrides, or dynamic first-match rules and prove the exact dataset and service route.
OverridesDynamic rulesFallbackServices
13
125 min
Personalization lifecycle
Request scopes and surfaces, render propositions once, measure display/interact evidence, and operate page and SPA timing.
PropositionsSurfacesRenderingDisplay events
14
135 min
Solution integration & migration
Connect Platform, Analytics, Target, AJO, RT-CDP, CJA, and event forwarding while migrating AppMeasurement and at.js with parity.
AnalyticsTargetAJOMigration
15
130 min
Validation & production operations
Use Debugger, Assurance, monitoring hooks, network evidence, rollout, rollback, incident triage, performance, and release controls.
DebuggerAssuranceCSPRecovery
End-to-end scenario
Collect a purchase and return the right experience once.
A consented purchase event carries valid XDM, a stable authenticated identity, and a unique transaction ID. The correct datastream routes it to licensed services, the response is handled safely, the visitor does not receive an obsolete offer, and operators prove browser, Edge, and downstream results without assuming exactly-once delivery.
Pressure-test this requestBrowser statesendEventConsent gateDatastream routeEvidence
Interactive Web SDK Payload Explorer
Will this edge event behave as intended?
Configure a synthetic event and run a deterministic readiness review. The simulator checks payload, identity, consent, routing, personalization, and evidence contracts. It sends nothing to Adobe or any third party.
EDGE CONTRACT / 01Choose a scenario, then run the review.
You will get a scored verdict, route trace, synthetic payload preview, and prioritized evidence list.
Pack contents
A working system, not a folder of slides.
The validated 1.0 release supports learning, implementation planning, interview preparation, launch review, and incident response. The counts below match the completed downloadable and hosted academy.
Domain playbooks
Beginner-to-advanced guides organized around production dependencies.
Hands-on labs
Payload, Tags, identity, consent, routing, personalization, migration, and debugging scenarios.
Operator templates
Event contracts, environment matrices, mapping sheets, migration ledgers, QA checks, and runbooks.
Interview questions
Scenario answers that test reasoning across product and team boundaries.
Practice questions
Domain-weighted review with explanations and official-source follow-through.
Payload Explorer
A deterministic edge-contract simulator for design reviews, debugging practice, and stakeholder walkthroughs.
Free preview artifact
Edge Request Contract Board
Use the one-page board to connect browser intent, consent, payload meaning, identity, datastream route, response behavior, downstream proof, and recovery ownership.
Download the boardMaintained source trail
Learn the model. Verify the moving parts.
The pack teaches durable reasoning and points time-sensitive limits, interfaces, and service behavior back to maintained Adobe documentation.
Core commands and payloads5 sources
Datastreams and Tags5 sources
Identity, consent and personalization5 sources
Shared language
Terms and boundaries teams routinely blur.
Knowing the nouns is not enough. Operators must also know which neighboring service owns each decision.
Web SDK
Adobe’s browser JavaScript SDK for sending experience data to Edge Network and receiving supported Edge responses.
Datastream
The server-side routing configuration that selects datasets and enabled Adobe services for an Edge request.
xdm
The schema-conformant portion of a Web SDK event used by Experience Platform and Platform-native applications.
data
A non-XDM event payload consumed only by a configured service or Data Prep mapping; otherwise its properties can be lost.
identityMap
A map of identity namespaces to descriptor arrays carrying IDs, authentication state, and primary status.
Proposition
A decision response item whose rendering and display or interaction evidence must be handled deliberately.
Default consent
The initial collection gate configured before consent is resolved and communicated through setConsent.
Edge evidence
The linked proof across browser command, request, response, routing, render behavior, and downstream result.
xdm ≠ data
xdm follows an Experience Platform schema. data requires a configured consumer or Data Prep mapping or its properties can be discarded.
Web SDK ≠ datastream
The browser SDK constructs and sends the request. The datastream selects server-side datasets and licensed Adobe services.
ECID ≠ authenticated person
A device identity supports continuity but does not prove a verified login or replace an intentionally modeled person namespace.
Consent gate ≠ CMP
Web SDK can enforce collection state, but the site still owns CMP integration, purpose decisions, and consent-change hooks.
Proposition response ≠ exposure
A fetched proposition is not evidence of a rendered experience; display and interaction events complete the measurement contract.
Browser 2xx ≠ downstream success
A request can be accepted while routing, mapping, dataset, report-suite, rendering, or service processing still diverges.
Individual license
$129 USD · one time
- Permanent downloaded 1.0 edition
- Hosted corrective and curriculum updates through 1.x
- Individual-use operator templates; no redistribution or resale
- Independent education; no Adobe software or exam voucher
Checkout open
Own the edge contract.
Secure checkout and delivery are handled by the configured commerce provider.
Get the pack for $129Questions? support@binarycipher.devCommon questions
Clear scope before purchase.
Does this cover all durable Web SDK topics?+
It covers architecture, event design, xdm and data payloads, environments, installation, Tags, configure and sendEvent, pages and SPAs, commerce, identity, consent, Data Prep, routing, personalization, solution integration, migration, security, debugging, and production operations. Version-specific and licensed features stay anchored to current Adobe documentation.
Is this an Adobe certification course?+
No. It is independent operator education. It supports implementation and certification reasoning, but Adobe controls product entitlements, exams, policies, names, and credentials.
Who is it for?+
Analytics implementers, web developers, administrators, privacy practitioners, Adobe solution operators, consultants, and architects who need one shared browser-to-Edge model.
What does the paid pack deliver?+
The completed release includes a versioned offline HTML academy for Gumroad delivery and a maintained hosted edition with customer-specific access and stable “latest online” lesson links. The manifest, license, support path, privacy headers, and hosted renderer are included and validated.
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. The reviewed terms are included in the package and will also be displayed before checkout opens.
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. Use the purchase link above to review the final terms and complete checkout.
A Binary Cipher product
From browser intent to downstream evidence.
Independent of Adobe. Adobe Experience Platform, Web SDK, and related marks belong to Adobe.