Profile_bird

Hey there! FeedBurner is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving FeedBurner's tweets.

Already using Twitter
from your phone? Click here.

FeedBurner

  1. @portermason Looks like mail was sent today; could it be in your spam folder? 5:07 PM Nov 30th from web in reply to portermason
  2. @imrogb Turn off utm_params. Sign in to FeedBurner>Select Feed>Select Configure Stats>Uncheck 'Track clicks as a traffic source ..." 2:53 PM Nov 23rd from TweetDeck in reply to imrogb
  3. @michlib Filing a bug with http://www.soapblox.net/ to allow utm parameters is probably not a bad idea either. 7:44 AM Nov 23rd from Tweetie in reply to michlib
  4. @michlib Turn off utm_params. Sign in to FeedBurner>Select Feed>Select Configure Stats>Uncheck 'Track clicks as a traffic source ..." 7:43 AM Nov 23rd from Tweetie in reply to michlib
  5. @provirtual It looks like your feed has them. (view source on your feed). Check the WP docs to see if there's any reason they might change. 11:42 AM Nov 20th from Tweetie in reply to provirtual
  6. @provirtual The best way to make sure that you don't have old posts in email is to give each item a guid and make sure it doesn't change. 9:11 AM Nov 20th from Tweetie in reply to provirtual
  7. How to manage the Google Analytics tracking parameters (i.e., utm_ params) in your feed's clickthrough links: http://pic.gd/e5fcc1 8:06 AM Nov 20th from TweetDeck
  8. @Pam_Spaulding Turn off utm_params. Sign in to FeedBurner>Select Feed>Select Configure Stats>Uncheck 'Track clicks as a traffic source ..." 7:01 AM Nov 20th from TweetDeck in reply to Pam_Spaulding
  9. @Pam_Spaulding Your blogging platform is having difficulty with url query params. Disable the FeedBurner Click-Analytics feature to fix. 7:46 PM Nov 19th from TweetDeck
  10. @sogrady wrt Google Analytics this announcement from today may be of interest to you. http://tr.im/ET2V 8:02 AM Nov 13th from Tweetie in reply to sogrady
  11. @wealer There is currently an issue with us retrieving Pipes feeds. We are working with Yahoo to get it resolved. 5:40 PM Nov 12th from TweetDeck in reply to wealer
  12. @WellHeeledBlog looks like your Reader/iGoogle numbers dropped. An occasional 1-day blip from time to time. May bounce back tomorrow. 7:32 PM Nov 11th from Tweetie in reply to WellHeeledBlog
  13. @jorenrapini Yep. There's a <div> and a <script> at the end of the feed (after the </rss>). Use the feed validator to see the issue. 12:24 PM Nov 11th from Tweetie in reply to jorenrapini
  14. @jorenrapini There's trailing junk at the end of your source feed. Sensitive XML parsers don't handle that gracefully. Check your feed. 11:58 AM Nov 11th from web in reply to jorenrapini
  15. @egordin None yet. We're waiting on news from the Pipes team. 9:11 AM Nov 11th from Tweetie in reply to egordin
  16. @fredchannel They should be available under Publicize-Email Subscriptions-Subscription Management-View Subscriber Details (at the bottom) 8:48 AM Nov 11th from web in reply to fredchannel
  17. Yahoo Pipes feeds are currently having issues connecting to FeedBurner. Although we don't have an ETA Yahoo is working to restore access. 7:24 AM Nov 10th from Tweetie
  18. @cullenfamily You can't burn @twitter feeds because they limit the number of requests from a single client (i.e. us). http://bit.ly/Hcx2a 12:28 PM Nov 5th from Tweetie in reply to cullenfamily
  19. Reach stats are available albeit a bit tardy today. Issues that have caused the delays over the last few days should be addressed now. 11:48 AM Nov 3rd from web
  20. @centsiblelife Hi again. Reach has been a bit bumpy the last few days. We're working on getting it back now and for the future. Apologies. 11:31 AM Nov 3rd from web in reply to centsiblelife