Reports of the Leads P.P.C.T.

This document describes the fields presented in the Lead P.P.C.T. report, which gathers the main information related to leads captured in Guru, allowing you to analyze the origin, context, and elements involved in each record.

From this report, it is possible to identify lead identification and grouping data, associated marketplaces and products, as well as the URLs used in the capture flow, facilitating performance analysis and monitoring of lead generation strategies.

On this page:

• Lead Identification and Grouping

• Marketplace data

• Products

• Capture URLs

Lead Identification and Grouping

In this section, you view the data that identifies the tracking associated with the lead and indicates the context in which it was captured within the structure configured during lead creation in Guru.

Available data includes:

1. Name: the name assigned to the tracking responsible for capturing the lead, at the time of P.P.C.T. configuration - allows you to quickly identify which specific tracking generated each click or conversion;

2. Group name: the tracking group associated with lead tracking, if any – the groups facilitate the centralization of related trackings, making it possible to organize them according to the context in which they were created, such as campaigns, products, or specific strategies.

Identifying tracking by name helps in the individual management of each link, while the group name provides a consolidated view of your entire campaign structure, optimizing the analysis time of your report.

Marketplace data

In the Originsection, you identify the transactional context associated with the lead, based on the relationship between the tracking and the product configured in Guru.

Available data includes:

1. Marketplace name: the name of the payment processor linked to the tracking - by identifying which gateway operations are processed through, you can compare the performance between different marketplaces used in your business;

2. Marketplace ID: the product identifier within the payment processor - useful for technical validations and data cross-referencing with external systems, ensuring the correspondence of information between Guru and the marketplace.

In practice, this data helps to understand the payment infrastructure associated with the lead, validate the technical configurations of your tracking, and cross-reference information with financial or sales reports.

Products

This section presents the product registered in Guru and associated with the tracking at the time of tracking link creation, allowing you to identify which commercial context each lead is linked to.

Available data includes:

1. Product name: the name of the product linked to the tracking responsible for capturing the lead - allows you to analyze the distribution and performance of leads by product.

Product identification facilitates data organization and readability, allowing you to segment captures and associate trackings with specific campaigns and pages. Furthermore, it can help maintain consistency between the marketing layer (lead capture) and the offer layer (product).

Capture URLs

In this section, you view the URLs involved in the lead tracking process, allowing you to understand how access was registered and to which page the user was directed until conversion.

Available data includes:

1. Origin URL and/or Disclosure URL*: the trackable link generated by Guru for the campaign - it is through this URL that the system registers accesses, identifies the origin of traffic, and associates the visitor with the captured lead;

2. Destination URL: the final address of the page to which the visitor is directed - in the case of Lead P.P.C.T., it is usually your capture page (landing page) or a sales page that includes contact capture before checkout.

*The Origin URL field displayed in the XLS file exported from Lead P.P.C.T. refers to the Disclosure URL field in the Guru admin.

This information is fundamental for analyzing traffic origin, validating the configuration of links used in campaigns, and ensuring that the capture flow is working as expected.

More Resources