ReportBuilder Issue

[thomask32386125]

Is anyone having issues pulling a report from Reportbuilder to match SiteCatalyst Visitor Profile > GeoSegmentation > Cities?

I run the same report, for the same City, same date range, same reportsuite and in Reportbuilder there is no data being pulled in (yet SiteCatalyst is showing 2k visits).

Thanks,

Tom

[dkatz1]

Amazing!  I was just going to post the same exact issue for regions/countries. No data gets pulled and the request block is simply blank.  I have the latest version of the software.

[HaiTechEric]

Hi there, Product Manager for report builder, here.

I am running report builder version 4.7.34 and pulled a simple geo-segmentation cities report for yesterday in both reports & analytics as well as report builder (See attached screenshot). It looks like everything matches to me. I would check to make sure you are not comparing to instances, which is a default metric used by geo-segmentation reports in reports & analytics. Thanks.

[img]geoseg cities.PNG[/img]

[Alexis_Cazes_]

Hi Thomas,

You might want to download the  latest version of ReportBuilder.

Once you have done so and you are still experiencing the issue I will advise you to contact ClientCare as this might be a bug.

Best regards.

Alexis Cazes

[thomask32386125]

Alexis,

Seeing the post below this seems to be a Bug accross multiple versions of Reportbuilder.

How would you like me to report this to ClientCare?

Thanks,

Tom

[thomask32386125]

Eric,

Attached is a screenshot of the problem.  Same Reportsuite, Same Metric, Same Date Range in SiteCatalyst and Reportbuilder.

I just redownloaded the newest version as well.

Thoughts? or potential things I'm doing wrong to not see the same #s?

Tom

[HaiTechEric]

The only thing I see different between your two reports is the sort metric in reports & analytics is set to revenue instead of visits. I would try removing the revenue metric from that report view or add it to the report builder request to see what you get.

[HaiTechEric]

Strange, there is a bug that is causing this at the API level. I would contact Client Care and open a ticket to get this addressed. Provide them the details and report builder logs, and they should have everything they need to escalate this to engineering.

[HaiTechEric]

Sorry for the multiple responses, but I have found a workaround as the issues seems to be a problem with the select specific filter and capitalization between the web and the API. If you go into the top items filter and apply a contains search of "toronto", the correct value will return. This applies to any geo-segmentation report right now. [img]geoseg cities workaround.PNG[/img]

[thomask32386125]

Eric,

That worked.

I do agree that the API is breaking with the Capitalization of the word.

Please let me know when this gets resolved so I can change my report.

Thanks,

Tom

[HaiTechEric · Accepted solution]

Hi Tom,

When you file the ticket with Client Care, please post the incident number in this thread so I and other Adobe employees can keep an eye on it.

Thanks,

Eric

[thomask32386125]

Eric,

This is logged as: BUG#MCWS-1851.

Here is the ClientCare Correspondence:

Hi Thomas,

It was a pleasure assisting you today.

As discussed, I investigated further on this issue and it does look to be a Bug hence I am submitting this to our Engineering Team for further investigation.

Also, this issue only occurs when using a Filter. If you do not select any specific city and get a list of Cities it works fine and the data is returned as expected. Hence, you can use this as an option meanwhile this Bug gets fixed.

I would share an update as soon as I have more information available regarding the same.

Best Regards,

Abhijeet Mishra

Adobe Marketing Cloud Customer Care