Skip to content

OneClick Tracking — Conversion Tracking for Meta Ads

OneClick Tracking is a conversion tracking system that corrects attribution mistakes made by Meta, delivering real data based on your campaigns’ UTMs.

What does OneClick Tracking solve in practice?

Section titled “What does OneClick Tracking solve in practice?”

It creates a tracking layer based on UTMs and on a direct integration with your sales platform/CRM to:

  • receive conversions directly from the source (e.g., Hotmart via webhook);
  • capture parameters that map the campaign, ad set and ad;
  • show the number of conversions and the real CPA inside Ads Manager;
  • reduce Meta’s attribution discrepancies and delays.

Does tracking also show results at the ad set and ad level?

Section titled “Does tracking also show results at the ad set and ad level?”

Yes. The naming is updated on the campaign, ad set and ad. This lets you identify which ad set and which ad (creative) is generating tracked sales, with tracked CPA at each level.

Does OneClick Tracking apply to all campaigns or only to optimized ones?

Section titled “Does OneClick Tracking apply to all campaigns or only to optimized ones?”

Tracking is applied at the account level. Once you finish the setup, campaigns are tracked whether or not they have an active optimization, and the tracking naming starts to appear on the campaign, ad set and ad.

A campaign without an optimization only needs to have had spend in the last 14 days to receive the naming. See below how to read this naming.

OneClick writes the tracked numbers in front of the name of the campaign, ad set and ad in Ads Manager:

[12 (45,30) | 5 (38,00) | 2 (41,50) | 1 (18,15)] Nome da sua campanha
  • Each block separated by | is a period, in the order you chose during setup — in the example, Maximum, 30 days, 7 days and Today.
  • Inside each block you see what you selected: the number of tracked conversions, the tracked CPA in parentheses, and the ROAS in braces { }.
  • A 0 means the period was counted and had no tracked conversions.
  • A - means the period cannot be counted yet (explained just below).

Names are updated automatically, roughly once an hour. For campaigns without an active optimization, this happens as long as the campaign has had spend in the last 14 days; after that it keeps the last name it received.

The naming only appears after the first conversion is received and attributed to a campaign. Until some period has a conversion, the name stays as it is.

OneClick only knows about sales starting from the first tracked conversion in your account. If the campaign was already running before that, a period starting before that date would include days when sales were not being tracked. Showing 0 for that period would say the campaign didn’t sell, which isn’t true: those sales simply weren’t recorded. That’s why these periods appear as -:

[- | - | - | 1 (18,15)] Nome da sua campanha

The periods fill in on their own over time: the 7-day period starts appearing about a week after the first tracked conversion, the 30-day period about a month after, and so on. The Maximum period (since the campaign started) stays as - for campaigns that started before the first tracked conversion, because the sales before it were never recorded.

Campaigns created after the first tracked conversion in the account show every period from the start.

The available integrations cover digital products (e.g., Hotmart), e-commerce and CRM lead generation (e.g., Pipedrive, with an event on stage change).

How do I request an integration with a platform that doesn’t exist yet?

Section titled “How do I request an integration with a platform that doesn’t exist yet?”

Go to OneClick Tracking → new integration → Suggest platform and submit the name. Prioritization depends on the volume of requests (internal ranking).

Note: tracking setup works best on a computer. See also the Custom Integration guide for platforms that send their own webhooks.

Before finishing the setup, you define how OneClick combines Ads Manager data with the conversions tracked by UTM. See Attribution Modes — there are four options: 100% UTM, Ads Manager attribution, journey-based (recommended) or custom.

Installing the UTM pass-through script:

Add the UTM pass-through script to every sales page so the parameters are carried all the way to the final checkout page. You can do this via Google Tag Manager or, preferably, by installing the script directly in the site’s header.

OneClick recommends using UTMs that contain IDs to allow accurate conversion tracking. OneClick’s default example:

utm_source=facebook-oneclick-ads&utm_content={{ad.id}}&utm_medium={{adset.id}}&utm_campaign={{campaign.id}}

If you already use a UTM pattern tied to GA4, you can combine both. Example of a pattern you may already use:

utm_source=facebook&utm_medium=cpc-{{adset.name}}&utm_campaign={{campaign.name}}&utm_content={{ad.name}}

Practical recommendations:

  • Keep at least the ad.id in the parameters — OneClick can attribute the conversion correctly when there is an ID (the ad.id is the most complete, because it also identifies the adset and the campaign).
  • A suggested hybrid option (keeps your labels readable and the IDs for attribution):
utm_source=facebook&utm_content={{ad.id}}-{{ad.name}}&utm_medium=cpc-{{adset.name}}&utm_campaign={{campaign.name}}
  • If you prefer to merge both sets into one (watch out for Meta’s character limit):
utm_source=facebook-oneclick-ads&utm_medium=cpc-{{adset.name}}-{{adset.id}}&utm_campaign={{campaign.name}}-{{campaign.id}}&utm_content={{ad.name}}-{{ad.id}}
  • Note on truncation: Meta usually limits the number of characters. Very long names can truncate the IDs — so it’s best to put the ID first when possible.
  • If the webhook event carries no ID at all, OneClick won’t be able to tell where the conversion came from.

There are two ways:

  • add the UTMs directly to the destination link; or
  • add the UTMs to the ad’s URL parameters field.

All ads need correct UTMs — otherwise part of the conversions will be left out of tracking.

Yes. Select multiple ads, edit the URL parameters field (which will show “mixed values”) and apply a single value to all of them.

OneClick Ads exposes tracking data through the Model Context Protocol (MCP). By connecting an AI assistant (such as Claude) to your account, you can ask questions in natural language, for example:

  • “Which of my accounts have tracking set up?”
  • “How many conversions did I get in the last 7 days via Hotmart?”
  • “Show this week’s conversions with the value of each transaction.”
  • “Which campaign generated the most tracked sales this month?”
  • “How much revenue did I make last month with OneClick Tracking?”
  • “What was my revenue over the last 6 months, month by month?”

The assistant queries your data in real time and answers with the results — no need to export spreadsheets or open separate dashboards.

For most of the platforms in the list above, setup is just pasting a Webhook link — and for those, you can ask your AI assistant to create the integration for you instead of repeating the steps manually in the app. Just say, for example, “set up tracking for my account through Hotmart”.

The assistant creates the integration and gives back what only you can do on your side: the Webhook link to paste into the platform, the UTM parameters for the ads, and the UTM pass-through script for the sales pages. After pasting this information into the platform and the site, come back to the assistant (or open the app) to confirm that conversions are arriving.

The assistant also creates the integration for CRM platforms that require an access credential (a token, for example) — such as Pipedrive, HubSpot, Kommo, Clint, GoHighLevel, PandaChat, Tintim, Agendor and BW Commerce. In these cases, after providing the credential, you need to tell the assistant which stages of your funnel count as a conversion (for example, “count it as a conversion when the deal moves to ‘Won’ in funnel X”) — without that, the integration is created but doesn’t record any sales yet.

Nuvemshop and RD Station CRM are still connected through the app, because the authorization process for these two goes through the platform’s own screen.

Can I adjust or reconnect an existing integration through the assistant?

Section titled “Can I adjust or reconnect an existing integration through the assistant?”

Yes. Once the integration exists, you can ask the assistant to adjust settings such as the currency, the attribution mode or which funnel stages count as a conversion — without recreating the integration from scratch. An adjustment made this way does not change or erase the integration’s other settings.

If a CRM integration’s credential stops working (for example, a token expired or revoked on the platform’s side), the app stops recording conversions through it. In that case, ask the assistant to reconnect the integration with the new credential: it confirms the credential is valid before saving, and the integration goes back to recording sales normally.

Campaigns with a WhatsApp objective/flow can be optimized. To track conversions on WhatsApp, we recommend using a dedicated solution that fires events to Meta (e.g., a “meeting scheduled” / “demo scheduled” stage) and then optimizing the campaigns for those events.