No recordings on destination URL conversion goals knowing there has been traffic

For a destination URL conversion goal that never records, the issue is almost always with either the goal definition or the UET tag/goal tracking status, not with traffic volume.

Check the following in order:

1. Verify the UET tag and goal linkage
   • Confirm the goal’s TagId (UET Tag ID) is the same tag that actually fires on the /thank-you-sales page. The UET tag ID must match the one configured on the goal.
   • In the UET dashboard, confirm that page views or events are being logged for the /thank-you-sales URL.
2. Check the goal’s TrackingStatus
   • Retrieve the goal via the Campaign Management API (for example, GetConversionGoalsByIds or GetConversionGoalsByTagIds) and inspect the TrackingStatus field on the UrlGoal.
   • If TrackingStatus is:
     • TagUnverified: the tag has not yet been verified; Microsoft Advertising has not received any activity from that tag. Ensure the tag is correctly installed and wait up to 24 hours.
     • TagInactive: no user activity data from the UET tag in the last 24 hours. Confirm the tag code is still present and firing.
     • InactiveDueToTagUnavailable: the account no longer has access to the UET tag (for example, permissions removed or account moved). In this case, the goal cannot record conversions until access is restored or the goal is reconfigured to a valid tag.
     • NoRecentConversions: the UET tag is active but no conversions have been recorded in the last 7 days. This usually means the goal conditions (such as the URL rule) do not match the actual traffic, or the conversion page is not tagged.
     • RecordingConversions: indicates that at least one conversion has been recorded in the last 7 days. If this is not the status, the goal is not currently recording.
3. Confirm the URL rule matches the real URL
   • For a destination URL goal defined as contains = /thank-you-sales, confirm that the actual URL seen by the browser when the conversion occurs really contains /thank-you-sales in the path (including case, query string, and any trailing slashes or variations).
   • If the URL includes additional characters (for example, /thank-you-sales/ or /thank-you-sales.html or query parameters before/after), ensure the contains pattern still matches the exact string present in the final URL.
4. Validate the conversion goal configuration
   • Confirm the goal is in an active Status (not Paused). The Status is user-controlled, while TrackingStatus is system-controlled.
   • Check that the goal type is UrlGoal and that it is associated with the correct campaigns/ad accounts.
   • Ensure the conversion window is not too short; if the ConversionWindowInMinutes is set very low, conversions that happen later may not be counted.
5. Validate that conversions are actually being sent
   • Use the UET dashboard to confirm that visits to /thank-you-sales are being logged.
   • If using app or custom events instead of pure page-load URLs, ensure the events are correctly implemented and that the goal is configured to count those actions.

If, after confirming the URL pattern, tag ID, and TrackingStatus, the goal still shows NoRecentConversions despite verified traffic to the conversion URL, the goal is likely misconfigured (for example, wrong tag, wrong URL rule, or wrong account/tag association). Recreate the goal with the correct TagId and a verified URL pattern, then monitor until the TrackingStatus moves to RecordingConversions once at least one conversion is logged.

References:

• Universal Event Tracking
• UrlGoal Data Object - Campaign Management
• ConversionGoalTrackingStatus Value Set - Campaign Management
• Windows App UET SDK
• URL Goal Record - Bulk
• Pages Viewed Per Visit Goal Record - Bulk