Reuse report work

Good Report setups and report blocks are worth reusing. If you have already invested time into a useful report design, Keytiles can help you turn that work into a starting point for the next setup or query.

Content of this page

Reuse good report setups

Creating a useful Report setup can take time. Once a setup answers an important question well, you can reuse that work instead of starting from scratch.

  • Use Clone setup to create a new setup based on an existing one.
  • Use Export to file and Import from file to move a setup through a local JSON file.
  • Use Clone query when you want a similar report block inside the same setup.

This makes report setups reusable assets. A good campaign, referrer, or content performance setup can become the starting point for future reports in the same or another Data Container.

Report setups as reusable assets

A Report setup is not only a one-time configuration. It contains the report title, description, schedule, Integration settings, and the queries that define the report content.

If you invest time into selecting the right events, filters, breakdowns, sorting, schedule, and descriptions, that setup can be reused later. You can clone it, export it to a JSON file, or import it into another Data Container as a reviewed new setup draft.

Reuse is especially helpful when several Data Containers need similar reporting logic but different data, filters, or delivery settings.

Reuse the setup later

After a setup works well, reuse it. This is often better than rebuilding the same report from an empty setup.

  • Clone the setup when you want a similar setup inside Keytiles.
  • Export the setup to a JSON file when you want a portable copy.
  • Import a JSON file when you want to use an exported setup as the starting point for a new setup.

After importing or cloning, always review the setup before relying on it. Check events, filters, schedule, Integration settings, and query titles.

Reuse report block designs

If one report block is useful, you can often reuse its design. Clone the query when you want another similar block in the same Report setup.

After cloning a query, adjust only what should change: title, filters, breakdowns, or sorting. This is useful when several blocks should follow the same structure but answer slightly different questions.

Review before publishing the copied report

Reuse saves time, but copied setups and queries should still be checked. Values that made sense in one Data Container may not exist or may mean something different in another one.

  1. Generate a test report instance.
  2. Check whether selected events exist in the copied context.
  3. Review Include only filters such as campaigns, referrers, tags, content types, and content structure paths.
  4. Check schedule and Integration settings.
  5. Update titles and descriptions so readers understand the copied report.