Paid Lens is a Decision Intelligence tool for performance marketing scenarios, with the core goal of making the "next budget adjustment" clear and judgeable. Through read-only connections, it brings together ad platforms, CRM, analytics tools, and revenue data, validates the data signals, and then ranks the most worthwhile actions by Impact, Urgency, and Confidence.
Purpose Paid Lens serves teams whose ad spend must translate into revenue, helping them reduce time spent piecing together reports and staring at dashboards, and focus their energy on defensible budget decisions. It is clearly positioned as a "controlled decision layer," not an automated media buying system—it will not automatically modify campaigns on the user's behalf, and all actions must be reviewed and decided by the team.
Main capabilities
- Data connections: aggregate advertising, CRM, analytics, and revenue signals through read-only connections; Google Analytics is listed in the official examples.
- Validation loop: check data completeness, data freshness, attribution coverage, integration health, and sufficiency of evidence.
- Recommendation ranking: prioritize potential actions by impact, urgency, and evidence-based confidence.
- Decision queue: turn scattered signals into a ranked decision queue, with each recommendation carrying a clear action, supporting evidence, and rationale.
- Confidence mechanism: confidence reflects the quality of the evidence supporting a recommendation, not how confidently the model expresses an answer; when data is incomplete, stale, inconsistent, or poorly attributed, confidence drops, recommendations are suppressed or turned into watch items, and the missing signals are pointed out.
- Example recommendation types: reallocate budget, reduce budget for a campaign, increase budget for a campaign, watch campaigns whose attribution coverage is below a threshold. The official examples show P1/P2/P3 priority recommendations, annotated with estimated impact, confidence, and urgency.
How to use it The officially described workflow has four steps: 01 Connect—bring together advertising, CRM, analytics, and revenue signals through read-only connections; 02 Validate—check data completeness, freshness, attribution coverage, integration health, and sufficiency of evidence; 03 Rank—prioritize potential actions by impact, urgency, and evidence-based confidence; 04 Decide—review recommendations, inspect the evidence, and let the team decide what action to take. Each recommendation can be expanded to see why it exists, its supporting evidence, expected impact, system confidence, and who decides the next step. Its pattern can be summarized as "recommendation → evidence → decision."
Use cases
- Performance marketing teams:reduce time spent piecing together reports and devote more energy to making defensible budget decisions.
- B2B SaaS growth teams: connect paid acquisition performance with pipeline and revenue signals.
- Performance marketing agencies: provide clients with a defensible decision layer rather than yet another reporting dashboard. The official materials emphasize that its security and compliance controls are designed for modern B2B teams.
Limitations Paid Lens does not automatically make any changes to campaigns; all actions must be reviewed by the team before they happen; it is a controlled decision layer, not an autonomous media buying system. When evidence is insufficient, it suppresses recommendations or turns them into watch items rather than giving high-confidence actions. Information such as specific charging methods, pricing, the complete list of supported platforms, and deployment methods is not yet provided in the materials.
