My conversions are not tracking

My conversions are not tracking

Traffic arrives, but conversions read zero or far below what your own system shows.

1. Confirm the conversion is verified. In Tracking › Conversions, the status should read Verified. If not, fire a test conversion.
2. Check your installation type. The Type column reads Manual, Gtm, or Server-Side. If it reads Gtm, a tag can be set up correctly inside the container and still never fire, because the container itself was never published after the tag was added or changed. Publish it, then confirm the tag fires on the page. If it reads Server-Side, open the code icon for the Server-to-server Pixel details and confirm with whoever manages that integration that events are reaching the endpoint.
3. Check the ClickID. This is the most common cause. Capture ClickID from the click URL when the visitor lands, store it against that user, and pass it back in your postback. Without it, conversions arrive unattributed.
4. Check where the code sits. The event must fire on the page that confirms the action, not the page that starts it.
5. Rule out ad blockers. If a Manual Tracking Pixel (JavaScript) is placed correctly but never fires in your own testing, a browser ad blocker is a common cause. Test again in a private window with blockers off before assuming the setup is wrong.
6. Check your UTMs. Set utm_source=Blockchain-Ads and utm_medium=referral so your analytics attributes traffic correctly. If traffic shows as an unknown referral, search for server.blockchain-ads.com.
7. Check the value parameter. Wallet ID and Transaction Value are optional fields under Advanced Options. Leaving them blank keeps Txn Value and ROAS at zero, but not CPA or the conversion count itself.

Fire one test conversion end to end after every fix, rather than waiting for live traffic to tell you.