- This topic has 5 replies, 3 voices, and was last updated 1 month ago by
.
-
Posts
-
Heyy, we're in a bit of a weird place with out instance of the Newsletter plugin. Our website can't run it natively because it'd break the website, so instead we're sending out newsletters with a backend-server connected to AWS SES. Thing is, the link tracking ends up trying to send it to the AWS address of the website first which is really awks.
What's the best way of doing this? Ideally we'd want the links to be there rather than send a newsletter with a backlink to our website but pointed via tinyURL or something :/
Thanks so much!
Amrit
Hello Amrit,
I'm sorry but I don't think I understood what is going on here : ) Could you describe your situation again?
Thanks,
MichaelHey Michael, apols! Will try to set it out in a neater way.
We have two hosts which sit in AWS, iplato.com and mygp.com
We have a separate server which is running a WP instance specifically to send out newsletters, this is using Amazon SES but is not web-accessible. Our marketing peeps wanna have link tracking but naturally it's pointing back to the webserver to try give reporting.
What I'm wondering I suppose if there is a different way to get those tracking stats without making the backend server available to an external networking, for the two websites they aren't on a VM muscley enough to handle the web-traffic if like 100k peeps click the backlinks.
I hope that helps?
Thanks a bundle,
AmritHello Amrit,
now it's all clear, thanks for the clarification. I'll ask our developers if this is doable, however it is a very particular situation which we normally cannot give support to.
Michael
Hi, if you can expose just the "home" of the site managing the newsletter and set the action links on Newsletter/Settings to the standard format, the tracking link reach the newsletter manageing site and then will be redirected.
You can possibly write a rule to accept a link only if it contains the na=aaa parameter.Hey Stefano, Michael! Thanks so much and yes I know it's a bit of an awkward setup, the main reason is that the main site hosted on AWS can't hack like, a gazillion clicks because of a false-economy cost saving they were forced to go through.
I totally get that the Newsletter plugin is designed to be an all-in-one addition to a functional, externally accessible website.
Please don't go through the trouble of bothering the devs about this! It sounds like the answer is a no, by design, and that's totally OK - we can use an external link provider to give marketing stats while also reducing load on the server.
Thanks both 🙂
Amrit
- You must be logged in to reply to this topic.