All posts by David Zeidman

RETweet Released for The Raiser’s Edge

We are really excited to release our latest free product RETweet. Setup a Twitter phone type, add Twitter addresses to The Raiser’s Edge and for each constituent that has one and then follow their tweets directly from their constituent record.

Follow their activity, check out their followers and who they are following. From this connect to Twitter to easily respond their tweets or click on their links.

We are offering this plug-in for free.  Indeed it was offered for free to all those of you who signed up to our newsletter as a big thank you before the holiday season. If you missed our newsletter then sign up now and we’ll send you a link. For everyone else you’ll have to wait until the new year. If you want to have a preview then check out the screencast

Greater Segmentation with MailChimp and Chimpegration

Chimpegration Professional allows users to see a constituent’s email activity.  It shows which emails they received, what they opened and which links they clicked on. Chimpegration, both free and Professional allows you to segment a list on MailChimp‘s by exporting constituents into specific groups. However there is no way currently in Chimpegration to segment based on this activity. Chimpegration gives you a view of the MailChimp activity. It does not bring the data over into The Raiser’s Edge so it is not possible to segment on this data.

However, now MailChimp have released a new product Goooal. You can use Goooal in combination with your existing MailChimp lists to help segment your constituents. Whenever a person clicks on a link you can setup Gooal to put that constituent into a specific segment. Once they are in a segment you can target them based on their previous visits. If your newsletter has links to information on different areas of your cause this is a perfect way to target those constituents who are interested.

Goooal is a free addition to MailChimp and compliments Chimpegration’s seamless integration with The Raiser’s Edge.

The challenges of developing generic solutions for The Raiser’s Edge

We develop a number of different types of solutions that connect The Raiser’s Edge with third party applications. When this is done for one organisation the hardest challenge is getting the requirements to match the end user’s as closely as possible. However we also develop a lot for third party applications directly. Most recently we released Chimpegration but there have been many others that integrate many different areas of the application. With these clients the important point is not so much as to match one set of requirements exactly but to match as many requirements exactly!

I have yet to come across two organisations that have set up RE the same way. Sometimes the differences are small but sometimes they are very large. One recurring theme is that of phone/email types. The Raiser’s Edge seems to be relatively unique in its setup of these values. Not only are phones and emails stored in the same location but you can store them according to address type too. How does this match up with a third party web application that uses email address as a primary key? They may have one field for home phone, one for mobile and possibly one other. How do you get that tie in with the possibility of any combination of phone and email types? I have seen a whole plethora of regular phone types e.g.

Home
Business
Preferred
Home 1
Home 2
(etc)
Primary
Work
Company

Those are just the ones I can think of as I write this. And of course each of these could have a number after them.

Then of course there is the proliferation of email (or is it e-mail, etc) addresses.

What techniques do we use to overcome these issues? When we are working with a third party developer directly it is often in their interest to develop the configuration piece. This saves them a lot of development cost. This means that we simply say to them if you want us to update a phone number you need to tell us which type it is. This is then supplied in the file/webservice. Likewise when we supply that piece of data, we also send the phone type too.

Another solution is to build a configuration part to the application. This is what we did with Chimpegration. We allow the end user to map the fields that they want to synchronise so that they specify which fields on MailChimp map to the fields on The Raiser’s Edge.

The last solution is the least desirable. It is possible to simply say that the home phone number should be called “Home” and email address should be called “Email” – end of story. This is clearly the simplest and cheapest but unless you have a lot of sway over the organisations that you are selling to it is unlikely that you are going to get many buyers.

Phone and email types are perhaps the most obvious but what other issues can arise?

Where you are collecting business details, should these be added to an organisation or to a business address on the constituent record? Should you create a new constituent for the organisation? How can you be sure that it does not already exist in the system but under a slightly different name. One solution is to allow the end user to review the matches that have been made but this again adds to the development cost. It could also be prohibitive if the volume of data you are bringing in is large.

What about fields that do not have an obvious place in The Raiser’s Edge. One application that we worked with had an anniversary date. There is no such field in RE. We gave the end user the option to ignore the field, store it has the spouse relationship from date or store it as an attribute.

What happens if one organisation makes a field mandatory? When I work with an organisation directly I will ask them what mandatory fields they have set up on their system. If, as part of the process, I have to create a new constituent then I will ask them to give me a default value for that field. For a generic solution this has to be worked into the application configuration.

You can see much of this in action in Chimpegration where we account for mandatory fields and different combinations of phone types and emails. Check out the synchronisation screencast for a glimpse of this in action.

So all said and done is this type of solution to be avoided? Absolutely not! It is not cheap because of the extra work involved in making the application work for all types of organisations. When people complain about NetCommunity or Patron Edge integrating badly with The Raiser’s Edge hopefully this article will have given you some insight as to the skills required by Blackbaud in getting the integration to work well. (Update 15th Dec 2011: I should clarify that given the difficulty in developing generic solutions I actually believe that Blackbaud have done a good job with these integrations)

If you are a third party application wondering how to integrate with The Raiser’s Edge then speak so us. We are skilled at doing this and have done it a lot. We can either do it for your or we can share the development. When done well it is a great asset to your company and will bring Raiser’s Edge users to your application.

Introducing Blackbaud +1?

I’m a big fan of Google and a big fan of Blackbaud. What do the two have in common? I’m not sure really. They are very different companies offering very different product ranges. However one obvious difference that is currently affecting me day to day is the fact that whereas Google are changing their interface throughout to reflect a modern sleek approach, Blackbaud (for the their “Edge” range of products at least) are not. In fact, not only are they not changing the way they look and feel, these products are stuck in a design that is several generations old. Due to the nature of the products they are also very restricted as to what they can do.

At the Blackbaud Conference for nonprofits in Washington last month I saw a demo of new functionality in Blackbaud CRM. It was highlighted that this functionality is only available in the “webshell” feature set of the application (as opposed to the ClickOnce feature set). If you are not familiar with those terms then essentially the “webshell” is the functionality available for all in a browser whereas the ClickOnce functionality is available only on Windows. What this also means though is that the webshell can utilise html5 and not be restricted to Windows Forms. This means a beautiful upgrade of the user interface is possible with much less of a struggle.

With the news that there will not be an RE8 what does this mean to those on RE7? When I recently showed our Chimpegration application to MailChimp I felt the need to apologise for the way that The Raiser’s Edge looked. When you look at MailChimp’s website it is very cool and very funky, just as you would expect from a website devoted to email marketing that takes pride in the range of sophisticated email templates on offer.  Clearly there is a lot more technical wizardry to MailChimp than just the templates but if their site did not look good, you would be put off from creating a campaign through them. They could see that the RE7 interface was antiquated but were clearly impressed by the depth of functionality available to users which was matched in Chimpegration.

And that is the point. The most noticeable changes that Google makes in Gmail, calendar, docs, reader, etc are staring right at you in the form of the interface. But they also make a lot of functional additions too. With the release of RE7.92 Blackbaud will certainly make some good improvements but they cannot afford to stop there. The reason Google is updating is as a form of rebranding. Raiser’s Edge 7 does not have that luxury so it must shine with its functional enhancements and make them known as loudly as a new interface would do.

Blackbaud moving towards the future, just not all the way to Infinity (yet)

The past two weeks have been packed with all things Blackbaud. Last week was the Blackbaud conference in Washington DC and then this week in London. Being a big fan of all most things Blackbaud,  I had a great time, met some great people, got to meet the all new star cast at the top of the company and was pleasantly surprised by the announcements made.

Waiting for RE8 has gone from waiting with great anticipation and expectations in previous years to how we find ourselves now. We now know that RE8 will happen at some point (albeit probably under a different name) but the wait is over. We are no longer waiting for the next big thing, but for the little things. In past years we have been wowed by what was to come on the Infinity platform. This was exciting but left us wanting it without it ever arriving for the majority. Now however, looking at the new functionality in RE7; query lists, new lookup functionality, better dedupe features and being able to easily mark participants as attended, shows that despite its name (and its UI), RE7 is moving forward. Blackbaud is moving forward for everyone.

This was demonstrated so much more so in Blackbaud Mobile. The application allows you to promote campaigns through channels that may have been previously inaccessable to the majority of organisations. Allowing organisations to promote and give supporters the mechanism to  donate through text message and mirrored on a Facebook app, brings their technology offerings into this decade.

After being burned by the anticipation of the Infinity platform’s greatness for The Raiser’s Edge users, Blackbaud are quite rightly avoiding the risk of repeated vaporware. One such thread could, in previous years, come from the exciting news of Raiser’s Edge Mobile. This application will be native to iPhone, Android and possibly Blackberry, will allow users to access their RE database directly from their mobiles. After having looked at a prototype version, I am quietly confident that this application will make it in the near future. This is another step in Blackbaud’s progression of the RE7 platform into the modern age.

What is really exciting however is the technology required to enable this. There will need to be a webservice layer for The Raiser’s Edge. There has been this web service layer for a while now with the NetCommunity integration. However it has always been restricted to NetCommunity specific tasks with limited use for other applications. If Blackbaud do the right thing this time around and make the web service layer generic and open to all applications, all of a sudden we will integration with The Raiser’s Edge like never before from all sorts of web based applications.

It does not matter what it is called (RE7 or RE8, Infinity or not) it is the perception that Blackbaud’s offerings are going forward and not stagnating. With the wait for RE8, RE7 was left languishing. The risk was great that organisations would move away from Blackbaud to other platforms offering what Blackbaud should have been doing years ago. Now at least they are moving into the modern era.

Chimpegration – An integration between MailChimp and The Raiser’s Edge

It is finally here – Chimpegration. Integration between The Raiser’s Edge and MailChimp. With our free customisation you can export your email addresses directly from The Raiser’s Edge into your MailChimp lists, populating your merge variables in one automated process. Raiser’s Edge users have always been used to creating Word mail merges so that they can create sophisticated merge documents. Now they can do the same with email. Once the email campaign has been sent you can manage any bounces or unsubscribes directly from The Raiser’s Edge. Not only that, you can also add an action, appeal or attribute to any constituent with an email that was sent the campaign.

All that for free!

If you want more then we also offer a (paid for) Professional version appropriately called “Chimpegration Professional”. This allows you to synchronise activity between the two systems. This means that you can make use of MailChimp’s own forms to allow you users to update their own information. It then feeds back into The Raiser’s Edge. Equally any information you update in RE will feed back into MailChimp. Don’t worry, the review screen gives you complete control over which information is moved where. Also with this version you are able to see each constituent’s activity directly from the constituent record. See when they were sent the email, when they opened it and what they clicked on.

I was very pleased to have won a MailChimp integration fund award to integrate The Raiser’s Edge with MailChimp. It is such a great product and the possibilities for integration were enormous. The Raiser’s Edge manages donors really well but it never really made it into the world of email marketing. Of course there is integration with Outlook but that is not good enough when you need to send out thousands of newsletters. NetMail was a good start but their template design functionality was so limited. NetCommunity was better still but even with that product there are too many compromises (and it costs too). There are a lot of different email marketing applications out there but I have been using MailChimp for a while myself as part of my website newsletter. It has great functionality but I would never have used it if it had not been for two things; it is free for smaller volume users and it has a great API. Things could have been so different. Before looking at MailChimp I applied to get a developer licence at ConstantContact. I had to fill out a form and justify my use of it. I did that but they never even got back to me.

Chimpegration – Free

MailChimp – Free

Email marketing – now Free!

Blackbaud Conferences 2011

It is that time of year again. This year I shall again be speaking at the Blackbaud conference in Washington DC and in London a week later.  This year my session will look at whether we really should customise our databases. The discussion will centre around The Raiser’s Edge and around Blackbaud Enterprise CRM. What are the main reasons for customising the software? How do you go about it? What sort of things should you look out for? In the end will it really be worth it?

In Washington I shall be speaking Monday at 2.30pm in Chesapeake 3. In London I shall be speaking at 12.20pm in Edward 5&6.

There are lots of questions and hopefully my session will answer many of the questions and if not then enable you to find your own answers. Sometimes the hardest part of the process is knowing which questions to ask.

I would love to meet up with everybody. Last year in DC one of the complaints was that it was so hard to find anybody. I did contemplate coming the the conference in fancy dress – everyone would surely be able to find me then! A pirate? A cowboy, An alien? Anyway I am not sure that I would get through immigration so easily. I will be coming as myself (see here for a mug shot) but will be setting aside some time where I will sit in the main atrium at the conference centre. Follow my twitter feed @zeiddev for exact details of where I am.

 

A .NET Fix

This post is totally unrelated to The Raiser’s Edge and the API but in case others are having the same issue I wanted to describe how I fixed it. I have just spent the last several hours trying to get the progress bar to scroll in the marquee style. I had seen several posts referring to using a background worker to retrieve data from the database while the progress bar scrolled in the UI thread. It sounded like the right solution but it didn’t make a difference.

I read one post that helped. It said that before you instantiate your form you need to enable the visual styles.

Application.EnableVisualStyles()

When I ran my application all of a sudden not only was my progress bar scrolling nicely but all of a sudden I could see the graphical styles that I always had seen in Visual Studio but never experienced in my Winform applications.

Blackbaud Enterprise CRM Integrations

If you had not noticed, our website zeidman.info has had a make over. We have also added a new section of everything to do with Blackbaud Enterprise CRM and the Infinity platform. Some of the screencasts there were previously embedded in conference presentations so now they have a home of their own. We are really excited by what the Inifinity platform has to offer (even if it is slow coming to the majority of users). Now you can see for yourself the kinds of customisations that can be developed and just how powerful the platform can be.

Have you been working on any BBEC customisations that you would like to share? Have you seen any others out there in the wild. Leave a comment and let us know.