Discrepancies in the API data compared to the UI for the same Ad ID.

[Alexis Surabian]

Hi team, I wasn't sure about what info you would need for this, so I might have provided to much info. Apologies if that's the case. 

Adv Name: Quicken Loans (Core Digital)
Adv ID: 78986528

FM: https://flight-manager.outbrain.com/flightmanager/spacey/advertisers/78986528/campaigns

Campaign ID:1121275784

Below is what the client reported, and the small guess at the issue that I responded with:

What the client reported:

It appears there are still discrepancies in the API data compared to the UI for the same Ad ID.

For campaign OB_QL-LRE_DeskTop_20260806_SeniorListicle-FullAud, specifically Promoted Link ID 001ce34d87f59fc79bea83805c51649ffd, the URL shown in the UI does not match the URL returned by the API. Also, the ad name is missing in the current API extract.

UI Screenshot : 

API Pull Screenshot :  

I am attaching the API Output file. We have already submitted the Payload. Let us know if we can provide more details.

What I responded: (Also telling them i was going to reach out here for assistance)
I noticed that in the API pull screenshot it says {{ad.id}}. At least when it comes to our UTM Tracking Suffix, i know the period is supposed to be an underscore, so {{ad_id}}. I'm not sure if this applies to the API but I just wanted to flag it for you.

Thanks,

Alexis

[bryn.whitcomb]

Hey Alexis, 

I'm not able to see the images you attached, could you try sending them again?

Also, can you share:

• The email of the user pulling this data
• The exact endpoints the client is using to retrieve this data, complete with IDs and parameters they might be using
• Whether they are using any 3rd party platform to connect to our API

Best,

Bryn

[Alexis Surabian]

Images attached. Also I will send the questions to the client today for the other three questions. 

[Alexis Surabian]

Here are their answers:

1. We are using email user : vcho...@coredigital.com and marketer id is : 00930517e897a86e6637154dd7449f9ced. We have retrieved the OB Token and using it for authentication.
2. Endpoint details : 
   1. Base URL : https://api.outbrain.com/amplify/v0.1
   2. Endpoint 1 : GET /marketers/00930517e897a86e6637154dd7449f9ced/campaigns
   3. Endpoint 2 : GET /reports/marketers/00930517e897a86e6637154dd7449f9ced/campaigns/{campaign_id}/periodicContent
3. We are not using any third-party platform. Our API script is calling Outbrain Amplify API directly.

[Alexis Surabian]

Bryn,

Just checking in on this. 

Best

Alexis

[bryn.whitcomb]

Hey Alexis, 

Thanks for all this info and sorry for the delay!

I believe the reason for the confusion is that the "landingPageDetails" object taken from endpoint #1 does not reflect the actual ad landing page URLs. Instead, this field is taken from the URL entered in campaign settings when the campaign is created, see attached screenshot. This field does not dictate the URLs of any ads within the campaign in any capacity, it's only used to determine the campaign's category. 

As for the issue with ad name not being shown, this is because neither of these endpoints are meant to return ad name data. In order to retrieve it, they should use the following endpoint, which gets promoted links by campaign: https://api.outbrain.com/amplify/v0.1/campaigns/{campaign_id}/promotedLinks

The ad name will be shown in the field called "text" (see documentation here). 

Please let us know if they have any further questions!

Best, 

Bryn