Conversion tracking

In Getting started · Updated (1 hours ago)

Conversion tracking sends your verified conversions (such as completed purchases or submitted leads) back to ClickPatrol. With this real conversion data, ClickPatrol can make more accurate blocking and unblocking decisions, recognizing genuine users based on the actions they actually completed instead of clicks alone. This guide shows you how to set it up through Google Tag Manager.

Why set up conversion tracking#

  • Conversions: Every time a conversion is triggered, it's sent to ClickPatrol to learn from your conversions.

  • Reduce false positives: Minimize incorrectly flagged legitimate traffic.

  • Better evaluation: Evaluate the quality of traffic on your platform more accurately.

  • Improved detection: Detect suspicious or fake clicks, especially with soft conversions.

Set up conversion tracking in Google Tag Manager#

  1. Create a new tag

    • Click on Tags → New.

    • Select Tag Configuration and choose Custom HTML.

  2. Insert the tracking code

    • Open your ClickPatrol dashboard, go to Integration in the sidebar, and open the Conversions tab.

    • Copy your personalized tracking code from there. It already contains your unique UID and the conversion parameters. Paste it into the Custom HTML field.

    Always use the code from your own integration page rather than copying an example, so your UID and parameters are correct.

  3. Configure triggering

    • In your GTM tag, go to Triggering.

    • Select a trigger for confirmed conversions, such as:

      • Purchase Completed

      • Lead Submitted

  4. Save and publish

    • After configuring the tag, click Save.

    • Click Submit and then Publish to make the changes live.

      How conversion data is sent to ClickPatrol #

      Customers can send conversion data to ClickPatrol in two ways:

      1. Conversion tag through Google Tag Manager Set up a conversion tag in Google Tag Manager and trigger it when a confirmed conversion takes place.
      2. Pixel or trigger to the conversion URL Fire a pixel or trigger to your ClickPatrol conversion URL and include the required conversion data.

      How ClickPatrol matches conversions #

      When ClickPatrol receives a conversion, we try to match it to a recorded click in the following order:

      1. Click ID match We first check whether the conversion includes a Google Click ID or another advertising click ID. The click ID can be received through Google Tag Manager or the ClickPatrol tracking template. If the click ID exists in our database, we match the conversion to the corresponding click.

      2. Fallback match If no click ID is available, we try to match the conversion using:

       • The IP address or fingerprint
       • The user HTTP header If we find a matching record in our database, we qualify and display it as a conversion.

       Why some conversions may not appear #

      A conversion will not appear in the ClickPatrol dashboard if we cannot find the required data to verify and match it to a recorded click. This may happen when:

        - No click ID was included with the conversion
        - The IP address or fingerprint does not match a recorded click
        - The user HTTP header does not match a recorded click
        - The required conversion data was not sent correctly

      We do not manually add or edit unmatched conversions. Conversion data can't be manipulated, so each conversion must contain enough information for ClickPatrol to verify and attribute it correctly.

      Data required to match a conversion#

      ClickPatrol needs enough data to match each conversion to a recorded click.

      For a click ID match, the conversion must include:

        • A Google Click ID or another advertising click ID
        • The conversion data sent through Google Tag Manager, the ClickPatrol tracking template, or the conversion URL. 

        If no click ID is available, ClickPatrol uses fallback matching. The conversion must include:

          • The IP address or fingerprint
          • The user HTTP header
          • The matching data must correspond with a record in the ClickPatrol database.

        If the conversion does not include a click ID and we cannot find a matching IP address, fingerprint, or user HTTP header, the conversion will not appear in the ClickPatrol dashboard.

          Important#

          Only apply this trigger to hard (real) conversions, not softer actions like page views or form starts. This is crucial for ClickPatrol to accurately track and unblock users based on genuine actions.

          Was this article helpful?

          Let us know so we can improve our documentation

          Thanks for your feedback!

          Need Help?

          If something isn't working or you have questions, our support team is here to help you.

          Contact Support