# DataLens AI

> The AI analyst that shows its work. AI-powered data exploration, analysis, and visualization agent with BigQuery integration and multi-model LLM support.

DataLens connects to your data warehouse (BigQuery), Google Ads, Meta Ads, and spreadsheets, answers plain-English questions with live queries, and shows the SQL behind every answer.

## Blog

- [Why Your ROAS in Google Ads Never Matches Your ROAS in Your CRM / Backend Database](https://www.datalensai.in/blog/roas-google-ads-vs-bigquery): Google Ads, Meta, and your CRM or backend database each attribute revenue differently. Here is exactly why the numbers disagree, and how to reconcile them without picking one to trust blindly.
- [Why Shopify, GA4 and Meta Report Three Different Revenue Numbers for the Same Day](https://www.datalensai.in/blog/shopify-ga4-meta-three-revenue-numbers): Three systems, one day, three revenue totals — and none of them is broken. Timezones, refunds, tax and shipping explain most of the gap. Here is how to decompose it line by line.
- [Self-Reported Attribution vs. Your Pixel: What "How Did You Hear About Us?" Is Actually Good For](https://www.datalensai.in/blog/self-reported-attribution-vs-pixel): A post-purchase survey will never reconcile with your pixel, and it was never supposed to. Here is the question it does answer, and how to weight the answer without fooling yourself.
- [UTM Governance: A Naming Convention That Survives Three Agencies](https://www.datalensai.in/blog/utm-governance-naming-convention): Most UTM schemes die the first time someone else touches them. A convention, a validator query, and the four rules that keep a taxonomy intact across agency handovers.
- [Modeled Conversions: What Google and Meta Are Filling In for You](https://www.datalensai.in/blog/modeled-conversions-explained): A share of the conversions in your ad dashboard were never observed — they were estimated. What modeling is, why it exists, and how to report a number that is part measurement and part inference.
- [Click IDs Are the Real Attribution Key: GCLID, FBCLID, WBRAID and Server-Side Tracking](https://www.datalensai.in/blog/click-ids-gclid-fbclid-server-side-tracking): Every attribution argument rests on a query parameter in the landing URL. What each click ID is, the five places it dies, and the two server-side systems that recover it.
- [Offline Conversion Imports: Teaching Google and Meta What Money Looks Like](https://www.datalensai.in/blog/offline-conversion-imports-crm-to-google-meta): The pixel sees the lead; the CRM sees the money ninety days later. What to send back, how matching works, and the mistakes that make imports harmful.
- [ATT, SKAN and the Privacy Sandbox: Why Your Dashboards Changed and What Works Now](https://www.datalensai.in/blog/ios-att-skan-privacy-sandbox-dashboards): Apple removed the identifier and Google is following. What ATT, SKAN and the Sandbox did to measurement, why dashboards look worse, and the stack that works on top.
- [Meta Ads vs. Google Ads: Five Metric Names That Don't Mean the Same Thing](https://www.datalensai.in/blog/meta-vs-google-metric-names): The same word means a different calculation on each platform. A field guide to the five most commonly confused metrics between Meta and Google Ads.
- [Your GA4 Numbers Don't Match Your Ad Platform. Here's the Decision Tree](https://www.datalensai.in/blog/ga4-vs-ad-platform-decision-tree): A step-by-step way to figure out which discrepancy you're looking at — attribution window, sampling, or a broken tag — before you file a bug report.
- [Conversion Lag: Why Yesterday's ROAS Is a Lie Until Thursday](https://www.datalensai.in/blog/conversion-lag-yesterdays-roas): Same-day and next-day conversion numbers are provisional, not final. Here is how much they typically move, and how to report on them honestly.
- [How to Read Database Query Plans and Stop the $400 Surprise Bill](https://www.datalensai.in/blog/bigquery-query-plan-400-bill): Cloud databases and warehouses bill by data scanned and compute used, not rows returned. Here is how to inspect query estimates before running, and the three habits that cut query costs 10-100x.
- [Your First 10 BigQuery Cost Guardrails — Before the Bill, Not After](https://www.datalensai.in/blog/bigquery-cost-guardrails): Ten controls you can put in place in an afternoon, ordered by how much they save per hour of effort. Custom quotas, maximum bytes billed, partition requirements, and the ones people skip.
- [Incremental Models Without dbt: Scheduled Queries That Don't Re-Scan the Year](https://www.datalensai.in/blog/incremental-models-without-dbt): You do not need a transformation framework to stop rebuilding a rolling table from scratch every morning. MERGE, a watermark, and a late-arriving-data window — in plain scheduled SQL.
- [Joining Ad Spend to Orders When There's No Common Key](https://www.datalensai.in/blog/joining-ad-spend-to-orders-no-key): Campaign-level spend and row-level orders share no id. Here are the three join grains that actually work, the fan-out bug that ruins the naive version, and the SQL for each.
- [Postgres vs. a Warehouse for Marketing Reporting: When to Stop Querying Prod](https://www.datalensai.in/blog/postgres-vs-warehouse-marketing-reporting): Your production database can carry marketing reporting further than most people assume — and then it cannot. The four signals that mean it is time, and the cheapest thing to do next.
- [One Currency, One Timezone: Normalising Multi-Account Reporting Before It Lies to You](https://www.datalensai.in/blog/currency-timezone-normalization-multi-account): USD and INR spend in one column, UTC and account-timezone days in one join. The exchange-rate table, the convert-then-truncate rule, and the view every report should read.
- [Why Your Revenue Doubled Overnight: Deduplicating Orders and Events in SQL](https://www.datalensai.in/blog/deduplicating-orders-events-sql): Ingestion doubles, fan-out joins and grain confusion multiply rows three different ways. The diagnostics that catch each and the dedup views that prevent them.
- [Stale Dashboards Lie Confidently: Freshness Checks That Catch a Broken Pipeline First](https://www.datalensai.in/blog/freshness-checks-broken-pipeline): A credential expired and the Monday review debated a demand collapse that never happened. Three layers of scheduled validation queries — freshness, shape, reconciliation.
- [The GA4 Database Export Schema, Explained Field by Field for Marketers](https://www.datalensai.in/blog/ga4-bigquery-export-schema): A marketer's guide to GA4 export's nested table structure — what event_params actually holds, and how to query it without a data engineering background.
- [Partitioning and Clustering, Explained With One Marketing Table](https://www.datalensai.in/blog/partitioning-clustering-marketing-table): Walk through what partitioning and clustering actually do to a query, using a single GA4-style events table as the running example.
- [Google Ads Data Transfer vs. the API: Which One Your Reporting Should Use](https://www.datalensai.in/blog/ads-transfer-vs-api): Two ways to get Google Ads data into BigQuery, with very different freshness, cost and maintenance tradeoffs. A practical comparison for choosing one.
- [Contribution-Margin ROAS: The Only ROAS That Survives a CFO Review](https://www.datalensai.in/blog/contribution-margin-roas): Revenue ROAS answers a question finance never asked. Here is how to rebuild it on contribution margin — with the cost lines people forget, and the SQL that computes it.
- [New vs. Returning Customer ROAS, and Why Blended Hides an Acquisition Problem](https://www.datalensai.in/blog/new-vs-returning-customer-roas): A stable blended ROAS can conceal acquisition falling apart underneath it. Split the numerator by customer type and the trend you actually need to see appears.
- [Payback Period vs. LTV:CAC — Which One Actually Gates Your Ad Budget](https://www.datalensai.in/blog/payback-period-vs-ltv-cac): LTV:CAC tells you whether a customer is worth acquiring. Payback tells you whether you can afford to acquire them this quarter. Only one of those is a budget constraint.
- [RTO and COD in Indian D2C: Your ROAS Is Wrong Until Delivery Confirms](https://www.datalensai.in/blog/rto-cod-indian-d2c-roas): A cash-on-delivery order is a promise, not revenue. With RTO rates running 15-35%, order-time ROAS overstates reality by a third — here is how to measure delivered ROAS instead.
- [Frequency, Reach and Saturation: Reading the Curve Before You Scale Spend](https://www.datalensai.in/blog/frequency-reach-saturation): Scaling spend inside a finite audience buys frequency, not reach. How to read the three curves together, and the diagnostic that tells you which wall you have hit.
- [Breakeven ROAS From First Principles: Margin, Fees, Shipping and the Floor Under Every Target](https://www.datalensai.in/blog/breakeven-roas-first-principles): One division sets the floor beneath every target you will ever set. Deriving breakeven from the full variable stack and running it as a bidding guardrail.
- [Cohort Payback Curves: Why Month-0 ROAS Misleads Repeat-Purchase Brands](https://www.datalensai.in/blog/cohort-payback-curves-repeat-purchase): Snapshot metrics judge a movie by its first frame. Grouping customers by acquisition vintage, reading payback as a crossing point, and separating acquisition from retention.
- [Discount-Adjusted Metrics: How Sale Events Inflate ROAS While Destroying Contribution](https://www.datalensai.in/blog/discount-adjusted-metrics-sale-events): Revenue triples and profit misses anyway. Margin compression, pull-forward holes and price-anchor erosion — and the reporting that prices each sale honestly.
- [Blended CAC vs. Channel CAC — Which One Goes to the Board?](https://www.datalensai.in/blog/blended-vs-channel-cac): Channel-reported CAC is almost always cheaper than blended CAC, and both numbers are correct. Here's how to know which one belongs in which conversation.
- [MER Explained, With the SQL](https://www.datalensai.in/blog/mer-explained-with-sql): Marketing Efficiency Ratio sidesteps attribution disagreements entirely. Here's the formula, a worked example, and the query that computes it from a warehouse.
- [Attribution Windows: 1-Day Click, 7-Day View, and Why Your Numbers Moved](https://www.datalensai.in/blog/attribution-windows-explained): Every ad platform ships a different default attribution window. Here is what each window setting actually changes, with worked examples.
- [Incrementality vs. Last-Click for Teams Without a Data Scientist](https://www.datalensai.in/blog/incrementality-vs-last-click): A holdout test is the only way to know an ad's true causal effect. Here is a lightweight version any team can run without a dedicated experimentation function.
- [LTV:CAC Is a Ratio, Not a Target — How to Read It Honestly](https://www.datalensai.in/blog/ltv-cac-honest-read): A 5:1 LTV:CAC ratio means very different things depending on payback time. How to read the ratio alongside the number that actually matters.
- [Seven Questions to Ask Before You Trust an AI's Answer About Your Data](https://www.datalensai.in/blog/seven-questions-before-trusting-ai): A syntactically valid query can still answer the wrong question. Seven concrete checks to run before you act on a number an AI gave you.
- [What an AI Analyst Can't Do Yet — an Honest List](https://www.datalensai.in/blog/what-ai-analyst-cannot-do): Eight things an AI analyst genuinely cannot do, written by someone building one. Where the ceiling is, why it is there, and which limits are shrinking.
- [Semantic Layers vs. Prompting: Where Business Definitions Should Live](https://www.datalensai.in/blog/semantic-layers-vs-prompting): You can put "active customer means ordered in 90 days" in a prompt, or in a semantic layer. One of those is a definition; the other is a suggestion.
- [How We Keep an LLM From Inventing a Column Name](https://www.datalensai.in/blog/preventing-llm-hallucinated-columns): A model that has never seen your schema will guess `order_total` and be wrong. The four layers — retrieval, constrained context, dry-run validation, repair — that stop it shipping.
- [The Real Cost of an AI Analytics Question: Tokens, Query Bytes, and What Drives the Bill](https://www.datalensai.in/blog/cost-of-an-ai-analytics-question): Two costs stack on every AI-generated answer, and the smaller one gets all the attention. A line-by-line breakdown of where the money actually goes.
- [Scheduled AI Reports vs. Dashboards: When a Daily Narrative Beats a Chart](https://www.datalensai.in/blog/scheduled-ai-reports-vs-dashboards): A dashboard waits to be opened. A scheduled narrative arrives whether or not anyone was looking. Which failure mode each one has, and how to pick.
- [Benchmarking an AI Analyst on Your Own 20 Golden Questions](https://www.datalensai.in/blog/benchmarking-ai-analyst-golden-questions): Fluency is not accuracy and demos are not decisions. Building a verified question-SQL-answer suite that scores models, prompts and schema changes.
- [Anomaly Alerts That Do Not Spam: Static Thresholds vs Dynamic Baselines](https://www.datalensai.in/blog/anomaly-alerts-thresholds-baselines): Every false alarm trains readers to ignore the real one. Respecting data maturity, expecting seasonality, and the severity ladder that keeps channels trusted.
- [Least-Privilege Data Access for AI Tools: Views, Redaction, Row Limits](https://www.datalensai.in/blog/least-privilege-data-access-ai): Exposing everything is a privacy surface and an accuracy problem at once. The analyst views, tokenisation and caps that narrow the world and improve the answers.
- [Text-to-SQL Isn't the Hard Part — Schema Context Is](https://www.datalensai.in/blog/text-to-sql-schema-context): Writing correct SQL syntax is the easy 20%. Knowing which of five tables holds "revenue" and how they join is the part that actually determines whether the answer is right.
- [How to Audit an AI-Generated Query in 60 Seconds](https://www.datalensai.in/blog/audit-ai-query-60-seconds): A fast checklist for scanning any AI-written SQL query before you trust its output — the joins, the filters, and the aggregation, in that order.
- [Why Every DataLens Answer Ships Its SQL](https://www.datalensai.in/blog/why-every-answer-ships-sql): A product philosophy note: why we decided a number without its query attached isn't a trustworthy number, and what that decision costs us.
- [Bring Your Own API Key: What That Actually Means for Your Data](https://www.datalensai.in/blog/bring-your-own-api-key): DataLens lets you connect your own model provider key instead of routing through ours. Here is what that changes about where your data goes.
- [Budget Pacing Mid-Flight: Reading Spend-vs-Plan Before the Month Ends](https://www.datalensai.in/blog/budget-pacing-mid-flight): Prorated expectations, partial-day honesty and the intraday trap: how to tell on the 12th whether you will overspend, underspend or land exactly on plan.
- [Creative Fatigue vs Audience Saturation: Telling Them Apart Before You Spend More](https://www.datalensai.in/blog/creative-fatigue-vs-audience-saturation): Frequency plus reach plus CPM decompose every scaling stall into its true cause. New creative fixes one of them; only a wider audience fixes the other.
- [Search-Term Mining: The Weekly Query That Pays for Itself](https://www.datalensai.in/blog/search-term-mining-weekly-query): The search terms report is a list of customers telling you what they wanted in their own words. The 30-minute weekly routine that converts it into negatives and new keywords.
- [Impression-Share Autopsy: Lost to Budget vs Lost to Rank](https://www.datalensai.in/blog/impression-share-lost-budget-vs-rank): Two loss columns prescribe opposite fixes: one wants money, the other wants better bids, quality or creative. Reading the split before spending a rupee more.
- [Geo Waste: The Pincodes Your Budget Should Never Have Visited](https://www.datalensai.in/blog/geo-waste-pincodes-rto-overlay): Delivery failures, COD refusal and serviceability gaps make some geographies structurally unprofitable. Overlaying RTO on geo performance finds the exclusion list.
- [Change-History Forensics: What Broke the Campaign Last Tuesday](https://www.datalensai.in/blog/change-history-forensics): Performance breaks have authors: edits, budget moves, auction shifts. Correlating the change log with the break before touching anything else.


## Blog clusters

- [Metric Discrepancies & Attribution](https://www.datalensai.in/blog/attribution): Why Google Ads, Meta, and your CRM show different numbers for the same campaign — and how to tell which one to trust.
- [Databases & Query Optimization](https://www.datalensai.in/blog/bigquery): How your ad and order data is stored, why reports can be slow or costly to run, and how to keep them fast and cheap — no engineering background needed.
- [Metric Explainers](https://www.datalensai.in/blog/metrics): What common ad numbers like CAC and ROAS actually mean, how to work them out, and the mix-ups that lead teams astray.
- [AI + Analytics](https://www.datalensai.in/blog/ai-analytics): How to check an AI answer about your numbers before you act on it — and why DataLens always shows its work alongside the answer.
- [Campaign Diagnostics & Optimization](https://www.datalensai.in/blog/diagnostics): When a campaign stops working, there are only a handful of usual causes. How to spot which one you have and what to do about it.


## Glossary

- [ROAS (Return on Ad Spend)](https://www.datalensai.in/glossary/roas): ROAS is the revenue generated for every unit of currency spent on advertising, expressed as a ratio or a multiple.
- [Breakeven ROAS](https://www.datalensai.in/glossary/breakeven-roas): Breakeven ROAS is the minimum ROAS an ad campaign must achieve to cover its own advertising and product costs without losing money.
- [MER (Marketing Efficiency Ratio)](https://www.datalensai.in/glossary/mer): MER is total company revenue divided by total marketing spend across all channels, measured as a holistic, attribution-free efficiency metric.
- [Blended CAC](https://www.datalensai.in/glossary/blended-cac): Blended CAC is the total acquisition spend across all marketing channels divided by the total number of new customers acquired in the same period.
- [Channel CAC](https://www.datalensai.in/glossary/channel-cac): Channel CAC is the acquisition cost for a single channel, calculated using only that channel's spend and self-reported conversions.
- [LTV:CAC Ratio](https://www.datalensai.in/glossary/ltv-cac): The LTV:CAC ratio compares the lifetime gross value of a customer to the cost of acquiring them, indicating long-term business viability.
- [CAC Payback Period](https://www.datalensai.in/glossary/payback-period): CAC payback period is the number of months required for a customer's cumulative gross profit to equal their initial acquisition cost.
- [AOV (Average Order Value)](https://www.datalensai.in/glossary/aov): AOV is the average dollar amount spent by a customer whenever they place an order.
- [Contribution Margin](https://www.datalensai.in/glossary/contribution-margin): Contribution margin is revenue remaining after deducting all variable costs associated with producing, packaging, shipping, and processing an order.
- [CPA (Cost per Acquisition / Action)](https://www.datalensai.in/glossary/cpa): CPA is the average advertising cost required to generate one specific conversion event, such as a lead, trial signup, or purchase.
- [CPC (Cost per Click)](https://www.datalensai.in/glossary/cpc): CPC is the average amount paid to an ad platform each time a user clicks on an advertisement.
- [CPM (Cost per Mille)](https://www.datalensai.in/glossary/cpm): CPM is the cost of displaying an ad one thousand times (mille is Latin for thousand).
- [CTR (Click-Through Rate)](https://www.datalensai.in/glossary/ctr): CTR is the percentage of people who clicked an ad after seeing it on their screen.
- [Frequency (Ad Frequency)](https://www.datalensai.in/glossary/ad-frequency): Frequency is the average number of times each reached person saw your ad over a given period — impressions divided by unique people reached.
- [RTO (Return to Origin)](https://www.datalensai.in/glossary/rto): RTO is an order that was shipped but never successfully delivered, and was returned to the seller — the revenue is reversed and the shipping cost is paid twice.
- [COD (Cash on Delivery)](https://www.datalensai.in/glossary/cod): Cash on delivery is a payment method where the customer pays the courier at the doorstep rather than online at checkout, so the order carries no payment until delivery succeeds.
- [Attribution Window](https://www.datalensai.in/glossary/attribution-window): An attribution window is the allowable timeframe between when a user interacts with an ad and when a resulting purchase is credited to that ad.
- [View-Through Conversion](https://www.datalensai.in/glossary/view-through-conversion): A view-through conversion credits an ad when a user saw the ad, did not click it, but later visited the website and completed a purchase within a short window.
- [Conversion Lag](https://www.datalensai.in/glossary/conversion-lag): Conversion lag is the time delay between an initial ad click and the final completed purchase, which makes recent-day campaign metrics provisional.
- [Incrementality](https://www.datalensai.in/glossary/incrementality): Incrementality measures the true causal sales an ad generated above and beyond what would have happened naturally without any advertising.
- [UTM Parameter](https://www.datalensai.in/glossary/utm-parameter): UTM parameters are simple text tags appended to a URL that identify the source, medium, and campaign name when a visitor clicks a link.
- [Modeled Conversion](https://www.datalensai.in/glossary/modeled-conversion): A modeled conversion is a conversion an ad platform reports without having observed it, estimated statistically from the conversions it could observe.
- [Bytes Scanned (Query Data Volume)](https://www.datalensai.in/glossary/bytes-scanned): Bytes scanned is the physical volume of data a database or cloud warehouse reads from storage to execute a query, determining cost and speed.
- [Partitioned Table](https://www.datalensai.in/glossary/partitioned-table): A partitioned table is a database table physically divided into segments by a specific column (usually a date), allowing queries to read only relevant segments.
- [Schema Mapping (Semantic Context)](https://www.datalensai.in/glossary/schema-mapping): Schema mapping is the process of providing explicit semantic definitions, relationships, and business logic for database tables and columns so users and AI agents query them correctly.
- [Text-to-SQL (Natural Language Querying)](https://www.datalensai.in/glossary/text-to-sql): Text-to-SQL is the AI capability of translating everyday conversational questions into executable, accurate database queries.
- [Data Freshness & Sync Latency](https://www.datalensai.in/glossary/data-freshness): Data freshness is the elapsed time between when an event occurs in the real world and when it becomes available to query in your database or warehouse.
- [Compute Units / Slots](https://www.datalensai.in/glossary/slot): A compute slot or processing unit is a virtual CPU and memory slice allocated by a database engine to execute query operations.
- [Semantic Layer](https://www.datalensai.in/glossary/semantic-layer): A semantic layer is a version-controlled definition of your business metrics and entities — what "revenue", "active customer" or "new order" mean in SQL — that every query and every tool resolves against.
- [Click ID (GCLID / FBCLID / WBRAID)](https://www.datalensai.in/glossary/click-id): A click ID is a unique, single-use identifier an ad platform appends to the landing-page URL when a user clicks an ad (gclid for Google, fbclid for Meta, wbraid/gbraid for iOS, msclkid for Microsoft, ttclid for TikTok).
- [Offline Conversion Import](https://www.datalensai.in/glossary/offline-conversion): An offline conversion import sends outcomes a platform could not observe itself — closed-won deals, delivered-and-paid COD orders, store sales — back into Google or Meta, matched to the original click via click ID or hashed identity.
- [ATT, SKAN & Privacy Sandbox](https://www.datalensai.in/glossary/skan-att): ATT (App Tracking Transparency) is Apple's permission prompt for cross-app tracking; SKAN (SKAdNetwork, evolving into AdAttributionKit) is the sparse, delayed, aggregated signal Apple returns instead of identity; the Privacy Sandbox is Google's equivalent transition for web and Android measurement.
- [Reporting Timezone & Currency Normalisation](https://www.datalensai.in/glossary/reporting-timezone): A reporting timezone (and currency) is the single declared timezone and money unit all reports are expressed in, with every source converted at query time from its native timezone and currency before any date truncation or aggregation.
- [Deduplication (Deduping)](https://www.datalensai.in/glossary/deduplication): Deduplication is reducing multiple rows that describe the same business reality — retried webhooks, double-fired pixels, overlapping backfills — to exactly one canonical row per business key, typically via ROW_NUMBER() partitioned by order_id or event_id.
- [Freshness Check (Data Validation Query)](https://www.datalensai.in/glossary/freshness-check): A freshness check is a scheduled validation query measuring whether reporting data arrived, arrived whole, and agrees with an independent system — newest-timestamp lag, volume and null-rate bands, and warehouse-vs-source reconciliation.
- [Cohort Payback Curve](https://www.datalensai.in/glossary/cohort-payback): A cohort payback curve plots cumulative contribution per acquired customer against months since acquisition, one line per acquisition cohort. Payback is the month the curve crosses CAC.
- [Discount-Adjusted ROAS](https://www.datalensai.in/glossary/discount-adjusted-roas): Discount-adjusted ROAS computes return on net realised revenue and true variable costs during promotional periods, then sets the result against the post-sale demand hole — pricing a sale instead of just recording its revenue.
- [Golden Dataset (AI Eval Set)](https://www.datalensai.in/glossary/golden-dataset): A golden dataset is a version-controlled set of question–SQL–answer triples with hand-verified correct results, used to score an AI analyst's accuracy on your own schema and definitions before and after any model, prompt or schema change.
- [Dynamic Baseline (Anomaly Detection)](https://www.datalensai.in/glossary/dynamic-baseline): A dynamic baseline is the expected value of a metric for a given moment — same-weekday trailing median, trend-adjusted, season- and event-aware — plus a tolerance band. Alerts fire on deviation from expectation rather than on crossing a fixed line.
- [Least-Privilege Data Access (for AI)](https://www.datalensai.in/glossary/least-privilege-access): Least-privilege data access gives an AI tool the smallest data scope that answers the question — curated views at fixed grains instead of raw tables, tokenised identifiers instead of raw PII, windowed history, and byte caps — enforced in database roles, never in prompt text.
- [Impression Share (IS)](https://www.datalensai.in/glossary/impression-share): Impression share is the percentage of eligible ad auctions in which your ad actually showed. The missing share splits into lost-to-budget (skipped auctions — needs money) and lost-to-rank (lost auctions — needs bids, quality or creative).
- [Creative Fatigue](https://www.datalensai.in/glossary/creative-fatigue): Creative fatigue is response decay within a fixed audience: the same people see the same ad repeatedly and click and convert less each time, while delivery economics (CPM, reach) stay roughly stable.
- [Search Term (vs Keyword)](https://www.datalensai.in/glossary/search-term): A search term is the exact query a user typed; the keyword is what the advertiser bid on. The gap between them — widened by broad match and close variants — is mined weekly for negative keywords (stop waste) and exact-match promotions (scale proven intent).


## Free tools

- [Budget Allocator](https://www.datalensai.in/tools/budget-allocator): Split a fixed monthly budget across Google, Meta and retention — with diminishing returns — and see which shift earns the next rupee. A what-if sandbox for budget season.
- [CAC Payback Simulator](https://www.datalensai.in/tools/cac-payback-simulator): Drag CAC, ARPU and churn and watch the payback curve bend — the month you break even, 24-month LTV, and whether the unit economics survive contact with reality.
- [ROAS Drop Doctor](https://www.datalensai.in/tools/roas-drop-doctor): ROAS fell and nobody agrees why. Answer 5 questions about what moved — CPM, CTR, CVR, AOV, frequency — and get a ranked diagnosis with a fix checklist.
- [UTM Builder + Governance Checker](https://www.datalensai.in/tools/utm-builder): Build clean campaign URLs with live validation — then paste existing URLs to score their naming before bad parameters pollute another quarter of attribution.
- [A/B Test Significance Playground](https://www.datalensai.in/tools/ab-significance): Enter visitors and conversions for control and variant — get verdict, confidence, lift bounds, and the sample size you actually needed. No more calling tests at 60/40.
- [Frequency & Fatigue Visualizer](https://www.datalensai.in/tools/frequency-fatigue): Drag impressions, audience size and creative decay to see when frequency turns from reach into waste — and what cap and refresh cadence that implies.
- [BigQuery Cost Estimator](https://www.datalensai.in/tools/bigquery-cost-estimator): Estimate what a query will cost before you run it — from validator bytes, with a table-scan simulator and a paste-your-query cost audit. On-demand BigQuery pricing, made concrete.
- [Breakeven ROAS Calculator](https://www.datalensai.in/tools/breakeven-roas): Enter your gross margin to find the minimum ROAS at which a campaign stops losing money — and the target ROAS at a chosen profit goal.
- [Blended CAC Calculator](https://www.datalensai.in/tools/blended-cac): Total spend across every channel, divided by total new customers — the acquisition cost number that reconciles with what you actually spent.
- [MER Calculator](https://www.datalensai.in/tools/mer-calculator): Total revenue divided by total marketing spend — the attribution-agnostic efficiency number, plus its contribution-margin-adjusted variant.
- [LTV:CAC Ratio Calculator](https://www.datalensai.in/tools/ltv-cac-ratio): Compare customer lifetime value to acquisition cost, and see the payback period alongside the ratio — the ratio alone hides how long payback actually takes.
- [Budget Pacing Calculator](https://www.datalensai.in/tools/budget-pacing): Project whether a campaign will land under, on, or over its monthly budget, based on spend-to-date and days elapsed.


## Other pages

- [FAQ](https://www.datalensai.in/faq)
- [Changelog](https://www.datalensai.in/changelog)
- [About](https://www.datalensai.in/about)
- [Privacy](https://www.datalensai.in/privacy)
- [Terms](https://www.datalensai.in/terms)