---
title: "Custom Integration"
description: "Learn how to connect any platform to OneClick Tracking through a custom webhook to track conversions in your Meta Ads campaigns."
---

OneClick Tracking **corrects wrong attributions made by Meta**, delivering **real data based on UTMs** and enabling safer scaling decisions.

**With OneClick Tracking you see the volume of real conversions per period right in your Ads Manager, making for a quick, clear audit without dashboards that are a hassle to keep up to date.**

Note: **OneClick Tracking** removes the need for extra tracking tools!

---

:::tip[You can connect several platforms at the same time]
OneClick Tracking lets you connect **more than one platform to the same ad account** at the same time (for example, Hotmart and Eduzz together). Each platform has its own integration — with its own Webhook link or access credential — and they coexist without competing with each other; just repeat the **"New Integration"** steps for each one you want to connect.

Each sale is attributed to the right campaign by its **UTM**, not by the platform. So if one campaign sells through one platform and other campaigns sell through another, each conversion is automatically linked to the campaign it came from, regardless of which platform generated the sale. The recommended setup is **each campaign serving a single platform** — avoid having the same campaign sell on two platforms at once.
:::

## Setting up OneClick Tracking

- Log in to your OneClick Ads account.
- Go to the "OneClick Tracking" tab, available in the left sidebar menu of [OneClick Ads](https://app.oneclickads.com.br/oneclick-tracking).

![image1](../../../../../public/oneclick-tracking/common/image-1.png)

2. Click "New Integration".

3. Select the product type ("Lead generation", "Digital product" or "Ecommerce") and click Continue.

4. Select the "**Customizado**" (Custom) platform and click Continue.

:::tip[Prefer a native integration when one exists]
The "Customizado" (Custom) option is for platforms that **do not yet have** a native integration in OneClick Tracking. Before following these steps, check whether your platform already appears in the list of supported platforms — it may have gained its own native integration (simpler to set up, with no need for Make). Chatwoot, used as the example below, for instance, now has its own native integration; the example remains valid to illustrate how Make works with any other platform that still relies on the Custom integration.
:::

4.1 How to set up a Custom integration using [Make AI](https://www.make.com):

4.2 Use this ready-made [layout ](https://us2.make.com/public/shared-scenario/4UnfCA8fV8S/integration-webhooks-json)in your Make:

![image2](../../../../../public/oneclick-tracking/custom/image-1.png)

4.3 Click Edit and create the first webhook:

![image3](../../../../../public/oneclick-tracking/custom/image-2.png)

4.4 Copy the webhook link and paste it into the webhook integration of the platform you are using (you should find the place for webhook integrations in your platform's app; in my case I'm building a custom integration with Chatwoot, which is a CRM):

![image4](../../../../../public/oneclick-tracking/custom/image-3.png)

![image5](../../../../../public/oneclick-tracking/custom/image-4.png)

4.5 Now click Start in Make and wait until a webhook event comes in from your platform (for Ecommerce and Digital product these events fire when a sale happens, but for CRMs the events fire when a user is created or a stage is changed)

4.5.1 I'll simulate a stage change in Chatwoot so we can move on:

![image6](../../../../../public/oneclick-tracking/custom/image-5.png)

I'll add the label "etapa-1" to the user "João Teste":

![image7](../../../../../public/oneclick-tracking/custom/image-6.png)
![image8](../../../../../public/oneclick-tracking/custom/image-7.png)

4.6 The event fired in Make:

![image9](../../../../../public/oneclick-tracking/custom/image-8.png)

4.7 Now that Make has received the platform's event, we can process it. The first step is to create a filter for the next step (for ecommerce/digital products we want to catch events with `status = "PAID"` or another status you want to track; for a CRM we want to track specific stages or labels).

How to choose the operator type in the filter (Array Operators vs Text Operators):

- Fields that are lists/arrays (for example `labels`, `tags`, `items`) must be filtered with **Array Operators**. Use operators such as `contains` to check whether the list contains a specific value. Example: if the label `etapa-1` is inside `labels`, choose the `labels` field → **Array Operators** → `contains` → `etapa-1`.
- Fields that are simple text values (for example `status`, `email`, `phone`) must be filtered with **Text Operators**. Use operators such as `equals`, `contains` or `starts with` as appropriate. Example: for `status = "PAID"` choose the `status` field → **Text Operators** → `equals` → `PAID`.
- Note: if you are selecting a regular value (not inside a list), always choose **Text Operators** instead of Array Operators — this avoids false negatives and incompatible operators.

In our example the value we want to track (`etapa-1`) comes inside the `labels` list, so we'll use **Array Operators** to find that item in upcoming events:

![image10](../../../../../public/oneclick-tracking/custom/image-9.png)

As an example of a filter when the field is a simple value (not an array), see the image below, which shows **Text Operators** selected and an `equals` to compare an exact text:

![image27](../../../../../public/oneclick-tracking/custom/image-21.png)

With the right filter created (Array or Text Operators), you make sure only the events you want move on to the next actions in the scenario.

4.7 Now, with this event recorded in Make and the filter ready, we can map the parameters we want into the shape we need:

For custom CRM integrations, we need to send the data to OneClick following the payload below (payloads vary from integration to integration; for Ecommerce and Digital product the payloads are different, but the process is the same):

:::tip[The exact JSON template is already available inside OneClick]
You don't need to rebuild this payload from the template below alone: the "Customizado" (Custom) integration setup screen itself shows the full JSON template, already filled in with your platform's name and your secret key — one per product type (Ecommerce, Digital product or Lead generation). Copy that template straight from the screen when building the mapping in Make.
:::

```json
{
  "payload_id": number,
  "platform": "nome_da_plataforma_cadastrada",
  "secret_key": "sua_chave_secreta",
  "lead_id": number,
  "data": {
    "lead": {
      "created_at": "string",
      "pipeline_id": "string",
      "tracking_parameters": {
        "sck": "string",
        "src": "string",
        "utm_source": "string",
        "utm_medium": "string",
        "utm_campaign": "string",
        "utm_content": "string",
        "utm_term": "string"
      }
    },
    "customer": {
      "name": "string",
      "email": "string",
      "phone": "string"
    }
  }
}
```

Copy and paste it into Make's JSON:

![image12](../../../../../public/oneclick-tracking/custom/image-11.png)
![image13](../../../../../public/oneclick-tracking/custom/image-12.png)

Now let's map all the parameters we need (when you click inside the Object, a small box opens with the event Make received):

![image14](../../../../../public/oneclick-tracking/custom/image-13.png)
![image15](../../../../../public/oneclick-tracking/custom/image-14.png)

**_ It is very important to fill in the UTM parameters (in this example, no UTM came in the webhook event). That's why you should send Make an event that contains the UTMs, so tracking can attribute the conversions to the respective Campaigns, Ad Sets or the Ads themselves _**

4.8 With the JSON configured, the last part is sending this mapped event to OneClick Ads; to do that, we configure the HTTP module:

![image16](../../../../../public/oneclick-tracking/custom/image-15.png)

- Paste the webhook link provided in step 3 of the Tracking setup into the URL parameter in HTTP:

![image17](../../../../../public/oneclick-tracking/custom/image-16.png)
![image18](../../../../../public/oneclick-tracking/custom/image-17.png)
![image19](../../../../../public/oneclick-tracking/custom/image-18.png)

- Select the method: "POST"
- Body Content Type: "application/JSON"
- Body Content: "JSON string" (obtained in the previous step)
  4.9 Save the integration and turn on "Immediately as data arrives":

  ![image20](../../../../../public/oneclick-tracking/custom/image-19.png)

5. Go back to the "Scenarios" tab and turn on the integration (switch on the left):

![image21](../../../../../public/oneclick-tracking/custom/image-20.png)

Now every event sent by your platform will be received and processed by Make! 6. Go to the next step of the integration and copy the UTM Script generated inside OneClick Tracking.

![image22](../../../../../public/oneclick-tracking/common/image-2.png)

6.1. Paste it into the "URL parameters" field in ALL of your ads in Ads Manager, as shown below:

![image23](../../../../../public/oneclick-tracking/common/image-3.png)

7. Install the **UTM Passthrough Script** on all your sales pages, so the UTMs are loaded automatically into the card of each lead generated.
   a. You can install it on your site via Google Tag Manager or, preferably, directly in your site's header.

8. Set the Attribution Mode.

- [Watch this video](https://www.youtube.com/watch?v=JgWkvv4ZNLY) to understand each model.
- Click Continue.

![image24](../../../../../public/oneclick-tracking/common/image-4.png)

9. Define the Naming Convention that your campaigns, ad sets and ads will receive in your Ads Manager and click Next.

:::caution[Renaming the campaign depends on processed conversions]
The naming configured here **will only be applied to the campaign name in Ads Manager once there is at least 1 processed conversion**. Receiving raw data from the integrated platform's webhook is not enough — the system must have structured the conversion and attributed it to a campaign. If the webhook is arriving but the campaign name hasn't changed yet, wait for the first conversion to be recorded.

To understand the numbers and the `-` that appear in the name, see [How to read the tracking naming](/en/oneclick-tracking/#how-to-read-the-tracking-naming).
:::

![image25](../../../../../public/oneclick-tracking/common/image-5.png)
![image26](../../../../../public/oneclick-tracking/common/image-6.png)

---

## Done!

Wait at least 24 hours for the setup to take effect, and all your campaigns (those that receive conversions) will start recording conversions right inside Ads Manager.

![Campaigns with the OneClick Tracking prefix in Ads Manager](../../../../../public/oneclick-tracking/common/image-7.png)

---

## Important Notes

- Only campaigns created after the setup will have access to the "Maximum Period" data. This **does not affect** OneClick Ads optimization on older campaigns in any way.
