Skip to main content

​
Why is my Apple Search Ads connection stuck in a pending state?

Apple Search Ads uses a two-phase setup, so a new connection stays pending until it is finished. The first phase records the account, and the second phase collects the three credentials Apple issues from its developer console: the Client ID, Team ID, and Key ID. Until those three values are supplied and validated, the connection remains pending and does not import data. To resolve it, the account owner completes the pending form with the Client ID, Team ID, and Key ID generated in Apple’s UI. When the form is submitted, Adriel runs a validation call against the ad account. If that call succeeds, the connection activates and the account’s name and currency are filled in automatically; if it fails, the connection stays pending. See How to connect Apple Search Ads to Adriel for the full walkthrough.

​
Why did my connection return to pending on its own?

Apple can invalidate the API signing certificate tied to a connection without warning. When that happens, the credentials Adriel holds can no longer authenticate, and the connection drops back to a pending state. Recovery is the same second phase as the initial setup: regenerate the API client in Apple’s developer console and re-enter the refreshed Client ID, Team ID, and Key ID in the pending form. Once the new credentials validate, the connection reactivates and reporting resumes.

​
Why do wide date ranges take longer to load?

Apple Search Ads report queries are broken into smaller pieces before being sent to Apple’s API, and the results are stitched back together afterward. Two factors drive this:
  • For ad group, ad, and keyword levels, Apple requires the campaign in the request path, so the query is split into one call per campaign.
  • For daily granularity, each request is capped to a 60-day window, so a long date range is fetched as several sequential windows.
The wider the date range and the more campaigns in scope, the more calls run behind the scenes, which is why large pulls take longer than a narrow one. Narrowing the date range, or breaking down at the campaign level rather than a deeper level, reduces the number of calls and speeds up loading.

​
Why can’t I see ad-account-level report rows?

Apple Search Ads does not expose an ad-account report level. Report data is available at the campaign, ad group, ad, and keyword levels only. Where an ad-account-level row would normally appear, Adriel substitutes the campaign level so the request still returns data. For an account-wide figure, the campaign breakdown aggregates every campaign in the account. The ad-account row itself may look empty because there is no account-level data to populate it.

​
Why are my keyword breakdowns empty?

Keyword and search-match-type breakdowns apply to Search campaigns only. For campaign types that do not run on keywords, these breakdowns return no rows, so a widget grouped by keyword shows nothing for those campaigns. Grouping by keyword is expected to return data only where Search campaigns are present in the selected scope.

​
Common issues

Apple Search Ads connections are always Pending by default and require Adriel back-office validation.Steps:
  1. Invite asset.connection@adriel.com to the Apple Search Ads account per the academy guide.
  2. An Adriel PM retrieves the clientId, teamId, and keyId and validates the source in the back office.
The customer does not provide the key ID.