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

SMSc3.5: Custom urls for a new campaign does not get reflected in SMSc

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: unspecified
    • Fix Version/s: None
    • Component/s: SMSc
    • Labels:
      None
    • Environment:

      Operating System: Windows XP
      Platform: PC

    • Bugzilla Id:
      3683

      Description

      Project: SMSc3.5
      Test Env: yell-dev-mms1

      For newly created campaigns using , default
      Steps:
      1. Run deployCampaign request of adMaxServiceBinding to create a new campaign.

      • Use custom display and destination URLs by using newly added "displayURL" and "destinationURL" parameters in request
        2. Checked in content_editor_google database and observed that in keyword and adcopy tables, the entries contain custom urls used in step1.
        3. Now deployed a site using deployCampaign request of siteGeneration for same BpId
      • checked that the site has been created
        4. Log into SMSc3.5 using valid credentials
        5. Navigate to "Google Adwords Campaign Settings" tab and observe "Google Adwords Click URL"

      Expected:
      The Google adwords click URL must be the one that was set in step1 (customized).

      Actual:
      Observed that the values for both display URL and destination URL are default ones.

      Note:
      On re-deploying using the same adMaxService request, when the user re-logged into SMSc3.5 using same BpId. Observed that now the custom urls are shown properly in "Google Adwords Campaign Settings" tab.

        Attachments

          Activity

            People

            • Assignee:
              prashant.balikai Prashant (Inactive)
              Reporter:
              gurpreet.singh Gurpreet Singh
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: