#1 The Pixel Tag is not reporting my attributed conversions. How can I ensure the pixel tag is capturing all conversions?
This could be caused by the HTML code for the base or event pixel being placed in the wrong location of your website or tag manager system.
Note that by installing the base pixel code within the page’s <head> section, this ensures the pixel tag fires quickly as it would be one of the first things to load. If you notice that your pixel tag is installed within an <iframe>, this will also prevent attribution from occurring so placing the tag outside an <iframe> should troubleshoot any attribution issues.
#2 I use floodlight tags to track conversions in Google Campaign Manager 360 (CM360) and am seeing zero or very few conversions being reported in Twitter Ads Manager.
These floodlight tags leverage <iframes>, which often cause the CM360 referrer URLs to be captured rather than the page URLs that are needed for conversion event attribution. To avoid attribution issues across your campaigns, ensure to implement your pixel tag directly on the page so URLs are passed correctly in order to trigger attribution. Piggybacking our pixel off floodlight tags will ultimately cause discrepancies.
If you are using Click Tags, follow the below setup to ensure proper conversion tracking:
Place your Click Tag under “Measurement” on the Ad Group level.
Ensure that no Click Tags are placed on the Ad/Creative level under the landing page URL field.
For additional information on correct CM360 and Click Tag setup, please refer to our help article here.
#3 I see a tag implemented on my website that I am unable to find on my Events Manager.
If you see a different tag ID implemented on your website that is not within your ads manager, it could be because:
The Tag ID is from a different ads account within your organization.
A previous Tag from the correct ads account was implemented, but since deleted in the dashboard.
#4 The pixel network calls have a status of ‘blocked.’ How can I fix it?
If you are using a Content Security Policy application on your website, it is likely that the pixel calls are being blocked by it.
To troubleshoot this issue, ensure that you're allowlisting "ads-twitter.com", "ads-api.twitter.com", and "analytics.twitter.com" in "img-src" and "connect-src" directives within your CSP header in order to continue to see results with the pixel.
#5 My pixel is correctly placed but there is still a highlight alert warning about the pixel health. What else could it be?
We recommend that you check your creative/ad level to ensure that the proper landing page URL is being used. If you are using a different destination URL than your website (such as a click tracker, URL shortener, or a redirect), this will cause the Click ID to break and the pixel will not capture all conversion data.
#6 I took the necessary steps to troubleshoot my pixel. How long until the Account Highlights warning goes away?
The warning on your account should go away between 12 to 24 hours after you troubleshoot your attribution issue.
If you still see a message on your account after taking the necessary steps, please reach out to @AdsSupport or your X representative for assistance.
To learn more about how to set up RDU, please visit the Ads Help portal and file a ticket under Mobile App, Conversion Tracking & Audience Manager >> How to set up Restricted Data Use.