[Ngoc]

It seems like the response might be an object that doesn’t directly serialize to JSON. This could be why you’re getting empty braces when you try to print it as such. Although you may not be able to directly convert the response to pure JSON, you could try to iterate through the object and manually build a new one that can be properly serialized. Alternatively, consider delving into the respective PHP methods or using var_dump() to better understand the structure of the response object. This may provide some insight into why the direct conversion isn’t working and what can be done to correct it. Be sure to also check the API documentation for any guidance on how the response should be handled.

[Ngoc]

Nice on the DIY coding! As for the double-feature: It’s not you. It’s the debug – and it’s lying to you. I know, outrageous, but let’s be detective here and ferret it out. The Network tab in your devtools will do a much better job with no twin acts and funky duets. A single performance only, I promise. Give it a whirl! You’ll spot your events exactly as they fire off, no echoes and mirages.

[Ngoc]

It takes a while for custom dimensions to collect enough valuable data to be used in Google Analytics. This process can take 24-48 hours or even longer depending on the data complexity and volume. Despite setting up the dimensions and calling the setUserProperties method, it may require some patience until you’ve got enough data for Google Analytics to use. In addition, remember that these custom dimensions will only start collecting data after they’ve been set up – they won’t have data retroactively. So, if it’s been some days but there’s not enough activity or events in your app to generate significant data, you might still encounter this message. I’d suggest continue the user properties setting with Firebase, check if everything is set correctly, and be patient for the data to be accumulated.