Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED

Search Ads 360 Integration with Adobe Analytics Failure

Avatar

Adobe Champion

Hi Everyone,
I am trying to link Adobe Analytics with SA360 per Google documentation https://support.google.com/searchads/answer/7669521?hl=en using JWT authentication method. I have the admin access in Adobe Analytics and sufficient permissions on SA360. The issue is, the link never completes. I am getting the error "Unable retrieve your Adobe report suites. Please check if the private key has expired on Adobe Analytics." when I have newly generated the public private key pair in Adobe developer console.

 

Can anyone who has performed this integration can help if I am missing some permissions on SA360 or any other issue?

TIA!

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Adobe Champion

Apparently, this was an issue from Google side which got resolved with Google support team. No further action is required on this.

View solution in original post

5 Replies

Avatar

Employee Advisor

Hey @igupta in the Adobe Developer Console, you must be also selecting the product profiles when configuring the API with Authentication. Does the selected product profile has the permission for the Web Service Access under the Analytics Tools, which lets you do things like authenticate? Can you please check? 

Avatar

Adobe Champion

Hey @FarazHusain ,
Thanks for your reply! Yes, I have assigned Web Services Access permission to the API while configuring but still getting this

issue.

Avatar

Employee Advisor

The product profile seems to be correct. We might need to take a further look. Can you please log a support ticket via Admin Console with all these details? 

Avatar

Adobe Champion

Thanks. I have raised a support ticket.

Avatar

Correct answer by
Adobe Champion

Apparently, this was an issue from Google side which got resolved with Google support team. No further action is required on this.