Trackings and AB Tests

Reports of the Checkout P.P.C.T.

This document gathers the main tracking data for Guru checkouts, allowing you to monitor traffic origin, identify associated trackings, products, and marketplaces, and validate the configuration of conversion flows. These reports facilitate the analysis, auditing, and optimization of checkout campaigns.


On this page:

  • Checkout Identification

  • Origin

  • Products

  • URLs


Before you start, you need…

Checkout Identification

In this section, you view the data used to identify and organize Checkout P.P.C.T.s, facilitating the location of trackings and the analysis of the origin of exported results.

This information allows you to identify which specific tracking generated a click or conversion, as well as analyze campaign performance individually or consolidated.

Available data includes:

  1. Name: the name assigned to the checkout tracking at the time of P.P.C.T. configuration;

  2. Group name: the group to which the tracking is associated - tracking groups allow you to organize trackings by context, such as campaigns, launches, or specific strategies, enabling consolidated performance analysis.

In checkout P.P.C.T. management, the use of this data facilitates the application of filters, the quick location of specific links, and the auditing of the results generated by each tracking.

The tracking groups allow you to organize trackings by context, such as campaigns, launches, or specific strategies, enabling consolidated performance analysis and the application of filters in dashboards and reports.


Origin

In this section, you view the data that identifies the payment processor or platform responsible for the transaction linked to the product configured in Guru.

Available data includes:

  1. Marketplace name: the name of the payment processor or platform used in the checkout - helps to visually identify which gateway sales are being processed through and compare performance between different marketplaces;

  2. Marketplace ID: the marketplace identification code - used to ensure correct correspondence between Guru and the payment processor in integrations, such as APIs, webhooks, and automated flows.

With this information, it is possible to analyze and compare sales performance between different marketplaces, as well as validate technical tracking configurations and ensure correct processor identification.


Product

With the data in this section, you identify the product associated with the checkout tracking, as configured at the time of checkout P.P.C.T. creation.

Available data includes:

  1. Product name: the product selected to associate the tracking - used to identify which offer the traffic and registered results refer to.

Product identification allows you to relate traffic to attempt metrics and valid sales, facilitating the analysis of conversion rate per offer, the comparison of revenue generated between different products, and the auditing of results obtained in each checkout.

Access the product information to view details of the product associated with the tracking.


URLs

In this section, you view the URLs responsible for directing traffic to the correct offer and recording the origin of clicks that lead to checkout.

This information allows you to validate whether the tracking is pointing to the correct page and whether the disclosure link used in ads, buttons, or campaigns corresponds to the Checkout P.P.C.T. configured in Guru.

Available data includes:

  1. Origin URL and/or Disclosure URL*: the link generated by Guru that should be used in disclosure points, such as ads, buttons, or promotional links - it is composed of the domain (standard or custom) and the friendly URL defined during the tracking configuration;

  2. Destination URL: the final page where the visitor is redirected after clicking the disclosure link, such as a sales page or the direct checkout link.

*The Origin URL field displayed in the exported Checkout P.P.C.T. XLS file refers to the disclosure URL field in the Guru admin.

Analyzing these URLs facilitates campaign audits, validation of the redirection flow, and cross-referencing between the disclosed link and the page delivered to the user, ensuring consistency between campaign communication and the checkout experience.


More Resources