Development Solutions/Flutter & Dart

[Solved] AdMob Error Codes & Logs (오류 코드 및 로그)

studio ODOC 2024. 7. 21. 08:58
반응형

AdMob Error Codes & Logs

오류 코드 및 로그

 

 

 

 

[Eng]

Common Error Codes are :

 

  • Error Code 0 : ERROR_CODE_INTERNAL_ERROR
This indicates that something happened internally; for instance, an invalid response was received from the ad server.

Newly created Ad Units can take upto 2 hours to become active (SpinUp Time). Any Ad requests from newly created Ad Units would also receive Error Code 0 in response to Ad requests until they are ready to serve live ads.

What to do? Test Ads!!
 

 

  • Error Code 1 : ERROR_CODE_INVALID_REQUEST
The ad request was invalid; for instance, the ad unit ID was incorrect.

This commonly suggests that the Ad Request implementation is not as per the SDK’s requirements - Resources like the  sample codes and sample apps provided in the developer documentation can help in implementing the functions correctly.
 

 

  • Error Code 2 : ERROR_CODE_NETWORK_ERROR

 

The ad request was unsuccessful due to network connectivity.  

This could be due to a user’s phone switching networks or network disturbances distorting the communication between the app and the Ad Server. Some Telecom providers may also limit specific traffic due to policy, which can also lead to such an error.



  • Error Code 3 : ERROR_CODE_NO_FILL
Description (Dev Docs Link) : The ad request was successful, but no ad was returned due to lack of ad inventory.

Why is  it Happening : Advertisers can target specific regions, platforms and user profiles based on business relevance, which can sometimes result in lower availability of Ads for a particular region or user profile. Error code suggests that the implementation is correct, and that the Ad Request was not filled because of lack of availability of a suitable Ad at that particular instant of time when an Ad Request was sent from the app.

Policy related restrictions on certain Apps or Ad Units will also lead to Error Code 3 being returned in response to Ad Requests.

What Can The Pub Do About it :

→ As we cannot manipulate advertiser demand, there are no particular ‘fixes’ for this error - the pub can cross-check the Ad Unit implementation to ensure that the Ad Units are implemented correctly.

→ Mediation : In some instances, certain Ad Networks may have limited performance in some regions or for specific formats, in which case the pubs can try using mediation to add other Ad Networks that may potentially perform well.

→ Check for Policy status for the Pub ID, the App and the Ad Unit ID. Also check the Brand Safety flags and Coppa status.

→ If the Pub can obtain Test Ads for an Ad Unit (Instructions) - then their implementation is correct, and the Ad Units will serve Ads normally when an Ad is available depending on advertiser demand.

 

[한국어]

오류 코드 0 : 오류_코드_내부_오류
내부적으로 문제가 발생했음을 나타냅니다(예: 광고 서버에서 잘못된 응답이 수신됨).

새로 생성된 광고 단위가 활성화되기까지 최대 2시간(스핀업 시간)이 소요될 수 있습니다. 또한 새로 만든 광고 단위의 모든 광고 요청은 라이브 광고를 게재할 준비가 될 때까지 광고 요청에 대한 응답으로 오류 코드 0을 받게 됩니다.

어떻게 해야 하나요? 광고 테스트!!


오류 코드 1: 오류 코드_INVALID_REQUEST
광고 요청이 유효하지 않습니다(예: 광고 단위 ID가 잘못되었습니다).

이는 일반적으로 광고 요청 구현이 SDK의 요구 사항에 맞지 않음을 나타냅니다. 개발자 문서에 제공된 샘플 코드 및 샘플 앱과 같은 리소스는 기능을 올바르게 구현하는 데 도움이 될 수 있습니다.


오류 코드 2: 오류 코드_네트워크_오류

네트워크 연결 문제로 인해 광고 요청이 실패했습니다.  

이는 사용자의 휴대폰이 네트워크를 전환하거나 네트워크 장애로 인해 앱과 광고 서버 간의 통신이 왜곡되었기 때문일 수 있습니다. 일부 통신사의 정책으로 인해 특정 트래픽을 제한하는 경우에도 이러한 오류가 발생할 수 있습니다.



오류 코드 3 : ERROR_CODE_NO_FILL
설명 (개발 문서 링크) : 광고 요청이 성공했지만 광고 인벤토리 부족으로 인해 광고가 반환되지 않았습니다.

발생 원인: 광고주는 비즈니스 관련성에 따라 특정 지역, 플랫폼 및 사용자 프로필을 타겟팅할 수 있으며, 이로 인해 특정 지역이나 사용자 프로필에 대한 광고의 가용성이 낮아질 수 있습니다. 오류 코드는 구현이 올바르게 이루어졌으며 앱에서 광고 요청이 전송된 특정 시점에 적합한 광고가 없어 광고 요청이 채워지지 않았음을 나타냅니다.

특정 앱 또는 광고 단위에 대한 정책 관련 제한으로 인해 광고 요청에 대한 응답으로 오류 코드 3이 반환될 수도 있습니다.

펍이 할 수 있는 일 :

→ 광고주 수요를 조작할 수 없으므로 이 오류에 대한 특별한 '수정'은 없으며, 퍼블리셔는 광고 단위가 올바르게 구현되었는지 확인하기 위해 광고 단위 구현을 교차 점검할 수 있습니다.

→ 중개: 특정 광고 네트워크가 일부 지역 또는 특정 형식에 대해 제한된 실적을 보이는 경우가 있는데, 이 경우 퍼블리셔는 중개를 사용하여 잠재적으로 실적이 좋은 다른 광고 네트워크를 추가할 수 있습니다.

→ 퍼블리셔 ID, 앱 및 광고 단위 ID에 대한 정책 상태를 확인합니다. 또한 브랜드 세이프티 플래그와 코파 상태도 확인합니다.

→ 퍼블리셔가 광고 단에 대한 테스트 광고를 얻을 수 있는 경우(지침) - 구현이 올바른 것이며, 광고주 수요에 따라 광고를 사용할 수 있을 때 광고 단에서 광고를 정상적으로 게재합니다.

오류 코드를 검토하면 새 광고 단위를 구현할 때 낮은 일치율 또는 광고가 반환되지 않는 등의 문제에 대한 문제 해결 노력을 최적화하는 데 도움이 될 수 있습니다. 포럼에 문제를 보고하거나 Google 지원팀과 소통할 때 오류 코드와 로그(찰스 로그 및 네트워크 추적)를 포함하는 것이 좋습니다.

반응형