Budget Optimizer enabled

Discussion in 'Google AdWords' started by Kronos, May 20, 2006.

  1. #1
    Hi all,

    Im new to Adwords so i thought i would enable the "Budget Optimizer" to automatically adjust my CPC. The bad thing is that im paying anything upto $1.35 per click which seems a little high to me. The good thing is my ad is maintaining 1st position. So far i have had the campaign running for about a week with 3,541 impressions 163 clicks and 1 conversion. Would you say that using this option is a more cost affective way or should I use the convensional way of adjusting CPC manually? does anyone else use the "budget Optimizer"?

    Thanks
     
    Kronos, May 20, 2006 IP
  2. advanet

    advanet Peon

    Messages:
    77
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #2
    With Budget Optimizer you should be improving number of clicks. Price wise, the cost will be not much different.
     
    advanet, May 21, 2006 IP
  3. Kronos

    Kronos Peon

    Messages:
    11
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Ok, thanks
     
    Kronos, May 22, 2006 IP
  4. dougadam

    dougadam Active Member

    Messages:
    495
    Likes Received:
    10
    Best Answers:
    0
    Trophy Points:
    58
    #4
    You must have set you're bid high.
     
    dougadam, May 23, 2006 IP
  5. Art

    Art Peon

    Messages:
    711
    Likes Received:
    17
    Best Answers:
    0
    Trophy Points:
    0
    #5
    In all honesty, it depends on a number of factors - your targeted niche, your competition etc. However, once you get a greater grasp on things you may consider setting things manually.

    If you really want to save money, increase your quality score by a) rewriting your ad or b) optimizing your keywords for relevance.

    Hope this helps :)
     
    Art, May 23, 2006 IP
  6. Kronos

    Kronos Peon

    Messages:
    11
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #6
    Thank you all
     
    Kronos, Jun 6, 2006 IP