TraceParts Help Center TraceParts Help Center
  • EnglishSwitch to English
    • FrançaisSwitch to Français
    • DeutschSwitch to Deutsch
TraceParts Help Center TraceParts Help Center
TraceParts Help Center TraceParts Help Center
  • EnglishSwitch to English
    • FrançaisSwitch to Français
    • DeutschSwitch to Deutsch
loading
  1. Home
  2. (3D Product Catalog Solutions) TraceParts Analytics
  3. Report
  4. Scheduling
  5. Leads report
Updated on July 1, 2025

(3D Product Catalog Solutions) TraceParts Analytics

  • Interface
    • Menu
    • Change language
    • Sign out
  • Analytics views
    • Dashboard
    • Content of an analytical view
      • Segments
      • Charts
      • Date selector
      • Dimension
      • Table
      • Data manipulation
    • Overview
    • Custom view
  • Administration
    • Users activity
    • User management
      • Invite a user
      • Permissions by roles
  • Report
    • Download report
    • Scheduling
      • Synthesis
      • Leads report
      • List of recipients
  • Glossary
    • Glossary
  • Contact Support

Leads report

Estimated reading: 6 minutes

The leads report provides an in-depth insight into the leads that have performed an action on the user’s catalog(s).

You can obtain leads report by downloading or scheduling a report.

Creating the report schedule

To schedule a leads report, provide the information below:

First part: identity and content of the report

  • Identity of the report (A): name, description (not required), status
  • Content to be sent (B): add filters to one or more primary dimensions: CAD files, documents, requests for quotation, new users.
  • Format (C): the report may be downloaded in Excel or CSV format. Data can also be sent in a zip file.
  • Sending setting: users need to define the delivery settings by first selecting a delivery method by email or FTP (over a file server).

Second part : creating the report settings

Excluding email addresses and domains from your reports

When you set up a scheduled report, you can choose to exclude one or more:

  • Email addresses (D)
  • Email domain names (E)

For example: this feature can be useful if you want to prevent the report from being sent to colleagues with the same email domain name.

Sending the report by email (F)

This method can be used to schedule one or more deliveries that must at least include the following: a recipient (G), the time zone (H), a delivery frequency (I) and the report language (J).

Special case of "sending shared data"

When scheduling, you can choose the scope of the data to be included in the report by specifying:
• The recipient
• The “Catalog” filter (optional)
• The “EasyLink & TraceParts Publishing Network” filter

Default data scope rule :

If no filter is defined during the scheduling process, the following rule will be applied by default: only data common to the scope of the scheduler and the recipient will be sent.

If a user schedules a leads report without adding filters and the scope of the report is wider than the scope of the recipient, the following warning message will be displayed:

The specified recipient does not have access to the contracts as the creator of this schedule. Only authorized data will be sent to the recipient.

Sending the reports by FTP (K)

With this type of delivery, you must provide the information for connecting to the user’s FTP server (L), i.e. the server’s URL address, the port used (if applicable), and the user’s login and password.

The server FTP must support UTF-8.

To receive a notification when the leads report is ready to be retrieved from the FTP server, users can enter a notification email address (M).

As with sending reports by email, users must then define the report language (N), the delivery time (O) and the frequency (P), as well as the time zone (Q).

Times zones

If you are configuring a report where the data time zone is different to the delivery time zone, there may be a gap of several hours for the data received.

Scheduling example

General rule: when users create a schedule for a leads report, the data period received will be based on the specified delivery time and frequency.

For example: on January 10, 2023, a user creates a schedule for receiving a monthly leads report at 10 am on the 15th day of each month:

  • On January 15, 2023, the user will receive a data file covering the period from January 10 to 15. This report will only contain statistical data from the date on which the scheduled report was created.
  • On February 15, 2023, the user will receive a leads report covering the period from January 15 to February 15.

Example of time zones

Choosing time zones

Choosing different time zones has a significant impact on the organization of your scheduled reports and their parameter settings. For example, there is a 26-hour time difference between the first time zone (UTC-12:00 GMT-12:00) and the last time zone (UTC+14:00 Line Islands Time (Kiritimati)).

This is the time zone from which the statistical data will be extracted (applies to all recipients).

Sending time zone

The sending time zone is chosen by the user creating the scheduled report. It defines the time at which the report will be sent. Where the report is sent by email, different time zones can be defined for each schedule.

Example:

You’re a sales manager in an international team. You want to create a scheduled report for sending statistical data every Monday at 9 am to your sales colleagues in New York (USA), Paris (France) and Tokyo (Japan).

Step 1: start by defining the reference time zone for downloading the data. From the list, choose a common time zone (UTC+01:00), Central European Time (Paris), since your company is headquartered in France.

Step 2: configure a schedule for each of your sales colleagues:

  • On the first schedule line (R), enter the email address of the sales team in New York and specify the time zone for their location, i.e. (UTC-05:00) Eastern Time (New York), and then set a weekly frequency for 9 am on Monday.
  • On the second schedule line (S), enter the email address of the sales team in Paris and specify the time zone for their location, i.e. (UTC+01:00) Central European Time (Paris), and then set a weekly frequency for 9 am on Monday.
  • Lastly, on the third schedule line (T), enter the email address for the sales team in Tokyo and adjust the time zone for their location (UTC+09:00) Japan Standard Time (Tokyo), and finish by indicating a weekly frequency for 9 am on Monday.

Step 3: save your scheduled report. Therefore, the sales teams will receive a report every Monday at 9 am (local time according to their time zone). The content of the reports may vary according to the delivery time, but each sales team will see the action at the same time as defined by the common time zone for all reports.

Custom reports according to the time zone

If you want to send a custom report containing data for the time zone corresponding to the location of your different sales teams (New York, Paris and Tokyo),
you must create three separate scheduled reports with a specific time zone (for their locations) from which the statistical data will be extracted.

Basically, the specified time zone for downloading the statistical data must match the time zone where the recipients are physically located:

  • The first scheduled report (U) is for the US sales team. The time zone from which the statistical data will be extracted is: (UTC-05:00) Eastern Time (New York).
  • The second scheduled report (V) is for the French sales team. The time zone from which the statistical data will be extracted is: (UTC+01:00) Central European Time (Paris).
  • The third scheduled report (W) is for the Japanese sales team. The time zone from which the statistical data will be extracted is: (UTC+09:00) Japan Standard Time (Tokyo).

Options

  • You can exclude specific email addresses and/or domain names from accessing the statistical data in your reports.
  • Depending on their role, users can create a recipient list directly in this interface.
  • Cumulative send: this option aggregates the statistical data from the beginning of the month, depending on the required type of content.
CONTENTS