Getting Started

How Diagnostics Works

Updated July 1, 2026 Diagnostics is no longer the only public CTA, but it remains the operational boundary between content discovery and implementation review.

When to Use Diagnostics

Use diagnostics when you have moved beyond a simple single-page preview. Typical triggers are recurring schedules, custom field requirements, many URLs, multiple retailers, or a target that is not already modeled by a safe public template.

What Diagnostics Collects

The form captures the representative target URL, fields required, estimated monthly volume, desired frequency, and any notes that affect provider choice or rollout complexity.

  • Representative URL or domain
  • Field list and data shape
  • Volume and schedule expectations
  • Context that changes risk or implementation cost

How Results Are Used

Diagnostics results become a lead record in the backend and drive the first implementation decision: prebuilt dataset, scoped custom collector, or a managed service recommendation.