In order to make the most of the features in Campaign Enterprise, you need to configure it correctly in your network. The response event tracking, and web based unsubscribe features all require Campaign Enterprise to be associated with a public IP and domain name. Accessing the program remotely from outside your network also requires you to associate campaign with a public facing address.
When you first open Campaign and log in, you will notice the IP address in the browser window is http://127.0.0.1:81. This IP is the local IP address for your computer; and every computer. The tracking features will only work when implemented or activated on the local machine. This configuration works great for testing the actual functioning of the links you create and ensuring the features write back to your database. However, once you want to go live to your customers, you must change this information to a public address.
Basically, Campaign has a built in web server that serves up its own interface pages and also the click through links and web based unsubscribe page. The image request for the tracking link is made to the Campaign server, if it is not public facing, none of these features will work for your customers. So, in order to configure Campaign for these features, here is what you need to do.
Click on the image below to see one example of how to configure Campaign in your network.
There are as many different possible network configurations as there are networks. This is just one example of the various pathways Campaign uses to connect to your network computers. Your IT personnel may have different requirements for their network. Those differences must be worked out with them and are not necessarily configured in Campaign. Once you get your Campaign Enterprise associated with a public facing address, you can take full advantage of the response events and web based unsubscribe features.