Every marketing team has data that lives outside the platforms. Offline conversion logs. Budget allocation sheets. CRM pipeline exports. Call tracking results. Custom KPI targets maintained by hand in a spreadsheet someone updates every Monday.
That data matters — often more than what the ad platforms report. A Google Ads CPA of $42 looks fine until you factor in the offline conversions from a call tracking sheet and realize the true CPA is $28. A campaign that looks underperforming in Meta's dashboard is actually your best channel once CRM close rates are included.
The problem is getting that spreadsheet data into the same conversation as your platform data. Until now, that meant exporting CSVs, pasting into slides, and building manual reconciliation tabs. LDOO treats Google Sheets as a first-class data source.
What connecting a spreadsheet unlocks
When you connect a Google Sheet to LDOO, the data syncs into the same normalized store as GA4, Google Ads, Meta Ads, Search Console, and every other source. Standard metrics — spend, clicks, conversions, revenue, sessions — are auto-detected from the column headers and can be asked about. Every other column is kept with its row.
No column mapping UI. No widget configuration. No drag-and-drop report builder. Connect the sheet, wait for the sync, and ask a question.
"What is our true CPA including offline conversions from the call tracking sheet?"
LDOO reads the ad platform data and the spreadsheet data together and returns one answer:
Google Ads reports a CPA of $42.30 based on 186 online conversions. Your call tracking sheet logged 94 additional offline conversions over the same period. Including both, the blended CPA is $28.40 — 33% lower than platform-reported. The Brand Search campaign drives 61% of offline conversions.
That is the answer your team would have spent 30 minutes assembling across three tabs. LDOO produces it in seconds.
Multiple spreadsheets per client
Most teams track more than one dataset in spreadsheets. A single client might have a budget tracker, a call log, and a CRM export — each in its own file.
LDOO supports connecting multiple spreadsheets per client. Each one syncs independently on your plan's schedule, and the data is queryable together. LDOO records which spreadsheet each row came from, and questions combine all of a client's sheets.
Add or remove sheets any time from the integrations page.
What happens to your columns
When LDOO syncs a spreadsheet, it reads the header row and auto-maps columns it recognizes:
- Date columns — date, day, period
- Cost metrics — spend, cost, ad spend, budget
- Performance metrics — clicks, impressions, conversions, leads, orders
- Revenue metrics — revenue, sales, income
- Efficiency metrics — CPA, CPC, CTR, and ROAS, calculated from the spend, click, conversion, and revenue columns
- Web analytics — sessions, users, bounce rate, page views
Columns that don't match a known metric — "Customer Segment", "Lead Score", "Sales Rep" — are kept as custom fields with each row.
There is no manual mapping step. LDOO detects what it can and preserves everything else.
Cross-source questions that require spreadsheet data
The real value is in questions that span platforms and spreadsheets:
Budget pacing. "Are we on track against budget this quarter?" — Compares actual spend from Google Ads and Meta against the budget target set for the client in LDOO.
True CPA with offline conversions. "What is our blended CPA including offline sales?" — Adds offline conversions from your call tracking or CRM sheet to the platform conversions.
CPA targets. "Is Verde Studio on its CPA target this month?" — Compares actual CPA from the ad platforms against the target set for that client.
Lead attribution. "Which campaigns drove the most leads?" — Combines ad platform data with a lead log whose first column is the campaign and which has a Leads column.
Each of these would take 15-40 minutes to answer manually — pulling data from two or three sources, pasting into a comparison tab, calculating the delta, and writing the narrative. LDOO does it in one question.
What format does the spreadsheet need
A header row and data rows. That is the minimum requirement. LDOO handles the rest.
Native Google Sheets and uploaded CSV files work directly. For Excel (.xlsx) files, open them in Google Drive and save as a Google Sheet first — the sync uses Google's Drive API, which requires the native format.
Dates can be in ISO format (2026-05-15), US format (05/15/2026), or even Excel serial numbers (46162). LDOO's parser handles all three. If a date column is missing, rows are dated to the sync date.
From spreadsheet question to client report
Once you have a cross-source answer that includes spreadsheet data, it flows into reports the same way any other answer does. One click turns the answer into a branded PDF. The report includes the AI-generated narrative, comparison data, and recommendations — with spreadsheet rows feeding the narrative alongside platform data. Client portals show the platform sources.
For teams that maintain budget trackers or offline conversion logs, this means the monthly report can finally include the numbers that matter most — without a manual reconciliation step.
Connect Google Sheets to LDOO and ask your first cross-source question.
