Understanding historical imports (is_backfill)
Why leads/deals imported more than 7 days after their actual creation date are flagged as historical imports and excluded from current period metrics.
In one sentence
When Metrikia ingests data more than 7 days after its actual creation date (on the CRM or Stripe side), the row is flagged is_backfill = true and excluded from current-period dashboard metrics by default.
Why
Without this rule, a bulk historical CRM import inflated the "Leads this week" counter with leads that were 6 months old. Period-over-period comparisons became meaningless. The banner "X% of leads are historical imports" triggers above 80%.
Source flagging logic
| Source | Logic |
|---|---|
| HubSpot CRM sync | now - hubspot_createdate > 7 days |
| Stripe Checkout reconciliation | always false (current event) |
| AI Import bulk CSV | always true (bulk historical) |
| API POST /leads manual | false (current event) |
| Metrikia pixel touchpoint | false (current event) |
See full history
The dashboard toggle "Include historical imports" (coming) switches to full-history view. Default view is filtered.
Re-flag existing data
For pre-existing rows ingested before this rule was enforced, contact Metrikia support. An administrator will re-run the flagging process on your account. The system automatically marks the relevant records without affecting recent imports.
Common issues
- "My dashboard shows 0 leads even though I imported 1000": they are probably all flagged
is_backfill. Toggle full-history to confirm. - "Recent leads created today still missing": if your CRM reports a past creation date for this lead, it will be flagged as historical. Contact support to investigate the specific case.
Previous guide
Understanding appointment status
Next guide
Understanding click-id resolution (Meta fbclid, Google gclid, TikTok ttclid)
To go further, check out our blog, the documentation or contact support.