Hello, still trying to get an answer on this… When using the blog-post content type for the Get data for Hubspot hosted content, it returns the blog post ID as the breakdown. We then use the List blog posts endpoint to get the names of each of those blog posts. However, we just ran into an issue where one or more of the blog post IDs returned by the analytics endpoint has a hyphen in it. These IDs do not appear in the blog post endpoint.
A couple of the IDs are “591062-203027” and “591062-203026”. It appears they are all starting with “591062”. I am wondering why some of them suddenly have hyphens.
Sincere apologies for dropping the ball on this thead… I completely missed your replies. Going forward, please be sure to tag me with @IsaacTakushi and your message will be much less likely to fall through the cracks.
I took a closer look and found the following:
The hyphenated “ID” is actually a legacy analytics_page_id which predates the current analytics system. It is combines the following values…
The591062 string corresponds to anotheranalytics_page_id field as well as alegacy_tab_id which I had not previously encountered.
The strings which follow theanalytics_page_id orlegacy_tab_id correspond to legacy blog post ID (legacy_id) values. If you retrieve blog ID 1936716288 from this endpoint, for example, you will find the analytics_page_id is a hyphenated 591062-188883 . The legacy_id value is even visible in old blog post URLs like: https://info.gbiosciences.com/blog/bid/188883/what-are-the-detergents-commonly-used-in-proteomics.
I’ll pass this insight along to the team and find out whether we can rectify the legacy analytics and blog IDs with our “new” IDs.
@IsaacTakushi, is there a better way for me to get names for multiple blogs then? Without having to go through all of them.
What I was doing, was taking the ID given by the blog-post breakdown from the analytics endpoint and matching it up to the IDs given from the blog endpoint (in order to match the blog post name with the analytics metrics, because an ID means nothing to our users). As you know, I was using an undocumented parameter to filter only the blog-post IDs returned from the analytics endpoint. However, that undocumented parameter does not work for the legacy IDs with a hyphen in them.
I can match the legacy ID to the analytics_page_id field on the blog posts but that means I now have to page through every blog post until I find all the ones I’m looking for. Is there a better way to filter the blog posts to get all blog posts I need with fewer API calls?
Unfortunately, I haven’t found a way to filter blog posts in that way. At this time, the only viable option I see for legacy IDs is to page through the results of the List blog posts endpoint.
I will see if that undocumented filter parameter can be made public. That, along with potential changes to how the Analytics API accounts for legacy blog IDs will be the best long-term solution for your use case.