--- title: "Tracking: what counts a conversion and how links get tagged" description: "What counts a conversion and how links are tagged: pixel and tag checks, shared tagging templates, server events from the CRM every 30 minutes." canonical: https://adsbeast.pro/features/en/tracking language: en section: features product_route: https://adsbeast.pro/pixels translations: - ru: https://adsbeast.pro/features/ru/tracking - uk: https://adsbeast.pro/features/uk/tracking - sk: https://adsbeast.pro/features/sk/tracking - es: https://adsbeast.pro/features/es/tracking - he: https://adsbeast.pro/features/he/tracking - ar: https://adsbeast.pro/features/ar/tracking --- # Tracking: what counts a conversion and how links get tagged Until you know what is counted and by what, every other figure means nothing. This section checks the pixels and conversion actions on each platform, keeps one set of tagging templates for every campaign, and sends server events from the CRM back to the platforms every 30 minutes. ## What is inside - **Counters**: The Meta pixel, Google conversion actions, the UET tag, the TikTok and LinkedIn counters - **Checks**: Is it installed, is it firing, which events and with which parameters - **Tags**: Link parameter templates, the same for every campaign and every client - **Server events**: From the CRM to the platforms every 30 minutes - **Quality**: How well events match real people and what would improve the match - **Analytics**: GA4 connects separately and adds post-click behaviour A campaign that spends without tracking lands in the audit findings. It is the first thing checked and the first thing fixed. ## What the section does ### Counters checked on every platform Each platform has its own counter and its own requirements. The section shows for each of them: is it installed on the site, are events arriving, which ones and with what parameters. Not "it should work", but "it works, here is the last event". - The state of the counter on each platform - The last events accepted, with their parameters - A list of what is missing for a complete picture ### One tagging scheme instead of a free-for-all When every manager invents their own link parameters, reports stop agreeing with each other. Tagging templates are set once for the agency and filled into every campaign for every client. - Link parameter templates for the agency - Tags filled into every new campaign - A check that the tag survived all the way to the lead in the CRM ### Server events from the CRM An event from a browser gets lost on the way: blockers, restrictions, how long files live. An event from a server arrives. From deal stages in the CRM the system sends a qualified lead and a sale back to the platforms every 30 minutes. - Events from CRM stages into Meta, Google and the Advertising in ChatGPT channel - How well events match real people - Sending errors with the platform response text ### The lead is tied to the click The click identifier is stored with the lead, so a sale can be returned to the campaign that produced it. Without that link server events are useless and a performance report turns into guesswork. - Platform click identifiers stored next to the lead - Tags carried into the lead and into the deal - A check that the link does not break on the way to the CRM ## How to put tracking in order Order is established once and then held by the system rather than by a manager remembering it. 1. **Check the counters** - For each platform: installed, firing, and what exactly it is firing. 2. **Set the tagging templates** - One set for the agency, filled into every campaign. 3. **Tie leads to clicks** - Click identifiers are stored together with the lead. 4. **Switch on server events** - From CRM stages back to the platforms every 30 minutes. ## Figures from the code - 30 min - between server event uploads - 5 - platforms with counters of their own - 24 h - between tracking checks in the audit ## What the section does not do - It does not install counters on the client site for them: it shows what is missing and how to check it. - It does not send platforms data that is not in the CRM. - It does not pass an absence of events off as zero conversions: "not measured" and "zero" are shown differently. - It does not work around platform and browser limits - server events operate within them. ## Questions and answers ### Why server events when there is a pixel? An event from a browser gets lost: blockers, file restrictions, a closed tab. A server event leaves your CRM and arrives. More importantly, it carries the deal stage rather than the fact that a form was sent. ### What does event match quality mean? How well the platform managed to match the event you sent to a particular person. The more correct parameters you pass, the higher the match and the better the optimisation works. The section shows the current value and what would improve it. ### How do tags help in reporting? One set of templates means every campaign for every client is tagged the same way, so reports agree with each other. The system checks that the tag survived all the way to the lead in the CRM rather than getting lost on the way. ### What do I do if a counter is not installed? The section shows it as a state and puts the campaign into the audit findings. Lead and sales campaigns without tracking do not pass the check at launch. ## Check the counters of your first client and see what is actually being counted The first 14 days are free on any plan and you do not need a card to start. Counter checks run from the first sync of the account. - Start free: https://adsbeast.pro/signup?lang=en - Pricing: https://adsbeast.pro/pricing?lang=en ## See also - [Lead quality: who fills in the forms and how real they are](https://adsbeast.pro/features/en/leads): Leads from every platform and from the site in one feed with a bot score: flagged from 40 points, blocked from 70. Industry profiles, delivery checks. - [Ad account audit: named lines, a reason, and the data behind it](https://adsbeast.pro/features/en/audit): Accounts audited on a schedule: every finding names a campaign, a reason and the data behind it. Delivery checked every 2 hours. - [Google Ads for agencies: every client account in one summary](https://adsbeast.pro/platforms/en/google-ads): Google Ads accounts over OAuth: figures every 15 minutes, 90 days of history, audits on a schedule, bids changed only after a person confirms. - [Meta Ads for agencies: form leads into the CRM, deals back into the account](https://adsbeast.pro/platforms/en/meta-ads): Facebook and Instagram accounts over OAuth: lead form entries land in the CRM at once, deals return as server conversions, Audience Network off by default.