Question 1

What Lago data can Polytomic sync?

Accepted Answer

The billing object model, broadly. Customers, subscriptions, plans, invoices, credit notes, wallets and wallet transactions, and billable metrics, plus add ons, applied coupons, coupons, billing entities, daily usage, entitlement features, fees, payments, plan and subscription entitlements, and taxes. One notable gap: raw usage events are not exposed as an object. If you need event level metering data rather than aggregated usage, that is not available through this connector, though daily usage covers most consumption reporting needs.

Question 2

How does incremental syncing work for Lago?

Accepted Answer

Only daily usage reads incrementally, and it does so carefully. Polytomic calls the usage analytics endpoint per subscription at daily granularity, checkpoints on the end of the period it completed, and then rewinds the start date by two days on the following run. That rewind exists because usage data settles late, and re-reading a small overlap is much safer than assuming yesterday's numbers were final. Every other object is a full paginated read on each ETL execution, which is manageable given billing record volumes.

Question 3

Does this work with a self hosted Lago instance?

Accepted Answer

Not currently. The API base URL is fixed to Lago Cloud rather than being a configurable connection setting, and the connection accepts only an API key. Since Lago is open source and self hosting is common, this is worth checking before you plan around the connector. If you self host and need this, it is a small change to the connector rather than a fundamental limitation, so it is worth raising with us.

Question 4

Can I build MRR and revenue reporting from this?

Accepted Answer

Yes, and doing it in your data warehouse rather than in a billing tool is usually the point. Subscriptions and plans give you the recurring commitment, invoices and fees give you what was actually billed, payments and credit notes reconcile what was collected, and daily usage explains consumption driven variance. Because it all lands next to your product and CRM data, you can segment revenue by cohort, plan, or account owner using definitions your finance and analytics teams agree on rather than whatever the billing tool reports natively.

Question 5

Can Polytomic write data back into Lago?

Accepted Answer

No, Lago is a source only connector, so ETL out of Lago is supported but writes into it are not. In practice the valuable direction is outward: getting billing data somewhere it can be joined and modeled. From there the same platform runs reverse ETL to push the results elsewhere, so a plan tier or overdue invoice flag computed from Lago data can be written onto a Salesforce account or a HubSpot company without a second tool.

Lago

Perfect pairings

Full billing object model

Incremental daily usage

Metering configuration

Example workflows

What you can sync

From Lago

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Lago in minutes

More integrations beyond Lago