See what is measured across your digital estate.
Step 01
XDM schema
Review the scan-derived experience-event schema and deployment payload.
Select a scan to build its AEP design.
Analytics Migration Accelerator
A clear, evidence-led view of your digital measurement—plus a practical path forward.
See what is measured across your digital estate.
Focus on evidence, impact and business value.
Give delivery teams a clear, agreed direction.
What the accelerator helps you do
Understand analytics, consent, content and key customer interactions.
Surface missing, inconsistent and outdated measurement.
Compare evidence over time and focus attention where it is needed.
Create an agreed plan that delivery teams can use.
What you’ll receive
A clear view of what is in place today.
Evidence-backed opportunities for improvement.
Practical guidance for analytics and digital teams.
Work together with confidence
Your administrators decide who can work with your projects and resources.
Only the consultants you approve receive access to your organization.
Reviews, approvals and generated resources stay connected to your work.
Start with clarity
Tell us what you want to improve. We’ll review your request and get in touch.
New here? Share a few details to request your account.
Account requests are currently handled by your DataSea contact.
Request an account
Share a few business details. An administrator will review your request and contact you.
Do not include passwords, credentials, personal analytics data, or other sensitive information.
Authorized access
Access is available by invitation. If you need an account, return to the overview and submit a private access request.
Authorized access
Use the account invited by your administrator.
Current project
Select a project Choose a scan to follow its lifecycle.Organization workspace
Migration workstreams and their immutable scan history in the selected organization.
Open a project to start a scan or review its immutable snapshots, newest first.
Project records
Open the evidence, CMS handoff, implementation plans, and deployment records generated for projects you can access.
Select a project to focus the library.
Loading project artifacts…
Organization administration
Manage organization settings, people, private Adobe connections, retained learning, and controlled model configuration.
Organization administration
DataSea is the protected parent. Client organizations represent legal clients, never websites or domains.
Selected organization
Loading authorized organizations…
Organization controls
Approved web scope, named environments, scan defaults, and audit history for this organization.
An approved domain includes its true subdomains and folders. New Sites and scans remain blocked outside this list.
Choose an organization to view approved domains.
Maintain the organization’s named production, UAT, development, and other environments. Domain labels remain separate descriptive context.
No environments have been configured.
Organization workflow defaults never weaken approved-domain enforcement, per-scan acknowledgements, or platform safety controls.
At least one active approved domain is required before the first Site or scan. Model-heavy design always remains behind explicit findings approval. Existing evidence stays readable when a domain approval expires or is removed.
Domain approvals, expiry, removal, actor, and rationale remain traceable.
No settings changes recorded yet.
Assignments remain default-deny and can be limited to a project, exact Adobe connection, sandbox, capability, and expiry.
Evidence-led analytics discovery
Understand site capabilities and evaluate Adobe Analytics dimensions across page-load and interaction calls.
Review snapshot
Choose a completed scan to review its findings.
Approval gate
Select a completed scan to freeze the evidence baseline used for design.
Recommended before Design
Requirements help Design compare intended outcomes with observed Scan evidence.
Select a completed scan to continue.
Scan summary
Findings panel
Select any infobox to add it as context for the assistant.
Select a scan to load the site summary.
Analytics discovery
Unique analytics dimensions and parameters observed across collection calls.
| Select a scan to load dimensions. |
Page-load inspector
Review passive evidence from navigation start through the first page-view call.
Select a scan to load page evidence.
No page selected.
Choose a page to review its timing and analytics calls.
Interaction audit
Start with site-level coverage, investigate evidence-backed analytics issues, then inspect individual observations when needed.
Select a scan to load interaction coverage.
Coverage groups will appear here.
No analytics issues loaded.
Choose an issue to review its expectation and evidence.
Commerce journey evidence will appear here.
Select a scan to load interaction evidence.
No interaction patterns loaded.
Choose a pattern to review retained evidence.
Administrator archive · Findings v1
The prior spreadsheet and XDM review experience is retained here for administrators.
Choose a completed scan to review its captured evidence.
Grounded assistant
Ask where evidence was observed, why XDM is proposed, or request a draft design change such as removing a field group. Conversation and decisions are retained with this scan. Changes require administrator approval; this tool does not modify Adobe AEP.
Viewer access can review existing findings but cannot submit model queries.
Select a scan to review the proposed XDM design.
Select a scan to load findings.
Display limit reached; use the audit workbook for the full export.| No findings loaded. |
Governed implementation
Turn scan evidence into an approved XDM, Adobe Client Data Layer, dataset, datastream, and Data Collection implementation plan.
Import an Adobe Developer Console JSON file. Its credentials are available only to the signed-in uploader and the raw file is not retained.
No Adobe connections saved.
Step 01
Review the scan-derived experience-event schema and deployment payload.
Select a scan to build its AEP design.
Controlled Adobe utilities
Build repeatable implementation plans while preserving source assets and retaining rollback manifests.
Adobe Data Collection Replicator
Catalog an existing web property, define sites that share its data-layer contract, and create site-specific datasets, datastream checkpoints, and draft Data Collection properties.
Select the private Adobe connection and Web SDK property to catalog.
Web SDK validation, resource inventory, lineage, and copying constraints.
Catalog a source property to inspect its implementation assets.
Add sites that use the same component-driven data-layer design. A path prefix distinguishes locales or sections on one hostname.
| Site | URL and path | Locale / market | Environment URLs | Remove |
|---|
For a same-domain locale, use the canonical URL and a path such as /de/. Data Collection property domains use the hostname; the embed-code or routing decision remains a website implementation responsibility.
Preview every write and manual checkpoint before any Adobe resource is created.
Catalog a valid source and add at least one destination to build a plan.
Adobe Data View Replicator
Use Adobe’s native copy operation, verify Data View settings and reporting components, and optionally recreate validated calculated metrics for the copied Data View.
Select your private Adobe credential, its CJA connection, and the Data View to copy.
Review connection context, Data View settings, components, and optional calculated metrics.
Select and catalogue a source Data View.
The target remains in the source connection. Datasets and connection-level derived fields are not changed.
Preview the native copy, verification, optional metric writes, and rollback boundary.
Catalogue a source and configure the copy to build a plan.
Authorized scope
The scanner stays on approved hosts. Business-effect actions remain off unless an authorized UAT commerce journey is explicitly enabled below.
Controlled customization
Adjust specialist emphasis without bypassing validation, scan limits, governance gates, or publishing controls.
Governed model funding
Choose who can use client-funded or DataSea-funded models across their authorized projects and tasks, with visible limits and audit.
Funding sources
Credentials remain server-side. No secret can be viewed after submission.
Loading model connections…
People with access
Access follows the named user and connection across every project they are authorized to use in this organization.
No model grants loaded.
Project preferences
Choose a payer only from connections the user is already permitted to use. A preference never grants model access.
Attribution & audit
Funding, organization, project, user, model, tokens and outcome remain traceable.
No model use recorded.
Policy history
Who changed model access, what changed, and when.
No model-access changes recorded.
Personal settings
Manage your profile and private Adobe connections. Credentials remain available only to the user who uploaded them.
Uploader-only access
Analyze an Adobe Developer Console JSON to discover accessible sandboxes, then choose the connection scope before saving.
Your current role can view analytics designs but does not permit creating Adobe connections.
No Adobe connections saved for your account.
Retained learning
Review the value-pattern rules created from confirmed findings. Disabling a rule is reversible and does not change saved scan evidence.
Loading retained rules…
Identity Platform
Invite application users and control their role without granting Google Cloud IAM access.
Role checks are enforced by the API, not only by this interface.
Loading members…
Review public requests before creating an Identity Platform account.
No pending access requests.
Recover scans while preserving evidence and deliverables.
Loading archived scans…
Reusable rules remain inactive outside their source client until reviewed.
Loading learning proposals…
Invitations, role changes, suspensions and setup-link generation.
No access changes recorded yet.