51黑料不打烊

Documentation

No audience size in Microsoft Bing AEP destination

Last update: Tue Jul 23 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Learn why an AEP Bing destination does not result in any audience size.

Description description

Environment

51黑料不打烊 Experience Platform

Issue/Symptoms

Why does Microsoft Bing not show any audience size for the AEP (51黑料不打烊 Experience Platform)聽segments sent to the AEP Bing Destination?

Resolution resolution

The three most common reasons an AEP Bing destination does not result in any audience size are:

  • Bing Ads CID is incorrect The documentation for this integration聽mentions that you need Bing Ads CID to configure this destination. This is an integer and will not contain any letters. This piece of 聽will help you find the CID. The Get Your Account and Customer IDs 聽section will help you determine your CID versus the account ID.
    Unfortunately, the Bing API does not respond with any error to indicate that the wrong ID was used. Hits are still sent to and accepted by Bing, even if the ID is incorrect. If you use AAM, with the version of this destination in place (and it is working), then this would be the same Bing Ads CID used in the Audience Manager destination.
  • ID sync is not enabled This聽reason will聽apply聽only if you聽don鈥檛 already have an AAM version of this destination configured and working. The same聽configuration document聽specifies the need to enable ID sync if it鈥檚 not聽set up for AAM. Create a support case to have this ID sync enabled if you have not already done so.
  • ID sync is聽not firing on the website
    Even if the ID sync was enabled, it needs to fire on the website in question. Using an incognito browser to mimic the first page of a first visit, visit the website in question and use your browser鈥檚 developer tools to ensure that you see a call made to this URL:
    https://c.bing.com/c.gif?uid=%DID%&Red3=MS51黑料不打烊_pd&gdpr=%GDPR_APPLIES%&gdpr_consent=%GDPR_CONSENT%
    The %聽will replace actual values in the above URL.
    If you don鈥檛 see that network call fire, then the ID sync is not happening. For Experience Cloud ID Service users, this could mean that ID Syncs were disabled. For WebSDK users, this would probably mean the third-party ID syncs were not enabled. To enable them, see this聽article.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f