How to Set Up Conversion Tracking for Ads (Pixels, Tags and Server-Side Events)
To set up conversion tracking for ads, define one conversion event, install each platform's pixel or tag (ideally through a tag manager), add a server-side or API connection for the same event, tag links with UTM parameters, test with a real conversion before spending, and reconcile ad-platform numbers against your own analytics. Infinall AI prepares campaign research, copy and creative; tracking is configured by you in your ad platforms and site.
Conversion tracking is the part of paid advertising most likely to be quietly broken. A pixel that fires twice, an event that fires on the wrong page, or a consent banner that blocks the tag will all make an ad platform optimise toward the wrong users while your dashboard looks fine. Set it up before you spend, not after the first disappointing week. This guide covers the common mechanics across Meta, Google, LinkedIn, TikTok, Reddit and others. Event names, tag types and privacy requirements vary by platform and region and change often, so follow each platform's current documentation, and consult your privacy or legal adviser on consent requirements. Infinall AI does not install tags or place media.
How to Set Up Conversion Tracking for Ads (Pixels, Tags and Server-Side Events)
Define the conversion and map the journey to it
Pick one primary conversion that reflects real business value: a paid purchase, a trial started, a qualified demo request or an activated account. Write down the exact page or action that completes it and which system knows it happened (your site, your app backend, your payment provider or your CRM). Add one or two secondary events, such as add to cart or signup started, only if they help the platform optimise earlier in the journey.
Install a tag manager and each platform's pixel or tag
Add a tag manager such as Google Tag Manager to your site, then create the base pixel or tag for each ad platform you will use, following that platform's setup flow. Use the platform's standard event names where they exist, since optimisation features usually key off them. Fire the conversion tag only on the confirmation action, not on the form page, and make sure it fires once per conversion. For single-page apps, trigger on a route change or a data-layer event rather than page load.
Add server-side or API events for the same conversion
Browser tags lose data to ad blockers, browser privacy features and declined consent. Most major platforms offer a server-side route, for example Meta's Conversions API, Google's enhanced conversions or server-side tagging, and similar options for LinkedIn, TikTok and Reddit. Send the conversion from your backend with the identifiers each platform accepts, and use the deduplication key the platform specifies so an event sent by both the browser and the server is counted once. Hash personal identifiers as each platform requires and honour user consent choices.
Tag every ad link with consistent UTM parameters
Define a naming convention and apply it to every destination URL: source, medium, campaign, and content or term for the ad or creative. Keep names lowercase and consistent, because "Meta", "meta" and "facebook" will appear as three separate sources in analytics. UTMs let you attribute signups in your own analytics and CRM independent of the ad platform's own reporting, which is how you catch over-counting.
Test with a real conversion before spending
Use each platform's event testing tool or helper (every major platform has a test or diagnostics view for events) and complete a real or test conversion on your site. Confirm the event appears once, with the right value and currency if applicable, and that the UTMs arrive in your analytics. Test on mobile and in a private window, and with your consent banner in both accepted and declined states. Fix duplicates and misfires now, because ad platforms learn from whatever data you send.
Set attribution windows, then reconcile numbers regularly
Choose and record the attribution window you use in each platform, since a platform using a different window from your analytics will report different totals. After the first week, compare conversions reported by each ad platform with your analytics, backend or CRM. Differences are normal because of windows, modelling and cross-device behaviour, but a large or growing gap usually signals a tracking fault. Judge campaigns on your own source of truth where possible and keep a short log of any changes to tags.
Frequently asked questions
Do I need both a pixel and server-side tracking?
Not strictly, but using both is the common recommendation from major ad platforms because each covers gaps in the other: the browser tag captures rich session context while the server event survives ad blockers and browser restrictions. If you can only do one, start with the browser tag through a tag manager, then add the server-side route when your volume or budget justifies the engineering time. Always deduplicate when you run both.
Why do my ad platform and analytics show different conversion numbers?
Platforms and analytics tools count differently: attribution windows, view-through versus click-only credit, cross-device modelling, consent-related gaps and time zones all cause differences. Some gap is expected. Investigate when the gap is large, suddenly changes or points in an odd direction, as that suggests double-firing tags, missing events or UTM problems. Pick a source of truth, usually your own backend or CRM, and use platform numbers for in-platform optimisation.
Does Infinall AI set up conversion tracking?
No. Infinall AI prepares campaign research, strategy, copy, creative and a launch guide for your review. You install the pixels and tags, configure events and publish campaigns in each ad platform. Infinall does not place media, manage live ad spend or replace legal advice on consent and privacy. The Free plan is $0 with 1,000 credits/month covering Full Campaign in Lite mode; Pro is $30/month.
Prepare your campaigns with Infinall AI, then track them in your ad platforms
1,000 free credits. No card required.