Understanding "recent" vs "historical" in your dashboard | Guides
Beginner2 min

Understanding "recent" vs "historical" in your dashboard

Your "last 30 days" counters show leads, deals, and appointments Metrikia received, not their origin date in your CRM. Here is how both dimensions work.

Understanding "recent" vs "historical" in your dashboard

Why this distinction exists

When you connect a CRM (HubSpot, Pipedrive, Salesforce, etc.) to Metrikia, the integration imports all available history, sometimes years of leads and deals. Without care, this backfill would surface tens of thousands of records as "recent activity" on your dashboard, which makes no sense: those leads are not new to you, they are just new to Metrikia.

To solve this, Metrikia stores two dates on every lead, deal, and appointment:

FieldMeaningUsed by
created_atOrigin date on the source side (CRM, Stripe, Meta)Cohorts, attribution, long-term analyses
imported_atWhen Metrikia received the row"Recent" counters: last 30 days, alerts, anomalies

How your widgets behave

  • "Leads created in the last 30 days", "Appointments this week", "Deals closed this month" on the main dashboard filter on imported_at. This is what you expect: "what did my team generate recently".
  • Attribution cohorts, retention charts, customer journey keep using created_at, because we need to know when the customer actually started the journey.
  • Cash collected / closed_at on the pulse stays based on business close date, not import.

Concrete case: you just connected HubSpot

Before: You saw 102,000 leads "created in the last 30 days" while your team only generated 300 in that window. Total confusion.

After: The "last 30 days" counter shows 300. The 101,700 historical leads still live in the CRM, keep their original created_at, and appear in cohort / attribution analyses.

How to verify on a specific lead

  1. Go to /app/leads
  2. Click a lead to open the detail drawer
  3. You will see "Created on" (= created_at, source origin date) and "Received on" (= imported_at, Metrikia ingestion date)

For leads created directly inside Metrikia, both dates are identical. For leads imported from a CRM, "Received on" is the date your team connected the integration.

What if I still want to see the history?

Every analysis that needs the business dimension (attribution, cohorts, mROAS) keeps working on created_at. You lose nothing, you just have both dimensions side by side.

If you think a widget should switch from one dimension to the other, open a request in Ideas and Roadmap (/app/settings, feature-request section) with the widget name and expected behaviour.

Common issues

  • "My dashboard dropped to 0 after the CRM connection": it is probably the opposite. Before, your counters wrongly included the backfill. Now they reflect real recent activity. Check the trend over 7 days after the connection.
  • "I created a lead manually and it does not show on the pulse": check the creation actually happened in /app/leads. If it was an existing lead, it may have been marked as already imported (email/phone dedup).
  • "I want to change a widget dimension": Diana cannot do this for you. Open a request in Ideas and Roadmap.

To go further, check out our blog, the documentation or contact support.

Ready to take action?

Create your Metrikia account and apply this guide in minutes.