Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
SIRJ keeps source records, normalized events, validation gates, and customer-visible proof connected so a revenue number never has to stand on confidence alone.
Lineage principles
The category can get noisy fast: hundreds of connectors, AI language, reporting claims, and pricing levers. SIRJ wins by making proof paths readable.
If SIRJ shows a revenue claim, the buyer should be able to follow it to the connected source, dashboard surface, report output, or trust control that supports it.
Dashboard previews, Ask Data answers, report exports, and integration visuals point back to source records, normalized event types, or deterministic metric definitions.
Reports and answers should only use records that pass tenant scope, connector health, supported metric, attribution, and disclosure checks before they reach a buyer-facing surface.
SIRJ is positioned around restraint: if a connector, metric, or source record cannot support a claim, the product should expose the gap instead of smoothing it over.
Deterministic route
Connected records, normalized events, attribution rules, dashboards, reports, and Ask Data answers all move through the same discipline: make the claim, show the source, validate the route, then let the buyer decide.
Claim-to-evidence proof map
This proof map is intentionally explicit. It prevents the site from sounding bigger than the product and keeps every major page attached to a verifiable role in the buyer journey.
| Surface | Claim | Evidence | Validation |
|---|---|---|---|
| Homepage | SIRJ is a revenue attribution platform, not a single landing page. | The homepage links into product, pricing, integrations, solutions, comparisons, security, and resources instead of keeping the buyer in one scroll. | route-manifest, homepage-platform-front-door-test |
| Platform overview | Source connections, normalization, dashboards, Ask Data, and reporting are one system. | Platform pillars are backed by integration catalog, event normalizers, dashboard generation, and Ask Data modules. | platform-pillars-lineage, site-map-route-coverage |
| Dashboards | SIRJ dashboards show the current revenue workspace only after connected source capability can support each surface. | The dashboards page maps readiness status, card eligibility, source health, recent activity, next-source guidance, and Ask Data prompts to dashboard generation and rendering modules. | dashboards-guide-validation, dashboards-page-render-test |
| AI dashboard builder | SIRJ drafts dashboard structure from connected source capability before visual layout. | The AI dashboard builder page explains card eligibility, metric definitions, source readiness, next-source gaps, and cited proof paths before generated dashboards become client-facing claims. | ai-dashboard-builder-route, dashboard-generation-lineage |
| Human review loop | SIRJ keeps AI-assisted dashboard and report output reviewable before client-facing claims go out. | The human-in-the-loop reporting page maps source-state checks, generated dashboard review, report approval, recipient visibility, and audit evidence to the public product surface. | human-review-route, reporting-review-lineage |
| Agency dashboard software | SIRJ frames agency dashboard software around client workspace scope, source readiness, card eligibility, and reporting handoff instead of a static KPI wall. | The agency-dashboard-software page maps client workspaces, dashboard surfaces, source requirements, agency operating views, reporting handoff, and validation standards to dashboards, client workspaces, integrations, reports, and data validation routes. | agency-dashboard-guide-validation, agency-dashboard-page-render-test |
| Marketing dashboard software | SIRJ frames marketing dashboard software around source coverage, card eligibility, graph surfaces, source health, and revenue proof instead of presentation-only dashboards. | The marketing-dashboard-software page maps source categories, dashboard cards, graph surfaces, template starts, source-health behavior, reporting handoff, and validation standards to integrations, dashboards, dashboard templates, reports, metric definitions, and data validation routes. | marketing-dashboard-guide-validation, marketing-dashboard-page-render-test |
| Dashboard templates | SIRJ templates start from buyer jobs and source requirements, not blank dashboard templates. | The dashboard templates page maps solution-specific board starts, required sources, proof rows, visible dashboard outcomes, and related routes to the dashboard generation and solution playbook modules. | dashboard-templates-guide-validation, dashboard-templates-page-render-test |
| Marketing analytics software | SIRJ frames marketing analytics software around source-backed revenue proof, attribution evidence, dashboard surfaces, and client-ready decisions instead of disconnected channel analysis. | The marketing-analytics-software page maps source categories, analytics questions, proof surfaces, validation workflow, missing-data states, and reporting handoff to integrations, attribution, dashboards, Ask Data, reports, metric definitions, and data validation routes. | marketing-analytics-guide-validation, marketing-analytics-page-render-test |
| Marketing ROI software | SIRJ frames marketing ROI software around source-backed spend, booked work, invoice, payment, attribution, and reporting evidence. | The marketing-roi-software page maps ROI questions, calculation boundaries, source requirements, attribution confidence, dashboard surfaces, report output, and unsupported states to revenue attribution, integrations, dashboards, Ask Data, reports, metric definitions, and data validation. | marketing-roi-guide-validation, marketing-roi-page-render-test |
| Revenue leak detection | SIRJ surfaces revenue leaks from source-backed gaps such as unworked leads, stale follow-up, unmatched ad spend, open revenue states, and disconnected sources. | The revenue-leak-detection page maps leak types, source evidence, user-visible alert surfaces, Ask Data behavior, human review holds, and workflow steps to client workspaces, connector health, notifications, attribution, and reports. | revenue-leak-guide-validation, revenue-leak-page-render-test |
| Stale estimate follow-up | SIRJ flags aging estimates, quotes, and lead-to-job paths from source-backed follow-up gaps before reports treat them as revenue. | The stale-estimate-follow-up page maps source evidence, quote and job states, owner routing, alert surfaces, Ask Data behavior, human review holds, and reporting boundaries to client workspaces, notifications, attribution, validation, and reports. | stale-estimate-follow-up-guide-validation, stale-estimate-follow-up-page-render-test |
| Proof-of-work client reporting | SIRJ turns source records, dashboard changes, reviewed AI output, weekly insights, report snapshots, and exports into client-facing proof of work. | The proof-of-work-client-reporting page maps report evidence, review decisions, supported and blocked claims, delivery history, export proof, and next proof gaps to reports, sample reports, human review, data lineage, and exports. | proof-of-work-reporting-guide-validation, proof-of-work-reporting-page-render-test |
| Connector health | SIRJ makes stale, setup-incomplete, failed, disconnected, and reauthorization-required sources visible before reports rely on them. | The connector-health page maps runtime health summaries, missing setup checks, sync cadence, sync run history, failure counts, and escaped provider errors to the operational modules that produce those states. | connector-health-guide-validation, connector-health-page-render-test |
| Connector QA lane | SIRJ makes Scale connector QA concrete by showing what source setup gets reviewed before reporting depends on it. | The connector QA page maps setup requirements, source health, selected resources, sync history, field expectations, unsupported states, and reviewer handoff to connector health and integration runtime modules. | connector-qa-guide-validation, connector-qa-page-render-test |
| Metric definitions | SIRJ explains how revenue attribution metrics are unlocked, calculated, compared, cited, and withheld when evidence is missing. | The metric-definitions page maps dashboard card eligibility, ad spend, attributed revenue, ROAS, cost per lead, campaign performance, source performance, form conversion, pipeline, Ask Data query specs, and report snapshots to runtime modules and tests. | metric-definitions-guide-validation, metric-definitions-page-render-test |
| Client workspaces | SIRJ gives agencies an account-level view across client workspaces without mixing client access or dashboard scope. | The client-workspaces page maps agency overview totals, visible-client filtering, workspace creation, invite roles, branding, weekly recipients, and report handoff to the runtime modules that enforce them. | client-workspaces-guide-validation, client-workspaces-page-render-test |
| Roles and permissions | SIRJ separates owner, analyst, and viewer access so agencies can share client proof without giving every user billing, integration, export, or deletion controls. | The roles-and-permissions page maps role abilities, client-scoped memberships, invitation states, workspace boundaries, export rights, and protected administration actions to the tenant and client-access modules that enforce them. | roles-permissions-guide-validation, roles-permissions-page-render-test |
| White-label reporting | SIRJ separates client branding from source-backed proof so white-label output does not become unsupported presentation polish. | The white-label reporting page maps client branding, dashboard mode, branded exports, scoped invitations, report handoff, and missing-data behavior to branding, reporting, client-access, and export modules. | white-label-reporting-guide-validation, white-label-reporting-page-render-test |
| Data retention and deletion | SIRJ separates tenant data export, raw-event retention, and scoped deletion jobs so governed buyers can review data exit and removal before rollout. | The data-retention-and-deletion page maps export package records, retention tables, deletion groups, permissions, client confirmation, rate limits, failed states, and audit evidence to compliance and runtime modules. | data-retention-deletion-guide-validation, data-retention-deletion-page-render-test |
| Webhooks and API ingestion | SIRJ treats webhook and API ingestion as a verified, tenant-scoped data path before source events can support reports or revenue claims. | The webhooks-and-api-ingestion page maps setup manifest callback URLs, webhook activation checks, signature verification, selected-resource rejection, raw payload storage, normalized events, rate limits, and sync run status to runtime modules and tests. | webhook-api-ingestion-guide-validation, webhook-api-ingestion-page-render-test |
| Sync observability and backfills | SIRJ makes scheduled syncs, manual syncs, webhook-triggered runs, retries, backfills, and stale-source states visible before reporting surfaces rely on connected data. | The sync-observability-and-backfills page maps first-sync defaults, backfill settings, due-sync orchestration, heartbeat processing, retry timing, sync state, run history, and health severity to integration orchestration, API runtime, and observability modules. | sync-observability-backfills-guide-validation, sync-observability-backfills-page-render-test |
| Notification delivery and recipients | SIRJ makes recipient configuration, weekly email delivery, failed sends, active anomaly alerts, due-send schedule checks, and notification history reviewable before automation reaches clients. | The notification-delivery-and-recipients page maps weekly recipient storage, email delivery records, sent and failed notifications, active anomaly alerts, Monday 7:00 timezone schedule checks, already-sent and not-due skips, rate limits, and tenant-scoped notification-center rows to delivery, notification, and API runtime modules. | notification-delivery-recipients-guide-validation, notification-delivery-recipients-page-render-test |
| Client invitations and access | SIRJ makes invite creation, pending invite review, token redaction, revocation, expiration, acceptance, and client-scoped membership creation visible before clients enter a workspace. | The client-invitations-and-access page maps dashboard team controls, invitation status records, invite role limits, generated accept links, token-hash redaction, invalid-token rejection, expiration checks, revocation rules, rate limits, and scoped membership creation to client-access, API runtime, auth, dashboard-state, and UI modules. | client-invitations-access-guide-validation, client-invitations-access-page-render-test |
| Account security and recovery | SIRJ explains email access, Google access, password recovery, reset links, session scope, and invitation acceptance before users enter protected reporting workspaces. | The account-security-and-recovery page maps signup, login, Google OAuth state, password reset actions, session hashing, JWT-compatible verification, HTTP-only cookies, and invite acceptance to the auth, session, client-access, and route modules that enforce those paths. | account-security-recovery-guide-validation, account-security-recovery-page-render-test |
| Account setup | SIRJ explains how selected plan and source context becomes a workspace entry point before buyers commit source data. | The account setup page maps plan intent, Google or email signup, login, invited access, trial state, first workspace routing, and source intent to auth, onboarding, and billing modules. | account-setup-guide-validation, account-setup-page-render-test |
| Rate limits and usage controls | SIRJ applies scoped usage controls before repeated requests can create duplicate sends, unsafe exports, runaway syncs, or noisy account actions. | The rate limits page maps account access, dashboard reads, Ask Data, integration management, syncs, webhooks, billing, report exports, weekly delivery, data exports, deletion, and retention jobs to the runtime controls and tests that stop blocked requests before sensitive work continues. | rate-limits-usage-controls-guide-validation, rate-limits-usage-controls-page-render-test |
| Onboarding | SIRJ shows the path from selected plan and source to first synced dashboard instead of leaving setup hidden after account creation. | The onboarding page maps signup plan/source intent, client workspace creation, integration setup requirements, first sync, dashboard readiness, and weekly reporting handoff to the runtime modules that enforce those states. | onboarding-guide-validation, onboarding-page-render-test |
| Setup guarantee | SIRJ uses onboarding risk reversal to reduce purchase hesitation without promising unsupported revenue outcomes. | The setup guarantee page maps plan fit, source readiness, implementation responsibilities, first dashboard expectations, refund boundaries, and support handoff to onboarding and pricing routes. | setup-guarantee-guide-validation, setup-guarantee-page-render-test |
| Reporting architecture review | SIRJ gives Scale buyers a concrete operations review instead of treating premium pricing as vague support. | The reporting architecture review page maps portfolio setup, source readiness, connector QA, report cadence, evidence gaps, and expansion guidance to dashboard, report, and integration proof paths. | reporting-architecture-guide-validation, reporting-architecture-page-render-test |
| Revenue attribution guide | SIRJ can define revenue attribution in the same source-backed language the product uses. | The guide answers category questions, explains the source-to-revenue workflow, names common reporting failures, and routes readers into integrations, pricing, and proof pages. | revenue-attribution-guide-validation, revenue-attribution-render-test |
| Marketing attribution software | SIRJ frames marketing attribution software around explainable revenue proof for agencies that need source-backed client answers. | The marketing-attribution-software page maps category criteria, source coverage, match rules, no-match behavior, proof surfaces, validation workflow, and fit boundaries to the attribution engine, integration pages, reports, and methodology routes. | marketing-attribution-guide-validation, marketing-attribution-page-render-test |
| Marketing reporting software | SIRJ frames marketing reporting software around imported source records, dashboard proof, weekly summaries, and revenue-backed client outputs. | The marketing-reporting-software page maps source categories, dashboard and graph surfaces, report outputs, weekly delivery, missing-data states, and validation workflow to integration pages, dashboards, reports, metric definitions, and data validation routes. | marketing-reporting-guide-validation, marketing-reporting-page-render-test |
| Lead-to-revenue matching | SIRJ exposes the matching engine that connects demand events to downstream revenue proof. | The matching page maps spend-to-lead, lead-to-deal, deal-to-payment, confidence, payment precedence, and statistical context to the runtime attribution modules and tests. | lead-to-revenue-guide-validation, lead-to-revenue-render-test |
| Attribution methodology | SIRJ explains how spend, leads, deals, and payments become attributed revenue before dashboards or reports use the result. | The attribution-methodology page maps 7-day spend windows, campaign and source matching, entity id, email, phone, job, appointment, invoice, and payment identifiers, confidence scores, deterministic revenue summaries, and statistical allocation to runtime modules and tests. | attribution-methodology-guide-validation, attribution-methodology-page-render-test |
| Ask Data | SIRJ answers plain-English revenue questions only when scoped dashboard data can support the answer. | The Ask Data page maps supported question types, query-spec parsing, tenant-scope checks, metric citations, chart rows, cache behavior, and unsupported responses back to the runtime modules and tests that enforce them. | ask-data-guide-validation, ask-data-render-test |
| Data routing and validation | SIRJ routes data deterministically from connector record to user-visible answer. | The routing guide names the ingestion, normalization, scope, metric, and unsupported-data checkpoints that protect dashboards, exports, and Ask Data from confident but unproven claims. | data-routing-guide-validation, data-routing-render-test |
| Data validation | SIRJ validates source records before they become dashboard cards, attributed revenue, Ask Data answers, weekly insights, or reports. | The data-validation page maps connector setup checks, normalized schema rules, tenant scope, metric eligibility, attribution evidence, stale-source handling, and unsupported-answer behavior to runtime modules and tests. | data-validation-guide-validation, data-validation-render-test |
| Agency reporting software | SIRJ positions agency reporting around source-backed revenue proof rather than chart assembly. | The agency-reporting-software guide maps category decision criteria, client-visible proof surfaces, implementation workflow, and validation standards to dashboards, integrations, reports, white-label exports, weekly insights, and attribution pages. | agency-reporting-guide-validation, agency-reporting-page-render-test |
| Client reporting software | SIRJ frames client reporting software around source-backed report proof rather than polished but fragile templates. | The client-reporting-software guide maps category decision criteria, report surfaces, weekly delivery, white-label output, client workspace scope, missing-data behavior, and export auditability to reports, sample report, weekly insights, client workspaces, and data validation pages. | client-reporting-guide-validation, client-reporting-page-render-test |
| Disclosures | SIRJ makes public product boundaries visible before buyers create an account. | The disclosures page explains attribution completeness, AI-assisted answers, integration dependencies, billing terms, roadmap language, privacy handling, and security links in plain public copy. | disclosure-guide-validation, disclosure-page-render-test |
| Reports and exports | SIRJ turns dashboards into client-ready reports, weekly insights, and exportable proof. | The reports page maps dashboard snapshots, source breakdowns, campaign performance, recommendations, weekly email delivery, PDF exports, and audit records to the product modules that produce them. | reports-guide-validation, reports-page-render-test |
| Weekly insights and alerts | SIRJ turns dashboard evidence into recurring insight and alert review before client communication goes out. | The weekly insights page maps insight generation, anomaly alerts, recommendations, recipient timing, delivery history, and failed-send states to insights, notifications, weekly delivery, and reporting modules. | weekly-insights-guide-validation, weekly-insights-page-render-test |
| Sample report | SIRJ shows the client-facing proof artifact instead of only describing reporting in abstract terms. | The sample report page maps snapshot metrics, source breakdowns, campaign rows, recommendations, attention items, and report lineage to report generation and export UI modules. | sample-report-guide-validation, sample-report-page-render-test |
| Exports and destinations | SIRJ explains how reports and tenant data leave the workspace without blurring exports, compliance packages, and Enterprise destinations. | The exports page maps PDF report exports, report history, tenant data exports, retention workflows, destination boundaries, and Enterprise planning to export and compliance modules. | exports-guide-validation, exports-page-render-test |
| Pricing | Growth is the highest-value default, with Starter, Scale, and Enterprise serving different buying moments. | Plan objects, buyer-fit rules, public plan questions, and validation checks support the pricing page. | pricing-strategy-validation, pricing-page-render-test |
| Plan comparison | SIRJ explains plan differences by operating complexity so buyers can choose without decoding a dense feature grid. | The pricing comparison page maps plan fit, client workspace volume, reporting cadence, integration coverage, onboarding depth, connector QA, governance needs, and upgrade triggers to pricing plans and rollout pages. | plan-comparison-guide-validation, pricing-comparison-page-render-test |
| Implementation timeline | SIRJ shows what happens after purchase so setup effort is explicit before a buyer starts. | The implementation timeline page maps plan selection, account setup, first workspace, first connector, dashboard readiness, reporting handoff, and expansion support to onboarding and integration setup modules. | implementation-timeline-guide-validation, implementation-timeline-page-render-test |
| ROI calculator | SIRJ gives buyers a source-backed way to compare reporting labor cost against platform investment. | The ROI calculator page maps reporting hours, client workspace volume, manual QA, disputed numbers, invoice-backed proof gaps, annualized savings, and plan-fit routing to pricing and reporting proof pages. | roi-calculator-guide-validation, roi-calculator-page-render-test |
| Billing and plan limits | SIRJ explains the commercial mechanics behind signup, trial access, checkout, cancellation, feature access, and workspace limits. | The billing guide maps signup trial creation, account-scoped subscriptions, Stripe checkout, billing portal sessions, subscription usability, feature gates, client workspace limits, and integration limits to runtime modules and tests. | billing-guide-validation, billing-page-render-test |
| Enterprise rollout | SIRJ gives governed buyers a separate rollout path for SSO, security review, retention, procurement, private connectors, and executive reporting. | The Enterprise page maps governance requirements, custom workspace volume, SSO support, security review, custom retention, private connector planning, procurement support, and rollout sequencing to trust and compliance pages. | enterprise-guide-validation, enterprise-page-render-test |
| Integrations | Each connector explains imported data and how users see that data in a graph or revenue proof view. | Integration objects include imports, source fields, sample rows, visualization rows, buyer questions, and event-type lineage. | integration-visualization-validation, integration-detail-render-test |
| Marketing data integration software | SIRJ frames marketing data integration software around imported records, normalization, validation, connector health, and revenue-proof surfaces instead of connector-count theater. | The marketing-data-integration-software page maps source categories, imported fields, normalizers, validation gates, connector health, dashboard outputs, reporting handoff, and custom connector scope to integrations, categories, data routing, data validation, dashboards, reports, and connector health routes. | marketing-data-integration-guide-validation, marketing-data-integration-page-render-test |
| Procurement checklist | SIRJ gives governed buyers a checklist for security, access, data scope, integrations, retention, exports, billing, legal review, rollout approval, and evidence gaps. | The procurement-checklist page maps reviewer questions, required proof, evidence routes, approval workflow, and review standards to Trust Center, security, client workspaces, integrations, source coverage, exports, billing, privacy, terms, Enterprise rollout, and data validation pages. | procurement-checklist-guide-validation, procurement-checklist-page-render-test |
| Audit log and compliance | SIRJ explains which audit actions, export records, deletion jobs, retention boundaries, and failed output states reviewers can inspect before rollout. | The audit-log-and-compliance page maps action rows, compliance packages, workflow, and proof standards to audit actions, tenant data tables, report export history, Trust Center, exports, security, privacy, and Enterprise routes. | audit-log-compliance-guide-validation, audit-log-compliance-page-render-test |
| Source coverage matrix | SIRJ exposes source coverage as records, visible surfaces, readiness checks, and unsupported states rather than a simple provider list. | The source-coverage page maps source categories, dashboard surfaces, readiness checks, workflow, proof standards, and FAQs to integrations, data routing, dashboards, reports, Ask Data, connector health, and custom connector planning. | source-coverage-guide-validation, source-coverage-page-render-test |
| Connector setup and permissions | SIRJ explains authorization method, required permissions, selected resources, setup controls, credential handling, and readiness states before a source is used for reporting. | The connector-setup-and-permissions page maps OAuth, API key entry, resource selection, webhook callbacks, pipeline mapping, permission groups, workflow, proof standards, and FAQs to the setup manifest, provider resource listing, orchestration, security, connector health, and data validation routes. | connector-setup-guide-validation, connector-setup-page-render-test |
| Marketing ETL software | SIRJ frames marketing ETL software around extraction, normalization, transformation, validation, and loading records into revenue-proof surfaces. | The marketing-etl-software page maps ETL stages, transform boundaries, validation gates, connector health, unsupported fields, dashboard/report destinations, and warehouse-fit boundaries to data routing, integrations, validation, exports, dashboards, and reports. | marketing-etl-guide-validation, marketing-etl-page-render-test |
| Marketing intelligence software | SIRJ frames marketing intelligence software around source-backed answers, dashboard context, attribution evidence, recommendations, and reporting handoff. | The marketing-intelligence-software page maps buyer intelligence questions, source coverage, freshness, Ask Data citations, dashboard surfaces, attribution evidence, recommendation boundaries, report handoff, and broad-platform fit to integrations, analytics, Ask Data, dashboards, data validation, performance management, reports, and comparisons. | marketing-intelligence-guide-validation, marketing-intelligence-page-render-test |
| Marketing performance management software | SIRJ frames marketing performance management software around source-backed KPIs, review cadence, alerts, decisions, recommendations, and reporting handoff. | The marketing-performance-management-software page maps KPI readiness, source health, performance review rituals, account-team decisions, alerts, client recommendations, dashboards, weekly insights, reports, and unsupported-performance states to analytics, dashboards, data validation, weekly insights, reports, and exports. | marketing-performance-management-guide-validation, marketing-performance-management-page-render-test |
| Custom connectors | SIRJ gives Enterprise buyers a scoped path for private sources that are not in the public connector catalog. | The custom connector page maps source purpose, authentication, available records, resource selection, validation gates, attribution role, connector health, and pilot rollout to runtime integration modules and tests. | custom-connectors-guide-validation, custom-connectors-render-test |
| Integration categories | SIRJ groups connector pages by the revenue-path job each category performs. | Integration category pages map catalog categories to buyer needs, required data signals, dashboard proof, validation workflow, and connector detail routes. | integration-category-validation, integration-category-render-test |
| Solutions | SIRJ has buyer-specific playbooks for the teams most likely to buy revenue attribution. | Each solution defines buyer trigger, recommended plan, stack, proof rows, workflow, objections, and source lineage. | solution-playbook-validation, solution-render-test |
| Comparisons | SIRJ is positioned against Funnel, Whatagraph, and Improvado with buyer-fit nuance, not blanket competitor bashing. | Comparison pages carry source URLs, pricing URLs, source snapshots, criteria rows, objections, proof paths, and positioning moves. | comparison-source-validation, comparison-render-test |
| Resources | SIRJ gives buyers a routed resource hub instead of forcing every objection through the homepage. | The resources page groups product, pricing, integrations, comparisons, trust, proof, and setup paths into buyer evaluation collections with related route links. | resource-hub-validation, resources-page-render-test |
| Site map | SIRJ exposes the full public platform map so buyers and crawlers can discover more than one page. | The site map page renders route sections, footer groups, and the route manifest so product, pricing, integrations, solutions, comparisons, trust, legal, login, and signup routes remain findable. | site-map-guide-validation, site-map-render-test |
| Trust Center | SIRJ groups security, lineage, access, compliance, legal, and rollout evidence for buyers who need procurement confidence. | The Trust Center page maps procurement review, security posture, source lineage, roles, invitations, exports, retention, deletion, legal documents, and Enterprise rollout routes into one evaluation hub. | trust-center-guide-validation, trust-center-page-render-test |
| Security | Trust is a conversion feature for revenue attribution. | Security explains source lineage, stale-data flags, tenant-aware access, export/deletion paths, and deterministic reporting restraint. | base-page-schema, site-map-route-coverage |
| Data lineage | SIRJ keeps product claims connected to source records, validation gates, and customer-visible proof. | This page exposes the source paths, validation gates, proof surfaces, and buyer-facing routes that support revenue attribution claims. | data-lineage-proof-map-validation, data-lineage-render-test |
Validation gates
These checks are boring in the best possible way. They keep the site indexable, the integration pages useful, the pricing page decisive, and product claims tied to evidence.
Every public product, integration, pricing, comparison, solution, procurement, and trust page must be present in getMarketingRoutes, the XML sitemap, and the public site map.
Every integration page needs imports, buyer questions, sample rows, visualization rows, source fields, and visualization lineage.
The data-routing guide must explain ingestion, normalization, tenant scope, metric computation, unsupported-data handling, and the proof surfaces those records feed.
The data-validation page must explain connector setup checks, schema normalization, tenant scope, metric eligibility, attribution evidence, stale-source behavior, and unsupported answer states.
The custom-connectors page must explain private source qualification, auth and resource review, available records, validation gates, revenue attribution role, pilot rollout, and unsupported states.
The Ask Data page must explain supported question types, query-spec validation, citations, chart rows, caching, and unsupported-answer behavior before AI-assisted answers are trusted.
The dashboards page must explain readiness status, card unlock rules, source health, recent activity, next-source guidance, and Ask Data prompts before dashboard claims appear complete.
The agency-dashboard-software page must explain client workspaces, source readiness, dashboard card eligibility, agency overview, reporting handoff, missing-data behavior, and access boundaries.
The marketing-dashboard-software page must explain source coverage, card eligibility, graph surfaces, dashboard templates, source health, revenue proof, missing-data behavior, and reporting handoff.
The marketing-analytics-software page must explain source coverage, attribution evidence, dashboard surfaces, cohort and segment questions, revenue proof, missing-data behavior, and reporting handoff.
The marketing-roi-software page must explain spend sources, lead quality, booked work, invoices, collected payments, attribution confidence, ROI calculation boundaries, reporting handoff, and unsupported revenue states.
The revenue-leak-detection page must explain unworked leads, stale follow-up, unmatched ad spend, open invoices, disconnected sources, alerts, review holds, and unsupported leak states.
The stale-estimate-follow-up page must explain stale estimates, quotes, calls, forms, CRM or job state, follow-up owner, alerts, held review states, and unsupported revenue outcomes.
The proof-of-work-client-reporting page must explain source evidence, dashboard changes, AI review decisions, blocked claims, report snapshots, exports, and next proof gaps.
The connector-health page must explain health status, missing setup checks, stale-data state, sync cadence, recent sync runs, failure severity, and reauthorization needs.
The metric-definitions page must explain card eligibility, formula inputs, date scope, source filters, computed Ask Data metrics, report extraction, and unsupported metric behavior.
The attribution-methodology page must explain spend-to-lead windows, downstream entity matching, confidence scores, deterministic revenue chaining, payment precedence, statistical allocation, and no-match behavior.
The client-workspaces page must explain agency overview metrics, visible-client scope, workspace creation limits, invitations, white-label branding, and weekly reporting handoff.
The roles-and-permissions page must explain owner, analyst, and viewer roles; client-scoped memberships; invitations; export limits; administration boundaries; deletion controls; and the checks that stop users from seeing the wrong client workspace.
The client-invitations-and-access page must explain pending, accepted, revoked, and expired invitation states; analyst and viewer invite roles; one-time invite links; token-hash redaction; invalid-token rejection; expiration; revocation; dashboard team controls; rate limits; and client-scoped membership creation.
The account-security-and-recovery page must explain email signup, email login, Google OAuth, signed state, password recovery, reset-link handling, scoped sessions, invitation acceptance, and redacted auth responses.
The rate-limits-and-usage-controls page must explain throttled action categories, user-visible blocked states, tenant-scoped usage boundaries, retry-safe workflows, and the adjacent product routes that show billing, integrations, exports, delivery, and account access.
The onboarding page must explain selected plan and source context, workspace creation, first connector setup, setup requirements, first sync, dashboard readiness, and reporting handoff.
Pricing must validate the Growth default, annual and monthly options, Enterprise lane, public plan questions, and buyer-fit rules.
The billing-and-plan-limits page must explain trial creation, account-scoped subscriptions, checkout, billing portal, workspace limits, feature gates, cancellation, and expired-trial behavior.
Integration category pages must group connectors by buyer job, show data signals, dashboard proof, validation workflow, and links to every connector in the category.
The marketing-data-integration-software page must explain source coverage, imported fields, normalization, tenant scope, validation gates, dashboard surfaces, connector health, custom sources, and reporting handoff.
The procurement-checklist page must map security review, access model, data scope, integrations, retention, exports, billing, legal review, rollout approval, and open evidence gaps to public proof routes.
The audit-log-and-compliance page must explain audit actions, report export evidence, tenant data export packages, deletion jobs, retention boundaries, failed output states, and reviewer routes.
The data-retention-and-deletion page must explain tenant data export, raw-event retention tables, default retention window, scoped deletion jobs, confirmation checks, rate limits, audit evidence, failed job states, and custom retention boundaries.
The webhooks-and-api-ingestion page must explain tenant-scoped callback URLs, webhook setup requirements, signature verification, selected-resource checks, raw payload normalization, rate limits, sync observability, and failed ingestion states.
The sync-observability-and-backfills page must explain scheduled syncs, manual syncs, webhook-triggered runs, default backfills, retry timing, heartbeat processing, stale-source detection, and sync-run history.
The notification-delivery-and-recipients page must explain weekly recipient configuration, email delivery records, sent and failed states, active anomaly alerts, due-send timezone windows, duplicate-send skips, rate limits, and tenant-scoped notification history.
The source-coverage page must map source categories to imported records, visible surfaces, validation behavior, dashboard requirements, readiness checks, and missing-evidence states.
The connector-setup-and-permissions page must explain OAuth, API key setup, required permissions, selected resources, webhook callbacks, credential handling, setup controls, readiness states, and unsupported-source behavior.
The marketing-etl-software page must explain extraction, normalization, transformation, validation gates, load destinations, connector health, unsupported fields, warehouse boundaries, and reporting handoff.
The marketing-intelligence-software page must explain source coverage, data freshness, attribution evidence, KPI support, Ask Data answers, dashboard surfaces, recommendations, fit boundaries, and reporting handoff.
The marketing-performance-management-software page must explain KPI readiness, source health, review cadence, decision workflows, alerts, client recommendations, reporting handoff, and unsupported-performance states.
The disclosures page must explain attribution limits, AI-assisted answers, third-party integrations, billing, roadmap language, privacy, and security in public buyer language.
The reports page must connect dashboards, weekly insights, white-label exports, report snapshots, recommendations, and audit logs to source-backed buyer proof.
The agency-reporting-software page must explain category requirements, stock reporting gaps, source-backed proof surfaces, workflow, validation gates, and plan-fit routes.
The marketing-attribution-software page must explain attribution source coverage, match rules, confidence, no-match behavior, revenue proof surfaces, validation workflow, and buyer-fit routes.
The marketing-reporting-software page must explain imported marketing sources, dashboard and graph surfaces, weekly reporting, report exports, missing-data behavior, validation workflow, and buyer-fit routes.
The client-reporting-software page must explain report snapshot proof, weekly delivery, white-label output, client workspace scope, missing-data behavior, export auditability, and plan-fit routes.
Each solution needs a buyer, trigger, recommended plan, proof rows, workflow, objections, and source-backed revenue path.
Each alternative page needs live-source URLs, source snapshots, criteria rows, objections, proof paths, and clear buyer-fit boundaries.
Ready when the numbers need to hold up
Every claim gets a visible receipt before the buyer ever creates an account.