Public source universe and full evidence ledger
"Transparency score is a six-item disclosure count: sample, population, data period, metric definition, methodology and accessible primary source. It is not a quality ranking for technical documentation."
Source ID,Original organisation,Source title,Direct URL,Exact source location,Publication / update / access date,Data-collection period,Sample size,Population,Geography,Industry / company-size scope,Exact claim or data point,Numerator,Denominator,Start event / end event,Methodology,Inclusion / exclusion rules,Known limitations / commercial or selection bias,Transparency score 0-6,Recommended IVRIS use
S01,Salesforce,Set Up Web-to-Lead,https://help.salesforce.com/s/articleView?id=sales.setting_up_web-to-lead.htm&language=en_US&type=5,Web-to-Lead setup and limits section,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce organisations using Web-to-Lead,Global product documentation,All Salesforce users; edition limits may vary,Web-to-Lead is a distinct intake mechanism with documented daily limits and setup dependencies.,N/A,N/A,Form post to Salesforce intake,Product documentation,Applies to Web-to-Lead only,Dynamic Salesforce Help rendering; limits and editions can change.,3,Contextual example
S02,Salesforce,Web-to-Case and Web-to-Lead Daily Limits Exceeded Due to Pending Request Queue,https://help.salesforce.com/s/articleView?id=000382807&language=en_US&type=1,Pending request queue limit and rejection behavior,2026-04-02,N/A,N/A,Salesforce Web-to-Lead and Web-to-Case requests,Global product documentation,All affected Salesforce organisations,"When the combined pending request queue reaches 50,000, additional requests are rejected rather than queued.",Rejected requests after limit,Requests submitted after the pending queue reaches limit,Inbound web request to intake decision,Product limit documentation,Combined Web-to-Lead and Web-to-Case pending queue,Rare boundary condition; administrative alerts and edition details should be verified in-org.,4,Direct statistic
S03,Salesforce,How to Troubleshoot a Non-Functional Web-to-Lead Form,https://help.salesforce.com/s/articleView?id=005228877&language=en_US&type=1,Troubleshooting and debug log guidance,2025-11-18,N/A,N/A,Salesforce Web-to-Lead implementations,Global product documentation,All,Debug logs and controlled submissions are relevant evidence when a Web-to-Lead form does not create a record.,N/A,N/A,Form submission to lead creation,Troubleshooting guide,Web-to-Lead,Exact page content may vary by Salesforce release.,3,Contextual example
S04,Salesforce,Salesforce Duplicate Matching Rules Blocking Web-to-Lead Submissions,https://help.salesforce.com/s/articleView?id=000387310&language=en_US&type=1,Duplicate rule behavior for Web-to-Lead,2026-06-20,N/A,N/A,Salesforce organisations with duplicate rules and Web-to-Lead,Global product documentation,All,"A duplicate rule can prevent a Web-to-Lead record from being created, including configurations that appear permissive in other channels.",N/A,N/A,Lead insert to duplicate-rule decision,Product troubleshooting documentation,Configuration-dependent,Actual outcome depends on duplicate and matching rule settings.,3,Contextual example
S05,Salesforce,Who owns new web-generated leads?,https://help.salesforce.com/s/articleView?id=sf.faq_leads_who_owns_new.htm&language=en_US&type=5,Default lead owner behavior,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce web leads,Global product documentation,All,"If an assignment rule does not determine an owner, a web lead can be assigned to the configured default lead owner.",N/A,N/A,Assignment evaluation to owner write,Product documentation,Web lead and default owner configuration,A fallback owner is not evidence that the primary rule worked.,3,Contextual example
S06,Salesforce,Case or Lead Assignment Rules fail to set the Owner,https://help.salesforce.com/s/articleView?id=000385609&language=en_US&type=1,"Active rule, criteria and apply-rule troubleshooting",Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce lead assignment implementations,Global product documentation,All,"Unexpected ownership can result from inactive rules, criteria mismatch or a transaction that did not invoke the active assignment rule.",N/A,N/A,Record save to assignment-rule invocation,Troubleshooting documentation,Transaction channel and configuration matter,"Does not cover custom Flow, Apex or third-party routers comprehensively.",3,Contextual example
S07,Salesforce,Assignment Rule Header,https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_header_assignmentruleheader.htm,AssignmentRuleHeader behavior,Current developer documentation; accessed 2026-07-23,N/A,N/A,Salesforce API inserts and updates,Global developer documentation,All,"API transactions can explicitly invoke an assignment rule through the AssignmentRuleHeader, so channel-specific test cases are required.",N/A,N/A,API request to assignment evaluation,Developer API specification,API behavior,Implementation language and API version must be recorded.,3,Comparison input
S08,Salesforce,Triggers and Order of Execution,https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm,Order of execution; duplicate rules and later automation,Current developer documentation; accessed 2026-07-23,N/A,N/A,Salesforce record-save transactions,Global developer documentation,All,Save-time automation executes in a defined order; a blocked save prevents later routing and notification steps from occurring.,N/A,N/A,Record save start to commit,Developer documentation,Order varies by automation type and release,Custom implementations can add asynchronous paths after commit.,3,Comparison input
S09,Salesforce,Set the Run Order of Record-Triggered Flows,https://help.salesforce.com/s/articleView?id=platform.flow_concepts_trigger_order.htm&language=en_US&type=5,Trigger order values and execution order,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce record-triggered flows,Global product documentation,All,"Flow run order is configurable, so the audit must capture active versions and trigger order rather than only flow names.",N/A,N/A,Record trigger to ordered flow execution,Product documentation,Record-triggered Flow only,Does not resolve interactions with all Apex and managed-package logic.,3,Comparison input
S10,Salesforce,Improve Data Quality in Salesforce,https://trailhead.salesforce.com/content/learn/modules/sales_admin_duplicate_management/sales_admin_duplicate_management_unit_1,Identifying duplicate records and how to handle them,Current Trailhead module; accessed 2026-07-23,N/A,N/A,Salesforce administrators,Global training content,All,"Matching rules define how potential duplicates are identified; duplicate rules define whether records are allowed, alerted or blocked.",N/A,N/A,Candidate record comparison to duplicate action,Official training documentation,Configured matching and duplicate rules,Training content abstracts edition and customisation details.,3,Contextual example
S11,Salesforce,Duplicate Rules Overview,https://help.salesforce.com/s/articleView?id=sales.duplicate_rules_overview.htm&language=en_US&type=5,Simultaneous record comparison limitation,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce duplicate management,Global product documentation,All,"Records created at the same time are not necessarily compared with each other by duplicate rules, creating a concurrency boundary case.",N/A,N/A,Concurrent record inserts to duplicate evaluation,Product documentation,Duplicate management behavior,Exact concurrency outcome should be tested in the target org.,3,Contextual example
S12,Salesforce,Field History Tracking,https://help.salesforce.com/s/articleView?id=tracking_field_history.htm&language=en_US,Tracked field limits and history behavior,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce standard and custom objects,Global product documentation,Edition-dependent,"Standard field history tracking is limited in coverage, so the audit must choose routing-critical fields deliberately or use additional audit capability.",Tracked fields,Potential fields,Field update to retained history,Product documentation,Edition and object limits apply,Field Audit Trail is a separate licensed capability with different limits.,3,Contextual example
S13,Salesforce,Debug Logs,https://help.salesforce.com/s/articleView?id=code_debug_log.htm&language=en_US&type=5,Debug log creation and analysis,Current Help page; accessed 2026-07-23,N/A,N/A,Salesforce administrators and developers,Global product documentation,All,"Debug logs can expose execution details for controlled tests, but only when logging is configured and retained.",N/A,N/A,Transaction execution to log record,Product documentation,"Trace flags, log levels and retention apply",Absence of a log is not evidence that no failure occurred.,3,Contextual example
S14,Salesforce,Assignment rules do not send notification emails for Leads or Cases created via API,https://help.salesforce.com/s/articleView?id=000384839&language=en_US&type=1,Assignment notification behavior for API-created records,2026-05-01,N/A,N/A,Salesforce API-created leads or cases,Global product documentation,All,"An owner assignment can succeed while the expected notification does not occur, depending on transaction channel and notification settings.",N/A,N/A,Owner assignment to notification dispatch,Product troubleshooting documentation,API and assignment configuration dependent,Email deliverability adds a separate downstream control.,3,Contextual example
S15,HubSpot,View form submissions,https://knowledge.hubspot.com/forms/view-form-submissions,Submission details and CRM-record linkage,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot form submissions,Global product documentation,All HubSpot plans subject to feature availability,HubSpot preserves submission-level details that can be compared with the resulting CRM record.,N/A,N/A,Form submission to submission record,Product documentation,HubSpot form types and permissions apply,Submission evidence alone does not prove later routing.,3,Contextual example
S16,HubSpot,Use non-HubSpot forms,https://knowledge.hubspot.com/forms/use-non-hubspot-forms,Before you get started; mapping behavior,2026-04-15,N/A,N/A,External HTML forms collected by HubSpot tracking code,Global product documentation,All,"Non-HubSpot collection can reject submissions above the form-count limit, record partial submit clicks, fail when tracking code or JavaScript is blocked, and retain submission data even when a field is not stored on the contact record.",Rejected or partial submissions where applicable,Non-HubSpot form submit events,Browser submit click to HubSpot submission/contact update,Product documentation,Static HTML form and tracking-code requirements,Behavior differs from native HubSpot forms and direct Form API integrations.,4,Direct statistic
S17,HubSpot,Add data privacy and consent information to your HubSpot form,https://knowledge.hubspot.com/forms/add-notice-and-consent-information-to-your-hubspot-form,Before you get started; existing-form update behavior,2025-12-17,N/A,N/A,HubSpot forms using privacy and consent fields,Global product documentation; legal relevance jurisdiction-specific,All,A form submission can set legal-basis and communication-consent records; changing default consent text does not automatically update existing forms.,N/A,N/A,Form interaction to consent properties,Product documentation,Privacy settings and selected options apply,HubSpot explicitly directs users to legal counsel for situation-specific advice.,3,Contextual example
S18,HubSpot,Enrich your contact and company data,https://knowledge.hubspot.com/records/enrich-your-contact-and-company-data,Eligibility requirements and fill behavior,2026-04-30,N/A,N/A,HubSpot contacts and companies selected for enrichment,Global product documentation,Feature availability varies by subscription,"Contact enrichment requires a business email, company enrichment requires a domain, and records are not enriched when no eligible data is available.",Eligible enriched records,Records submitted for enrichment,Record selection to enrichment outcome,Product documentation,"Subscription, permissions and enrichment availability apply",Availability is not a correctness guarantee; enriched values still require routing-safe fallbacks.,4,Comparison input
S19,HubSpot,Assign ownership of records,https://knowledge.hubspot.com/records/how-to-set-a-record-owner,Rotate records between multiple owners,2026-05-01,N/A,N/A,HubSpot records assigned or rotated by workflows,Global product documentation,Subscription-dependent,"Rotation counts are action-specific; the first assignment among equal counts is random, and changing owners can reset the established rotation.",Assignment counts per rotate action,Records passing through that rotate action,Workflow action entry to owner assignment,Product documentation,HubSpot rotate-record workflow action,Fairness within an action is not the same as equal total portfolio ownership.,4,Comparison input
S20,HubSpot,Review your workflow's enrollment history,https://knowledge.hubspot.com/workflows/workflow-enrollment-history,History retention and daily successful-log limit,Current page; accessed 2026-07-23,N/A,N/A,HubSpot workflow executions,Global product documentation,Subscription-dependent,"Enrollment history is stored for six months; after 100,000 successful workflow execution logs in a day, further success and info logs are not stored that day, while error logs continue.",Stored successful execution logs,Successful workflow executions per day,Workflow execution to log retention,Product documentation,HubSpot workflow logging,Retention and product behavior can change; missing success logs can reflect the limit rather than absence of execution.,4,Direct statistic
S21,HubSpot,View workflow revision history,https://knowledge.hubspot.com/workflows/view-workflow-revision-history,Revision list and restore behavior,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot workflows,Global product documentation,Subscription-dependent,Workflow revision history can identify which version was active around an incident and supports version-aware testing.,N/A,N/A,Workflow change to revision record,Product documentation,Feature availability and retention apply,A revision record does not prove which branch a specific record followed without execution evidence.,3,Contextual example
S22,HubSpot,Export property history,https://knowledge.hubspot.com/properties/export-property-history,"Export content, revision limits and UTC timestamps",Current page; accessed 2026-07-23,N/A,N/A,HubSpot CRM object properties,Global product documentation,All plans subject to permissions,"Property-history exports can include old and current values, update time and source; contact properties retain up to 45 revisions and several other object types up to 20; timestamps are UTC.",Retained revisions,Property updates,Property update to history export,Product documentation,Only records with a past or current value are included,High-churn properties can exceed revision retention and hide older ownership changes.,4,Direct statistic
S23,HubSpot,Understand record property change sources,https://knowledge.hubspot.com/properties/understand-source-information-in-property-history,Source information definitions,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot CRM property changes,Global product documentation,All,"Property source information can identify the user or tool responsible for a value change, supporting remediation ownership.",N/A,N/A,Property update to source label,Product documentation,Source labels vary by update mechanism,A generic tool label may not identify the exact internal branch or external request.,3,Contextual example
S24,HubSpot,Deduplicate records in HubSpot,https://knowledge.hubspot.com/records/deduplication-of-records,Automatic deduplication identifiers,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot contacts and companies,Global product documentation,All,HubSpot automatically uses email for contact deduplication and company domain for company deduplication in supported creation paths.,N/A,N/A,Record creation/update to identity match,Product documentation,Creation method and object type matter,Not every integration path and custom object follows the same identifier logic.,3,Comparison input
S25,HubSpot,Add additional domains to a company,https://knowledge.hubspot.com/records/add-additional-domains-to-a-company,"Primary domain, associations and history limitations",Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot company records with multiple domains,Global product documentation,All,Additional domains affect future matching and association but do not merge existing companies automatically; additional domain changes are not represented like normal property history.,N/A,N/A,Domain configuration to contact-company association,Product documentation,Primary and additional domains have different behavior,"Account matching needs explicit tests for subsidiaries, aliases and multiple candidate companies.",3,Comparison input
S26,HubSpot,Manage your Salesforce integration settings,https://knowledge.hubspot.com/salesforce/manage-your-salesforce-integration-settings,"Sync Health, API allocation and sync errors",Current page; accessed 2026-07-23,N/A,N/A,HubSpot-Salesforce integrations,Global product documentation,Integration subscription and Salesforce limits apply,Sync Health exposes API allocation and error categories with counts of impacted records; sync errors can prevent data from moving between systems.,Impacted records per error type,"Records attempted for sync, if available in account",Source-system change to integration sync outcome,Product documentation,HubSpot-Salesforce connector settings,Dashboard counts require a preserved export or screenshot for incident evidence.,3,Contextual example
S27,HubSpot,Troubleshoot Salesforce sync errors,https://knowledge.hubspot.com/salesforce/troubleshoot-salesforce-sync-errors,Errors preventing sync and duplicate-rule examples,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot-Salesforce integrations,Global product documentation,All connector users,"Permission, validation and duplicate-rule errors can stop individual records from synchronising even while the connector remains installed.",Records in an error state,Records attempted for sync,Sync attempt to error resolution,Troubleshooting documentation,Error-specific,"Connector health must be checked at record level, not inferred from installation status.",3,Contextual example
S28,HubSpot,Install and use the HubSpot-Salesforce integration,https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration,Initial sync and resync behavior,Current Knowledge Base page; accessed 2026-07-23,N/A,N/A,HubSpot-Salesforce integrations,Global product documentation,All connector users,"Existing records do not necessarily synchronise immediately after installation; imports, triggers and login restrictions can affect the initial and continuing sync.",N/A,N/A,Integration installation to record sync,Product documentation,Connector setup and Salesforce security configuration,Exact setup sequence varies by account and release.,3,Contextual example
S29,Zapier,View and manage your Zap history,https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history,"Run details, version and step data",Current Help page; accessed 2026-07-23,N/A,N/A,Zapier workflow runs,Global product documentation,Plan-dependent,"Zap history records run status, workflow version, timestamps and data received and sent by each step, making it usable as transaction evidence.",N/A,N/A,Trigger receipt to each action outcome,Product documentation,History access and plan retention apply,Deleting a completed run removes the record but does not undo its action.,3,Contextual example
S30,Zapier,What is replay?,https://help.zapier.com/hc/en-us/articles/19220226086797-What-is-replay,"Autoreplay attempts, exclusions and time limits",Current Help page; accessed 2026-07-23,N/A,N/A,Errored Zap runs,Global product documentation,Plan-dependent,Autoreplay can retry an errored step up to five times; Filter and Paths steps are not replayed; runs must be replayed within 60 days and require available tasks.,Replay attempts,Eligible errored steps,Error to replay outcome,Product documentation,"Status, plan, task balance and workflow-change restrictions apply",Retries can increase latency and may repeat side effects unless downstream actions are idempotent.,4,Direct statistic
S31,Zapier,Understand held and stopped Zap runs,https://help.zapier.com/hc/en-us/articles/8496037690637-Understand-held-and-stopped-Zap-runs,On-hold causes including app connection and task limits,Current Help page; accessed 2026-07-23,N/A,N/A,Zapier workflow runs,Global product documentation,Plan-dependent,"A workflow can be on hold because of disconnected apps, account limits or platform policy, creating delayed rather than immediately failed transactions.",Held runs,Triggered runs,Trigger to hold/release,Product documentation,Status-specific,A held state requires an audit cut-off rule to classify delay versus loss.,3,Contextual example
S32,Workato,Workato API - Jobs,https://docs.workato.com/workato-api/jobs.html,Repeat jobs limitations,Current documentation; accessed 2026-07-23,N/A,N/A,Workato recipe jobs,Global developer documentation,Plan and retention dependent,"Jobs can be repeated only within retention, in batches of up to 25, with a maximum of 100 repeats per master job.",Repeated jobs,Eligible retained master jobs,Master job to repeat execution,Developer API documentation,Retention and trigger-data availability apply,Repeat behavior must be tied to recipe version and idempotency controls.,4,Direct statistic
S33,Segment,Analytics.js retry behavior,https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/,Network and server retry behavior,Current developer documentation; accessed 2026-07-23,N/A,N/A,Segment Analytics.js events,Global developer documentation,All,"Client libraries may retry delivery after network or server errors, so a routing audit must distinguish one logical submission from multiple delivery attempts.",Delivery attempts,Logical events,Browser event to destination delivery,Developer documentation,Library and destination behavior vary,Duplicate business effects are an inference and depend on destination idempotency.,3,Comparison input
S34,HubSpot Developers,Webhooks API documentation,https://developers.hubspot.com/docs/api-reference/webhooks-webhooks-v3/guide,Delivery attempts and response handling,Current developer documentation; accessed 2026-07-23,N/A,N/A,HubSpot webhook subscriptions,Global developer documentation,All developer users,Webhook delivery and retry behavior is version-specific; receivers should return success promptly and maintain their own processing evidence.,Delivery attempts,Webhook events,Webhook event to receiver acknowledgement,Developer documentation,API version and subscription type must be recorded,HubSpot documentation contains version-specific retry semantics; never generalise across webhook modes.,3,Comparison input
S35,Information Commissioner's Office,What is valid consent?,https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/consent/what-is-valid-consent/,Consent request and record-keeping guidance,Current guidance; accessed 2026-07-23,N/A,N/A,Controllers relying on consent under UK GDPR,United Kingdom,All covered organisations,"Where consent is the lawful basis, requests should be clear and separate, and organisations should retain evidence that consent was obtained.",N/A,N/A,Consent request to demonstrable record,Regulatory guidance,UK GDPR and PECR context; legal basis varies,Not legal advice and not universally applicable outside the UK.,3,Contextual example
S36,European Union,"General Data Protection Regulation, Article 7",https://eur-lex.europa.eu/eli/reg/2016/679/art_7/oj,Article 7 conditions for consent,Regulation applicable since 2018; accessed 2026-07-23,N/A,N/A,Processing subject to EU GDPR where consent is relied upon,European Union / EEA context,All covered controllers and processors,A controller relying on consent must be able to demonstrate that the data subject consented; withdrawal must be possible.,N/A,N/A,Consent to demonstrability/withdrawal,Primary legal text,Only where EU GDPR applies and consent is the selected lawful basis,Requires jurisdiction-specific legal interpretation.,3,Contextual example
S37,RevenueHero,How to Audit Your Lead Routing Workflow,https://www.revenuehero.io/blog/how-to-audit-your-lead-routing-workflow-3,Benchmark and workflow-mapping sections,2026-07-06,Stated as 12 months; exact dates not disclosed,Not disclosed,Described as B2B SaaS customers; selection rules not disclosed,Not disclosed,B2B SaaS; size mix not disclosed,Page reports qualified-to-booked medians and vertical comparisons from proprietary aggregate data.,Booked meetings,"Qualified leads, as described; operational definitions not fully disclosed",Qualified lead to booked meeting,Proprietary aggregate; public method incomplete,Unknown inclusion/exclusion and customer selection,"Commercial source, non-reproducible, insufficient for a universal benchmark.",3,Exclusion
S38,LeanData,Best Ways to Audit Lead Routing and Uncover Lost Leads,https://www.leandata.com/blog/best-ways-to-audit-lead-routing-and-uncover-lost-leads/,"Salesforce assignment, round-robin and audit-log sections",2023-01-10,N/A,N/A,Salesforce/LeanData users,Global commercial content,B2B revenue teams,"Page recommends mapping the lifecycle and reviewing assignment rules, defaults, notifications, round robin, Flow/Apex and vendor audit logs.",N/A,N/A,Configuration review,Vendor implementation guidance,Salesforce-centric and LeanData-commercial,Does not establish a platform-neutral transaction evidence model.,2,Contextual example
S39,NC Squared,How to Audit Your Salesforce Lead Routing Logic and Fix What's Broken,https://nc-squared.com/blog/article/how-to-audit-your-salesforce-lead-routing-logic-and-fix-whats-broken,Five metrics and benchmark sections,2026-06-11,Not disclosed,Not disclosed,Not disclosed,Not disclosed,Salesforce users,"Page proposes assignment-to-first-touch, distribution parity, default owner, rule bypass and SLA breach metrics, plus universal health thresholds.",Varies,Not consistently defined,Varies,Commercial guidance; no study method disclosed,Salesforce-centric,Threshold and uplift claims should not be used as benchmarks.,1,Exclusion