Missing "ad_name" data on API reports

[Veronika Breslaw]

Hi team, 

My client is having trouble with ad_name parameters in some of the ads in their reports. 

Attaching one of such report examples. As you can see from the report, some ad names are populating fine and some appear as {{ad_name}}.
Can you please check what the problem could be or we can also hop on a call with the client ( they are super savvy and knowledgeable).

They say there is no pattern in when it pulls the correct ad name and when it appears as  {{ad_name}}.

Here is the Json body: GET https://api.outbrain.com/amplify/v0.1/reports/marketers/ACCOUNT_ID/promotedContent?from=2025-11-01&to=2025-11-01&limit=100&offset=0&breakdown=

Headers: OB-TOKEN-V1: ACCESS_TOKEN

Attached are screenshots of the needed ad name vs the {{ad_name}}: 

[Veronika Breslaw]

Hi team, 

I'm just following up here.

[Ales Kesar Valenko]

Hi Veronika, 

We're investigating, and will get back to you shortly. 

Best regards, 

Aleš

--
You received this message because you are subscribed to the Google Groups "Outbrain-AmplifyApi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to outbrain-amplif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/869a4a8f-2626-45bb-9411-2a4d9d4d6d16n%40googlegroups.com.

--

Ales Kesar Valenko Demand Technical Solutions Team Lead e | ales.kes...@teads.com

The information in this email is confidential and intended only for the addressee(s) named above. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. Teads does not warrant that any attachment(s) are free from viruses or other defects and accepts no liability for any losses resulting from infected email transmission. Please note that any views expressed in this email may be those of the originator and do not necessarily reflect those of the organization. For more information or feedback, contact us here.

[Ales Kesar Valenko]

Hi Veronika, 

The ad_name is basically the metadata, or the param that you set only on the Amplify dashboard. 

But if the client wishes to obtain the title of the ad, then they should reference the text field: 

In case of additional questions, please let me know. 

Best regards, 

Aleš 

[Mariia Yatsenko]

Hi team,

I'm the client who has faced this problem. Could we please set up a quick call with our technical specialist so we could solve this issue more effectively? 

Kind regards,
Mariia

[Veronika Breslaw]

Dear Ales, 

The client really needs your help. 

This has been going on for a while now. Please address the issue. 

Thank you 

[Ales Kesar Valenko]

Hi Veronika and Mariia, 

Apologies for taking a bit longer to get back to you, I was checking the available information, to provide you with an answer. 

I noticed we're not looking at the right data. The first two images that Veronika shared show some sort of a log, after a conversion happens - I'm assuming you obtained this from your website logs, Mariia? 

In the first one we see a lot of information, together with the clickId, publisher and section id, etc. But in the second one, we don't see this information, so here I'm assuming that the traffic in the second screenshot didn't come from Outbrain. I cannot be sure - here I'm assuming, based on the available data. 

The above mentioned has nothing to do with our API services.

The call that was attached in the first email (https://api.outbrain.com/amplify/v0.1/reports/marketers/ACCOUNT_ID/promotedContent?from=2025-11-01&to=2025-11-01&limit=100&offset=0&breakdown=), retrieves the available info correctly. 

Tha main questions here is, at what data we're looking at from the first and second screenshot, and further - If Mariia want's us to further investigate this, the Veronika please open a DO case. 

Best regards, 

Aleš 

To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/8a9dbca3-c0d5-4122-80a5-4121e9f0ea01n%40googlegroups.com.

[Veronika Breslaw]

done - https://outbrain.lightning.force.com/lightning/r/Case/500Tg00000U67fBIAR/view

--

Veronika Breslaw Senior Account Manager e | veronika...@teads.com

[Mariia Yatsenko]

Hi Aleš!

Let me try to explain the issue once again and share our hypothesis on why it might be happening, as it seems there may still be some misunderstanding from both sides.

Recently, we noticed that it became possible to put ad names in our dashboard and pass the ad name into the UTM parameters using the macro {{ad_name}}. This is extremely valuable for us because we dedicate significant time to creative analysis, and we use our internal naming system which greatly supports the evaluation process. On our side, we successfully matched ad_id with ad_name, allowing us to view performance data based on the ad name rather than just the ad ID.

However, over the past few months, instead of receiving our ad names in the reports, we are getting the literal {{ad_name}} value. This significantly affects our ability to correctly assess creative performance.

Additionally, the screenshots provided by Veronika show what we see in our logs, after a user completes a conversion:

• On the second screenshot (image 61), instead of the standard numeric Outbrain click ID, we receive {{ob_click_id}}, which prevents us from obtaining not only the ad_name, but also publisher_name and section_name making publisher-level analysis impossible.

• On the first screenshot, the data appears correctly.
  The paradox is that these were two different users coming from the same ad_id, which confirms they were both from Outbrain (I highlighted them on the screenshots). We have fully verified our tracking setup internally, and everything is working correctly on our side.

We would really appreciate your help in understanding why this discrepancy occurs and how we can resolve it together.

If it's more convenient for you, we’re happy to jump on a call together with our technical specialists to go through the details and identify the root cause.

Thank you in advance for your support.

Kind regards,
Mariia

[Azalea Creatives]

I really hope you guys are able to resolve this pressing issue and make great gains in your professional careers. But why am I on this thread?

To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/e46d9bae-f9b8-40a3-9f4e-1dfd49f9c6a4n%40googlegroups.com.

[Ales Kesar Valenko]

Hi Mariia, 

Thank you for your feedback. 

At the same time Maria, I'd like to ask that you share with us a log from a broader period - like for a week or two weeks, so we can see if there are any patterns. Also; when did you first notice this, that it started appearing, did you change anything in that period in regards to the setup, anything similar? How do you gather the logs/reports - after you send the data to us, to count the conversion, or before that? Are you using any 3rd party solution for the reports? 

At this point I'm assuming you're using a S2S implementation (server to server), which offers us limited options of troubleshooting - just to manage expectations. 

@Veronika Breslaw please wait for Mariia's feedback and update the case with the info.

Best regards, 

Aleš  

To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/e46d9bae-f9b8-40a3-9f4e-1dfd49f9c6a4n%40googlegroups.com.

[Mariia Yatsenko]

Hi Aleš!

I sent you a private email earlier ('reply to an author'), but I don’t see it on my side.
Could you please let me know if you received it?

Kind regards, 
Mariia

[Ales Kesar Valenko]

Hi Mariia,

Thank you for letting me know. 

I can confirm I've received the email. I'll include it in the opened case and we'll do our best to provide you with insights as soon as possible. Due to our process, from the opened case, we'll inform Veronika who'll inform you. 

Best regards, 

Aleš 

To view this discussion visit https://groups.google.com/d/msgid/outbrain-amplifyapi/2dfdceb0-d2b7-4016-b740-4fde6913c8b2n%40googlegroups.com.