Dana unifies Meta, Google, TikTok, Shopify, Klaviyo, and GA4 into one reconciled number. Every metric carries provenance. Every gap is flagged before it reaches a decision.
Three platforms. Three numbers.Nobody knows which one is right.
Every platform reports differently.
Meta says 847 conversions. Google says 1,102. GA4 says 1,876. Shopify shows 1,243. Variance runs 30 to 70 percent across sources, and the loudest dashboard wins the meeting.
Pipelines break quietly.
An API drops at 2 AM. A pixel breaks on mobile. A UTM convention shifts mid-campaign. Most teams notice three to seven days later, after the decisions have already been made.
Reconciliation eats the week.
Ten to fifteen hours per week pulling, cleaning, matching, and rebuilding reports across four platforms. By the time the spreadsheet is finished, the numbers are already stale.
Models train on noise.
Forecasts, attribution, scenario tests are all only as good as the inputs. Dirty data flowing into Felix, Parker, and Sam compounds every miss they make.
What Dana ships
Five capabilities.One reconciled data layer.
Each capability serves a specific job: unify the sources, reconcile the math, monitor the pipes, normalize the schema, and feed clean data to the rest of the workforce.
Single source of truth
Six-plus data sources unified into one reconciled view, with full provenance on every number.
Meta, Google, TikTok, Shopify, Klaviyo, GA4 ingested via OAuth
Every metric tagged with source, pull time, and reconciliation hash
Refresh cadence configurable per source, default every 6 hours
Example. 987 ad-driven conversions traced to 412 Meta + 318 Google + 257 organic
Daily conversion reconciliation
Cross-checks platform-reported conversions against Shopify orders every cycle, with the gap explained line by line.
Order-level matching on order_id, timestamp, UTM
View-through and cross-device duplicates removed
Discrepancy report routed to Slack with attributed root cause
Example. Meta reported 847; 435 view-throughs removed; 412 verified against Shopify
Tracking-health monitoring
Watches every pixel, server-side event, and API connection. Surfaces breaks within minutes, not days.
Meta Pixel, GA4, server-side, and platform API health
Pattern-break detection on event volume and UTM shape
Alert lands before the morning report shows zeros
Example. Meta Pixel mobile failure flagged at 2:14 AM, traced to a site deploy
Schema normalization
Reconciles event names, currencies, timezones, and naming conventions across platforms so downstream models read one shape.
Meta Purchase, Google conversion, TikTok complete_payment unified
Multi-currency converted to business currency at daily FX
Timezones aligned to one business clock before any math runs
Example. PST, UTC, and EST source feeds normalized before nightly retrains
Workforce-aware
Dana is the data layer. Felix, Parker, Sam, Maya, Olivia, and Dex all read from the same reconciled truth.
Felix trains forecasts on deduped, verified conversions
Parker validates attribution against Shopify-matched orders
Sam, Olivia, Maya, and Dex pull from one shared schema
Example. One reconciliation cycle feeds six agents, no manual exports
A typical day
What Dana doeswhile the dashboards lie.
One operating day, hour by hour. Specific numbers vary by account.
Mon · 2:14 AM
Flagged
Meta Pixel fires zero events for 12 minutes on mobile Safari. Dana detects the volume break and pages on-call before the morning standup.
Mon · 4:00 AM
Synced
Pulls fresh data from Meta, Google, TikTok, Shopify, Klaviyo, and GA4. Every record stamped with source, pull time, and API version.
Normalizes timezones (PST, UTC, EST) and currencies (USD, EUR, GBP) to business clock and base currency. Schema written to shared layer.
Mon · 5:14 AM
Delivered
Feeds reconciled inputs to Felix's nightly forecast retrain and Parker's attribution checks. One shared schema, zero export friction.
Mon · 9:47 AM
Flagged
UTM convention drift detected: half of last week's paid social campaigns landing in Other. Pattern flagged with 14-day diff.
Mon · 10:21 AM
Patched
Server-side event dedupe patches the Add to Cart double-fire on mobile checkout. Provenance log records the fix and the prior state.
What's underneath
Real reconciliation pipelines.Not a dashboard skin.
Dana runs on purpose-built reconciliation pipelines: per-source ingestion, schema normalization, order-level matching, and provenance for every number that leaves the system.
Reads from
Shopify orders, Klaviyo events, GA4 sessions, plus Meta, Google, and TikTok ad platforms via OAuth. No warehouse copy, no nightly dump.
OAuth-based ingestion, refresh cadence per source
Reports to
Sheets for reconciled tables and provenance audit logs. Notion for the long-form data-quality reports. Format adapted per surface.
Reconciled tables refreshed every 6 hours
Collaborates with
Felix trains on reconciled inputs. Parker validates conversions against Shopify. Sam grounds scenarios on verified baselines. Maya, Olivia, and Dex read the same shared schema.
One shared data layer across all six other agents
Built on
Per-source ingestion adapters, schema normalization across platform event taxonomies, order-level matching on order_id and UTM, and provenance hashing on every record.
Reconciliation pipelines with full audit trail
Ready when you are
See Dana reconcile your accounts, or talk to us about your data stack.
The pilot connects your platforms in under five minutes. The first reconciliation cycle finishes within 24 hours, with full provenance from day one.