GTM AIGTM AI

How to Review Source Health in the Collection Manager

Learn how to check which sources feed your GTM Context Graph and how complete the data is.

Andres PerezAndres PerezSenior Director, Product Management

Learn how to check which sources feed your GTM Context Graph and how complete the data is.

Overview

The Collection Manager lists every collection in your GTM Context Graph, such as accounts, contacts and opportunities. For each one it shows how many records have arrived, which connected sources they came from, how recently each source sent data, and how completely each field is filled. Use it to spot a source that has stopped sending data or a collection that is mostly empty.

The page is part of the GTM Context Graph section, so it is available when your organization has the GTM Context Graph and the Collection Manager turned on. Record counts, fill rates and source freshness come from the data your connected integrations have delivered.

Review the health of your collections

  1. In the left navigation panel, open the GTM Context Graph group and click Manager.
  2. Read the tiles under Your Context. Active collections counts the collections that have records, Records shows the total and how many sources it comes from, Fields shows the field total and how many are custom, and Needs attention shows how many collections have a stale source or low fill.
  3. Read the tiles under ZoomInfo Context for the datasets ZoomInfo manages for you. Active datasets counts the datasets, Records under management shows the total across the datasets that report one, and Fields says to open a dataset to see its fields. Needs attention shows a dash there, because the page cannot report it for ZoomInfo datasets.
  4. Click the Your Context tab to see only the collections your own sources feed, or ZoomInfo Context to see ZoomInfo-managed datasets. All shows both.
  5. Type in the Search collections and fields box to find a collection by its name, description or one of its fields.
  6. Click the Needs attention chip to list only collections with a stale source or low fill. Click it again to clear the filter. The No metrics chip lists collections that do not report volume or fill rate.
  7. Read the Status column for each collection.

What each status means

  • Healthy: every source has sent data in the last 24 hours and the average field fill is 40% or higher.
  • Stale source: at least one source has not updated any record in more than 24 hours. The row also says how many sources are behind.
  • Low fill: the average fill across the fields that can be measured is below 40%. Fields without a fill rate are left out of the average.
  • No metrics: the collection is not covered by volume and fill-rate reporting. This is a gap in what is measured and does not mean there is a problem with your data. Records, fill rates and source counts are reported for seven collections: accounts, contacts, opportunities, products, users, account contact roles and account team roles.
  • Metrics unavailable: the numbers could not be read this time. Try Refresh metrics.

A source that has never reported a record is not counted as stale. It appears as a collection with no sources instead.

Look at one collection in detail

  1. On the Collection Manager page, click a collection's row.
  2. Review the tiles at the top: Records, Sources, Sources behind and Average field fill.
  3. Click the Fields & fill rate tab to see each field with its type, origin (Standard or Custom) and fill rate. Click a field to see Fill by source, which shows each connected source, the vendor column mapped to the field and how often it arrives filled.
  4. Click the Sources tab to see each source with its instance, source object, record count, ZI match rate, Source updated and Graph updated times. A source with no update in 24 hours is marked Stale.
  5. To return to the overview, click the back link to Collection Manager at the top of the page.

The ZI match rate appears only for accounts and contacts. It shows how many records were matched to a ZoomInfo company or contact.

If a collection cannot be opened, the page says "Collection not found" or "Collection unavailable". Go back to the overview and try again in a moment.

Add a custom field to a collection

A collection whose field schema loaded shows a New field button at the top of its page. Custom fields can be edited or deleted later, and standard fields cannot.

  1. Open the collection from the Collection Manager page.
  2. Click New field at the top of the page.
  3. In the New custom field window, enter a Field name, choose a Type, and add a Description that says what the field holds and who writes it. The window previews the API name the field will get.
  4. Click Create field.

After a field is created, its type and API name cannot be changed. To change the rest, open the field's actions menu on the Fields & fill rate tab and click Edit field, then Save changes. To remove a custom field, open the same menu and click Delete field, then confirm in the Delete custom field window. Deleting a field removes everything stored in it and cannot be undone.

Add a source to a collection

  1. On the Collection Manager page, click Add source in the top-right corner. Or click Add source in the Sources cell of a collection that has no sources, or on the collection's own page.
  2. In the Add a source window, review the integrations tagged for the GTM Context Graph, or for the collection you chose.
  3. Click Open Integrations Hub to open the full list in a new tab and connect the source there.

Coverage of tagged integrations is still being filled in. If the window says no integrations are tagged, a vendor that can feed the collection may simply not be tagged yet, so open the Integrations Hub to see everything available. Volumes and fill rates appear after the first sync of a new source.

Refresh the numbers

  1. Click Refresh metrics in the top-right corner of the Collection Manager page.
  2. If a banner starts with "Some collection data could not be loaded", the numbers that depend on it show as unavailable. Click Refresh metrics to load them again.
  3. If a banner says "Could not refresh the collections. Showing the last loaded data.", the page is showing the last numbers it loaded. Click Retry to load them again.

A read that takes longer than 20 seconds is treated as failed, so a very large account can show Metrics unavailable until a retry succeeds. If a number is unknown, the page shows a dash and never a zero.

If you see an error

  • "Some collection data could not be loaded:" followed by the names of what failed (e.g., record counts, fill rates, the collection list or the field schema). Part of the page could not load, so the numbers that depend on it show as unavailable. Click Refresh metrics.
  • "Could not refresh the collections. Showing the last loaded data." The refresh did not finish, so the page kept the numbers it had. Click Retry.
  • "Collection not found" with "It may not exist in your graph, or it may have been removed." The collection in the link is not in your graph. Click the back link to Collection Manager and pick a collection from the list.
  • "Collection unavailable" with "Try again in a moment." The collection could not be opened. Wait a moment and open it again.
  • "Fields unavailable" with "This dataset's fields could not be loaded." or "This collection's field schema could not be loaded." The field list did not load. Wait a moment, then reopen the collection.
  • "Fill rates could not be loaded" or "Source metrics are unavailable". The collection's fill rates or source numbers did not load. Click Retry on the tab, or use Refresh metrics on the overview.
  • "Mapping could not be loaded" The vendor column for a source could not be read. Close the field and open it again.
  • "Could not load the integration catalogue" with "The Integrations Hub did not answer. Try again, or open it directly." The Add a source window could not list integrations. Close it and try again, or click Open Integrations Hub.
  • "Could not create the field. Try again." and "Could not save the field. Try again." The custom field was not saved. Click Create field or Save changes again.
  • "Could not delete the field. Try again." The custom field was not deleted. Click Delete field again.

Resources