Conversion tracking records the sale, and attribution assigns credit
Short answer
Tracking answers whether the purchase or lead event was recorded. Attribution answers which eligible ad click, view, or channel receives credit for it. A purchase can be correctly tracked and still have no Google Ads attribution. Conversely, an attributed dashboard total is not proof that every backend order was tracked.
Validate CAPI JSON Open the rulepack
Use one order to separate the questions
A shopper clicks an ad on Monday, lands with a click identifier, and buys on Tuesday. The checkout system records an order. A browser tag or server API sends a Purchase event with order ID, value, and event time. That is the tracking path. The ad platform then tries to join the event to an eligible click or view and applies a lookback window and attribution model. That is the attribution path.
If the Purchase request never leaves, fix tracking first. If it leaves but the redirect lost gclid or fbclid at landing, inspect the click chain and match signals. If event and identifier both arrive, check conversion-action settings and reporting rules. Adding another purchase pixel at the last stage can turn a reporting question into duplicate events.
The raw event count is a different number from credited conversions
A backend order ledger counts completed transactions. A GA4 purchase event report counts events Analytics observed. A Google Ads Conversions column counts selected conversion actions credited according to Ads settings. A Meta ads report applies Meta's own eligible interactions and attribution rules. These numbers have related meanings but different denominators and dates.
Track unique transaction IDs across the layers. If the ledger has 100 orders and GA4 saw 90 unique purchase IDs, investigate the missing ten events. If GA4 saw 100 but Google Ads credits 35, investigate the share of customers that interacted with ads and the account's goals and windows. You cannot conclude that 65 pixels failed from the Ads column alone.
Click IDs are the bridge, not the conversion
A gclid, fbclid, or other click identifier arrives on a landing URL after an ad interaction. The site may preserve a supported identifier in a first-party cookie or server session for later matching. The identifier says where the visit came from; it does not say a purchase happened. The conversion event says the action happened; without usable match information the platform may have limited ability to credit a specific ad.
Redirects, cross-domain checkout, consent decisions, and delayed CRM sales can break that join. Check the exact landing URL and every redirect hop before changing an attribution model. UTMs are useful campaign labels, but they are not a substitute for every platform's click ID or conversion request.
Settings can move credit without changing the event
An attribution model determines which eligible touchpoints receive credit. A lookback window limits how far back those interactions can count. Google Ads also distinguishes Primary from Secondary conversion actions and One from Every counting for each action. Changing one of these can change a report or bid signal while the underlying order and pixel request remain the same.
For daily comparisons, check whether one report places the conversion on click date and another on conversion date. Google documents this as a source of apparent mismatch between Ads and Analytics. Compare a wider range or the Ads by-conversion-time columns before you declare a tracking outage based on a single day.
A useful triage order
First, confirm the business action in the backend ledger. Second, confirm a single event with the right name, ID, value, currency, and time reached the intended vendor endpoint. Third, confirm the click or view identifiers survived the landing and checkout journey where applicable. Fourth, inspect the platform's conversion action, counting method, attribution window, date basis, and selected campaign goal. Record the first stage that disagrees with evidence.
Pixellint helps at the request and payload stage. It can flag malformed pixel URLs, bad clocks, and invalid conversion API fields. It cannot decide whether a particular customer was eligible for an ad platform's attribution. Keep the raw request, the backend order, and the report setting together when filing a measurement issue.
Questions
Can a conversion be tracked but not attributed?
Yes. The event can reach the platform without an eligible ad interaction or enough matching information to credit a campaign.
Do two platforms' attributed conversions add up to unique sales?
No. Both platforms can claim credit for the same backend order under their own attribution rules.
Sources
Check the artifact
Paste the pixel URL or JSON body into the
playground. Same engine as
pixellint validate. Artifacts you test may be stored;
see privacy.