Chronometrica vs XTech for a Google Ads Creative Library

Choose by the report’s required output

The buyer need behind this comparison is specific. A public post requested reports for four competitors, supplied Meta and Google library links, and asked about creative volume and variations. This article covers the Google creative inventory part of that request. The named Actor comparison is our editorial choice. Public buyer request.

A creative library is a set of saved creative records with source links, available assets, and collection context. It lets another person inspect the public evidence behind a report.

For this decision, compare the rules for saved records and the available collection inputs.

These product facts come from the dated documentation check. Chronometrica documentation, XTech documentation.

Chronometrica fits a library that requires reviewable assets and a fixed variation structure. Its stated acceptance rule directly supports that need. This recommendation concerns its output contract: the rules that define a saved record. It does not establish better speed, accuracy, coverage, or reliability.

Write your required record before choosing the collector. This makes the decision easier to review. It also prevents a large result count from hiding a missing field that the report needs.

Understand what Chronometrica accepts

Chronometrica documents a useful-creative rule. It saves a creative row when public media or a usable preview is available. If neither is available, it documents no paid metadata-only creative result. Metadata means descriptive information about a creative, without the usable asset itself. Chronometrica documentation.

That rule matters when the report must show the creative. A record can contain useful descriptive information but still fail an asset review. The collector’s acceptance rule and your report’s acceptance rule should agree.

The documented row keeps creative identity, `mediaUrl`, `previewUrl`, `variationCount`, `variations`, the requested region, platform and format, and `observedAt`. Each attached variation has `mediaUrl`, `previewUrl`, `width`, and `height`. The documentation also defines missing-value rules and row status. Chronometrica output documentation.

Use these fields for separate purposes. Creative identity tells you which creative the row represents. Media and preview links let you inspect it. Variation fields describe its attached versions. Requested filters show what you asked the collector to search. `observedAt` records when the observation was made.

A preview can satisfy the documented acceptance rule. If your project requires a direct media file, state that stricter requirement before collection. A usable preview alone would not meet it.

Keep unknown values as unknown values. An unknown width is not a width of zero. An absent media link does not become a direct asset link because a preview exists. The reviewer must be able to see what information is available.

Check the input limit without assuming a total library limit

Before choosing a tool, write down the targets, requested filters, and required volume. State whether the report needs a sample or all results in its declared scope.

The checked Chronometrica input schema accepts between 1 and 100 entries in `targets`. It permits `maxItems` from 1 to 5,000. The supplied settings checked for this article use `region: "US"`, `platform: "ALL"`, and `adFormat: "ALL"`. This check does not establish support for other values. Chronometrica input schema.

The 5,000 maximum is a checked limit on the `maxItems` input. It does not establish a total library limit across separate collections. The supplied evidence also does not establish that several collections can produce a complete inventory above that limit.

If your requirement needs a `maxItems` value above 5,000 in one collection, Chronometrica does not meet that requirement under the checked schema. Do not silently replace that requirement with a smaller sample. Do not assume that adding targets removes the input limit.

For a broader all-results requirement, the input limit alone cannot settle whether the tool meets the job. You need evidence that the collection method can cover the required result set. This comparison provides no such completeness test.

A small sample can still support a review of visible creative patterns. Label it as a sample. Requested filters show the search scope, but they do not prove that every eligible creative was found.

Use a small acceptance check before building the library

The first check should answer one question: does the saved output meet the report’s rules? A small collection can help you inspect field structure, source links, and counting units. It cannot prove complete coverage.

1. Match each competitor to the intended advertiser or domain. Record the resolved advertiser beside the original target. Confirm that the records belong to the intended business. Declare the requested region, platform, format, and any source date values used in the report.
2. Choose the Actor against written acceptance rules. State whether a usable preview is enough or whether direct media is required. Define the variation fields you need. Check the region and surface controls against the report’s scope. Separate required fields from optional details.
3. Inspect the actual input and start small. Use one target and a small shared cap for an initial comparison. Inspect each Actor’s own settings. Do not assume that one Actor’s field names apply to the other.
4. Review saved rows and target outcomes. Check creative identity, usable media or preview, attached variations, and missing values. Keep skipped or unusable counts where available. Record a source error as a source error. An unresolved target outcome does not prove that the advertiser has no ads.
5. Build the library with source and observation context. Save the source or preview link, requested filters, and `observedAt` with each accepted creative. Add an accept or review reason. Compare visible creative patterns within that declared scope.

Chronometrica provides a public creative-library Task. A Task is a saved input preset. Use it as a starting point, then inspect its actual settings before a run. A saved receipt confirmed a public HTTP 200 response, which means the page was available at that check. It did not confirm the current saved input. Creative-library Task.

The following input passed a local check against the cached public JSON Schema. A JSON Schema defines allowed input fields and values. All supplied field names exist in that schema. This is a check of input structure, not proof that the live source will return results.

{
  "targets": [
    "nike.com"
  ],
  "region": "US",
  "platform": "ALL",
  "adFormat": "ALL",
  "includeDeliveryDetails": false,
  "maxItems": 3
}

Replace `nike.com` with your intended public target. The domain is an input example, not a collected result. The value `3` sets a small cap for the first review. No run was made for this article. Chronometrica input documentation.

The example sets `includeDeliveryDetails` to `false`. If your report needs delivery details, inspect their documented meaning before changing that setting. Extra detail should answer a defined report question. It should not change the unit you count.

After review, decide whether the accepted rows contain the fields and evidence your report requires. Resolve any missing requirement before expanding collection. More records cannot repair a mismatch between the saved record and the required report.

Count creatives and variations as separate units

The following example is fictional. It is not an Actor test, a live dataset, a buyer quotation, or a measured cost result.

Suppose a source check finds three candidate creative identities:

• Creative A has three usable variations.
• Creative B has one usable preview variation.
• Creative C has metadata but no usable public media or preview.

Under Chronometrica’s declared acceptance rule, A and B qualify as useful creative rows. C does not qualify. Keep C in the skipped or unusable accounting. Do not invent an asset for it.

The arithmetic uses two separate units:

• Three candidate identities minus one unusable candidate equals two saved creative rows.
• Three variations plus one variation equals four attached variations.

The fictional report therefore contains two accepted creatives with four attached variations. Two creatives are not four ads, four campaigns, or four measured outcomes.

A clear summary would state that this fictional check accepted two creative identities with four attached variations. It would also state that one candidate lacked usable public media or a preview. Both facts matter when the reader reviews the count.

The skipped candidate does not prove a collection defect. In this example, its exclusion follows the acceptance rule. Its exclusion also does not prove that the advertiser has no creative. The candidate exists in the example, but it has no usable asset.

Apply the same counting rule to every competitor in the report. Comparing one advertiser’s variation count with another advertiser’s creative count would use different units. Keep both totals if both help the reader, and label each total clearly.

Keep the report open to source review

Use a library record that gives the reviewer enough information to inspect each decision. Include the resolved advertiser, creative identity, source or preview link, available variations, requested filters, `observedAt`, and the accept or review reason.

Keep target outcomes beside the library. A target with no accepted rows needs an explanation. Possible outcomes include no usable result in the checked scope, an unresolved advertiser match, or a source problem. Preserve the known outcome. Do not fill gaps with assumptions.

Source links and observation dates also help when later collections differ. Compare targets, filters, observation times, and acceptance rules before interpreting a changed count. The count alone does not explain the change.

The existing guide, How to Export Google Ad Creatives and Keep Their Source Evidence, covers the wider library method. Use this named Actor comparison to choose the collector and acceptance rule. Use that guide to organize the resulting evidence.

Do not add inferred performance fields to the library. Public creatives do not verify spend, sales, conversion rate, audience success, or strategy success. A visible message supports a description of that message. It does not establish the business result behind it.

This limit matters for the original buyer need. A creative inventory can support the creative-volume and variation portion of a report. It cannot, by itself, answer which competitor’s ads succeed or why they succeed.

Keep shown dates and billing claims within their meaning

Keep public first-shown and last-shown values within their stated source meaning. A long span between those dates does not prove continuous delivery, high spend, or strong results. See how to read ads shown dates before using those values in a comparison.

Apply the same rule to delivery details. Preserve their published meaning. Do not turn a public date span into a sales estimate or an unsupported account of campaign strategy.

Chronometrica’s useful-row rule is a documented acceptance and billing rule. It is not a measured cost advantage. Chronometrica documentation.

XTech also excludes empty searches and source errors from paid creative rows. No missing-preview defect or useless-row charge is established here. XTech documentation.

No matched run or price test supports a claim that one tool costs less. If cost will decide the purchase, check current billing units against the same agreed collection scope. Keep that cost check separate from the documented output fit assessed here.