Uploaded image for project: 'Yell'
  1. Yell
  2. YELL-611

adding refcd & tsacr to destinationURL in BING campaign deployment fails

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: Bing-Integration
    • Fix Version/s: Bing-Integration
    • Component/s: AdMax
    • Labels:
      None
    • Environment:

      hosts file matches yell-ec-xml2

      Yell - Bid Manager - Bing Integration Pulse build 209

      Description

      Not sure if this is a requirement (hence low priority), but think it's worthy of opening a bug to track it.

      2 parts:

      1) In a campaign deployment request to ADS, keywords aren't created when refcd is in the destinationURL, like in the following example (note, I got the format from http://kbase.ri.thesearchagency.com/index.php/TSA_Referral_Tag_Process#MSN_Search ):

      I just tried sending a request with this:

      <icom:customURL>

      <icom:displayURL>

      {param1}

      </icom:displayURL>

      <icom:destinationURL>http:example.com/special.php?refcd=MS

      {OrderItemId}{MatchType}_special_offer</icom:destinationURL>

      </icom:customURL>



      keywords are not created. In the admax listener log I see the following exceptions:



      2012-04-18 19:26:17.387 (3) [pool-32-thread-1]: Caught other/unrecoverable API Error: "com.microsoft.adcenter.v8.EditorialApiFaultDetail"

      2012-04-18 19:26:17.556 (3) [pool-4-thread-2]: No new jobs to execute for type: [6]

      2012-04-18 19:26:17.665 (3) [pool-32-thread-1]: Exception [SEUser 20000014 KeywordChangeRequest add request: SQL error processing 10 pending add(s)]:java.sql.BatchUpdateException: Column 'disapprovedText' cannot be null

      at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:665)

      at com.carldunham.jst.db.Database.commitBatch(Database.java:722)

      at com.thesearchagency.searchengines.bing.contenteditor.dao.BaseDAO.saveErrorsInsertErrorsHelper(BaseDAO.java:1100)

      at com.thesearchagency.searchengines.bing.contenteditor.dao.BaseDAO.saveErrors(BaseDAO.java:529)

      at com.thesearchagency.searchengines.bing.contenteditor.changerequest.BaseChangeRequest.saveErrors(BaseChangeRequest.java:376)

      at com.thesearchagency.searchengines.bing.contenteditor.changerequest.BaseChangeRequest.handleAPIError(BaseChangeRequest.java:223)

      at com.thesearchagency.searchengines.bing.contenteditor.changerequest.BaseChangeRequest.makeRequest(BaseChangeRequest.java:139)

      at com.thesearchagency.searchengines.bing.contenteditor.BingContentEditor$RequestWorker.call(BingContentEditor.java:1375)

      at com.thesearchagency.searchengines.bing.contenteditor.BingContentEditor$RequestWorker.call(BingContentEditor.java:1352)

      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)

      at java.util.concurrent.FutureTask.run(FutureTask.java:123)

      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

      at java.lang.Thread.run(Thread.java:595)



      2012-04-18 19:26:17.666 (2) [pool-32-thread-1]: Bing Request Errors for accountID 10000012(KeywordChangeRequest)

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      id=13287, trackingID=b22b8ff5-2b65-42b3-a106-8449faa56651: , code=1326: , errorCode=CampaignServiceTooMuchAdTextInDisplayUrl: , message=The Ad Display URL has too much text.:

      .....



      Note that campaigns, ad groups and ads are created successfully in AdCenter, just not keywords. The ads have http:example.com/special.php?refcd=MS{OrderItemId} {MatchType}_special_offer as the destinationURL.



      Here's one of the failing keywords in content_editor_bing:



      mysql> select id from bce_adGroup where name like 'cdtest11%';

      -----

      | id |

      -----

      | 188 |

      | 189 |

      -----

      2 rows in set (0.00 sec)



      mysql> select * from bce_keyword where adGroupID=188 limit 1\G;

      *************************** 1. row ***************************

      id: 13273

      adGroupID: 188

      searchEngineIdentifier: NULL

      text: stamp duty calculator

      keywordType: Exact

      maxCPC: NULL

      exemptionRequest:

      destinationURL: http://example.com/special.php?refcd=MS{OrderItemId}{MatchType}

      _special_offer

      isPaused: false

      isNegative: false

      status: Active

      1 row in set (0.03 sec)

      2) I also tried having the destinationURL be <icom:destinationURL>http:example.com/special.php?refcd=MS

      {OrderItemId} {MatchType}

      _special_offer&tsacr=MS

      {AdId}

      </icom:destinationURL>

      but the request fails (before it's put on the queue) due to a SAXParserException

      -nothing is sent to AdCenter

      -I got the format from http://kbase.ri.thesearchagency.com/index.php/TSA_Creative_Tag_Process#MSN

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              caitlyn Caitlyn Duggan (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: