Newsletter Studio in staging/productive environment
Hallo,
I have a question about how to realize following scenario:
We have Test, Staging and Production environment. All editors work on Staging. They want to send newsletters from there. They cannot login to the production environment. Where do we have to install Newsletter Studio? Are there any solutions to use whole functionality (subscribe, unsubscribe, tracking,...) of Newsletter Studio without to install on production environment?
Newsletter Studio is built to work in the enviroment where it is installed - as the tracking and so on all points to the same domain as the editors send from. So if you're sending from the stage enviroment, tracking and unsubscribing will point to this enviroment.
I guess that you could run the package in the stage enviroment but that would mean that the recivers will get unsubscribe-links and links to "read online" that points to the stage enviroment which I guess is not a good idea?
Depending on your excat needs we could swop some of the defult features and replace them with custom ones so that ie. relative links to the stage-enviroment would be replaced with links to the production enviroment.
If you want to talk about details, don't hesitate to send me an email: markus [at sign goes here] enkelmedia.se
Newsletter Studio in staging/productive environment
Hallo,
I have a question about how to realize following scenario:
We have Test, Staging and Production environment. All editors work on Staging. They want to send newsletters from there. They cannot login to the production environment. Where do we have to install Newsletter Studio? Are there any solutions to use whole functionality (subscribe, unsubscribe, tracking,...) of Newsletter Studio without to install on production environment?
Thank you for your feedback
Heiko
Hi!
Newsletter Studio is built to work in the enviroment where it is installed - as the tracking and so on all points to the same domain as the editors send from. So if you're sending from the stage enviroment, tracking and unsubscribing will point to this enviroment.
I guess that you could run the package in the stage enviroment but that would mean that the recivers will get unsubscribe-links and links to "read online" that points to the stage enviroment which I guess is not a good idea?
Depending on your excat needs we could swop some of the defult features and replace them with custom ones so that ie. relative links to the stage-enviroment would be replaced with links to the production enviroment.
If you want to talk about details, don't hesitate to send me an email: markus [at sign goes here] enkelmedia.se
/ m
is working on a reply...