# Google LSA Billing Is a Temporal Data Problem: Why Historical Configuration Matters

DevFeed: [Google LSA Billing Is a Temporal Data Problem: Why Historical Configuration Matters](<https://devfeed.tech/articles/google-lsa-billing-is-a-temporal-data-problem-why-historical-configuration-matters-114854.md>)

Original publisher: [Read original article](<https://hackernoon.com/google-lsa-billing-is-a-temporal-data-problem-why-historical-configuration-matters?source=rss>)

Author: Mayur S

Published: 2026-11-03T11:38:44Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [Temporal data](<https://devfeed.tech/topics/temporal-data.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [audits](<https://devfeed.tech/tags/audits.md>), [billing](<https://devfeed.tech/tags/billing.md>), [bitemporal-modeling](<https://devfeed.tech/tags/bitemporal-modeling.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-modeling](<https://devfeed.tech/tags/data-modeling.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [data-warehouse](<https://devfeed.tech/tags/data-warehouse.md>), [database](<https://devfeed.tech/tags/database.md>), [deduplication](<https://devfeed.tech/tags/deduplication.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event](<https://devfeed.tech/tags/event.md>), [event-sourcing](<https://devfeed.tech/tags/event-sourcing.md>), [google](<https://devfeed.tech/tags/google.md>), [google-ads](<https://devfeed.tech/tags/google-ads.md>), [google-local-service-ads](<https://devfeed.tech/tags/google-local-service-ads.md>), [google-lsa](<https://devfeed.tech/tags/google-lsa.md>), [lead](<https://devfeed.tech/tags/lead.md>), [local-service-ads](<https://devfeed.tech/tags/local-service-ads.md>), [models](<https://devfeed.tech/tags/models.md>), [october-2026-lsa-update](<https://devfeed.tech/tags/october-2026-lsa-update.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [temporal-data](<https://devfeed.tech/tags/temporal-data.md>)

## AI overview

LSA billing audits depend on reconstructing the configuration and evidence around a lead when it occurred, not just inspecting current settings. The article recommends preserving call, configuration, lead-status, and billing records as immutable events; keeping event, ingestion, processing, and evaluation times distinct; versioning configuration with valid and transaction time; and linking records while marking inferred matches and confidence. Reconciliation should retain status changes, handle late arrivals and duplicates, and avoid inventing history when a source exposes only current status. Before migration, preserve available campaign reports and distinguish them from customer lead records. These methods make agency evidence reproducible, but do not establish what Google's internal systems used or reveal its undisclosed decision logic; audits should state gaps and limits.

## Source excerpt

Google LSA billing depends on historical events and configuration. Learn how event sourcing and temporal data models improve lead audits.