Inquiry about Discrepancy between Microsoft Advertising API and UI Data for conversion by goal

Jaden 10 Reputation points
2024-08-08T06:18:26.1566667+00:00

Dear Microsoft Support Team,

I am reaching out to report an issue I am experiencing with the conversion goal data obtained from the Microsoft Ads platform. Specifically, there is a discrepancy between the conversion values displayed in the Microsoft Ads UI and those retrieved via the ConversionPerformanceReportRequest API.

Issue Description

I have been using the ConversionPerformanceReportRequest API to retrieve conversion data segmented by goals. However, the conversion values returned by the API do not match the values displayed in the Microsoft Ads UI for the same goals and time periods.

Steps Taken

  1. Checked Data Synchronization: I ensured that the time frame and data synchronization times between the API and the UI are aligned. However, the values still do not match.
  2. Verified Time Zone Settings: I confirmed that the same time zone settings are used in both the API requests and the UI, to ensure there are no discrepancies caused by time zone differences.
  3. Reviewed Filtering and Aggregation: The API requests were configured to use the same filters and aggregation settings as the UI, including campaign, ad group, and device type filters.

Consulted API Documentation: I reviewed the API documentation to ensure that the fields I am requesting correspond directly to those displayed in the UI. Despite this, the values remain inconsistent.

Request for Assistance

I would appreciate your guidance on how to resolve this discrepancy. Specifically, I would like to understand:

  • Whether there are known issues or differences in data calculation or synchronization between the API and the UI.
  • If there are additional settings or parameters I should consider when using the ConversionPerformanceReportRequest API to ensure data consistency.
  • Any other potential reasons for the discrepancies that I may have overlooked.

So, Here's my request for request:

<SubmitGenerateReportRequest
			xmlns="https://bingads.microsoft.com/Reporting/v13">
			<ReportRequest i:nil="false" i:type="ConversionPerformanceReportRequest">
				<ExcludeColumnHeaders i:nil="false">false</ExcludeColumnHeaders>
				<ExcludeReportFooter i:nil="false">true</ExcludeReportFooter>
				<ExcludeReportHeader i:nil="false">true</ExcludeReportHeader>
				<Format i:nil="false">Csv</Format>
				<FormatVersion i:nil="false">2.0</FormatVersion>
				<ReportName i:nil="false">xxxxx ConversionPerformanceReportRequest</ReportName>
				<ReturnOnlyCompleteData i:nil="false">false</ReturnOnlyCompleteData>
				<Aggregation>Summary</Aggregation>
				<Columns i:nil="false">
					<ConversionPerformanceReportColumn>ConversionsQualified</ConversionPerformanceReportColumn>
					<ConversionPerformanceReportColumn>Goal</ConversionPerformanceReportColumn>
					<ConversionPerformanceReportColumn>CampaignId</ConversionPerformanceReportColumn>
				</Columns>
				<Filter i:nil="true">
					<AccountStatus i:nil="false">ValueHere</AccountStatus>
					<AdDistribution i:nil="false">ValueHere</AdDistribution>
					<AdGroupStatus i:nil="false">ValueHere</AdGroupStatus>
					<CampaignStatus i:nil="false">ValueHere</CampaignStatus>
					<DeviceType i:nil="false">ValueHere</DeviceType>
					<KeywordStatus i:nil="false">ValueHere</KeywordStatus>
					<Keywords i:nil="false"
						xmlns:a1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
						<a1:string>ValueHere</a1:string>
					</Keywords>
				</Filter>
				<Scope i:nil="false">
					<AccountIds i:nil="false"
						xmlns:a1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
						<a1:long>xxxx</a1:long>
					</AccountIds>
					<AdGroups i:nil="true">
						<AdGroupReportScope>
							<AccountId>ValueHere</AccountId>
							<CampaignId>ValueHere</CampaignId>
							<AdGroupId>ValueHere</AdGroupId>
						</AdGroupReportScope>
					</AdGroups>
					<Campaigns i:nil="true">
						<CampaignReportScope>
							<AccountId>ValueHere</AccountId>
							<CampaignId>ValueHere</CampaignId>
						</CampaignReportScope>
					</Campaigns>
				</Scope>
				<Time i:nil="false">
					<CustomDateRangeEnd i:nil="false">
						<Day>2</Day>
						<Month>8</Month>
						<Year>2024</Year>
					</CustomDateRangeEnd>
					<CustomDateRangeStart i:nil="false">
						<Day>30</Day>
						<Month>6</Month>
						<Year>2024</Year>
					</CustomDateRangeStart>
					<PredefinedTime i:nil="true"></PredefinedTime>
					<ReportTimeZone i:nil="true"></ReportTimeZone>
				</Time>
			</ReportRequest>
		</SubmitGenerateReportRequest>
Microsoft Advertising API
Microsoft Advertising API
A Microsoft API that provides programmatic access to Microsoft Advertising to manage large campaigns or to integrate your marketing with other in-house systems.
418 questions
Microsoft Advertising
Microsoft Advertising
A platform for Microsoft's advertising efforts designed to manage all advertising and reporting for partner advertisers. Previously known as Bing Ads and adCenter.
78 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Asha Kanta Sharma 451 Reputation points
    2024-08-20T16:01:33.2933333+00:00
    1. Verify that the data sources and settings used in the API match those in the UI.
    2. Check synchronization delays and ensure consistent time zones.
    3. Review API parameters and request configurations.
    4. Consult Microsoft Ads support for any known issues or additional guidance.
    5. Use alternative metrics and reports to cross-verify data.
    2 people found this answer helpful.
    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Age Calculator 0 Reputation points
    2024-10-15T12:22:16.4166667+00:00
    1. Verify that the data sources and settings used in the API match those in the UI.
    2. Check synchronization delays and ensure consistent time zones.
    3. Review API parameters and request configurations.
    4. Consult Microsoft Ads support for any known issues or additional guidance.
    5. Use alternative metrics and reports to cross-verify data.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.