Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
Using SNS for any notification use case where available is the default and defacto solution. It directly integrates with SES to configure both incoming email and email delivery responses.
Additionally, any notifications, such as CloudWatch alarms, are a good use case for SNS topics and allow us to fan out delivery as needed (pagerduty, email, etc)
Landing pages. Say, a webinar optin page. Or a lead magnet optin page. People can be persuaded to believe that others like the lead magnet and don't want to be left behind and also they can trust others opinions. So, having a widget on these pages that shows, "XYZ just signed up" can help with getting more sign ups. A widget that shows the amount of people that are looking at a certain page is also beneficial. The best thing to do, is to test at all times. See if the conversion rate is increased or if it drops. And test variations of the widget one at a time. Sometimes, it helps, but in some cases, one can see little difference. So the key is to test. We used it on a front page and we optimized it for speed. We saw that we had several things that slowed our site down. So we decided to take away some of the items. This included our widget from Provely. It does not take a lot of resources, but we were super savvy and wanted the optimal speed. We might revert back into adding it again, but for now, we stripped the page for all extra baggage so we were certain that we had the correct overview on the speed that was needed. The widgets can be less appropriate also, if one wants full attention to the copy on a page. This is also a savvy choice. So the key is to TEST, again... To determine if it helps or halts conversions. This example we are seeing on direct response sales pages in the make money online nice. They rarely use this. Some do. So again, testing will determine the effect. (A savvy user tests, but even those, skip it some times, so it is best to use your own due diligence)
At times you receive access denied errors which are annoying.
Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
We see the professional look it gives, and the live proof it provides. It helps with conversions, so we want to be sure we have the optimized numbers for our business. It is worth keeping so we earn more leads, and sales by piggybacking on the psychological effect of FOMO and more. We believe it is a must have in our arsenal, at least on selected pages.
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
The AWS documentation is well maintained and has lots of information which makes it easier for developers to refer to and develop applications in a fast efficient manner. It is well documented with examples which is easy to understand and implement. You can also get help by posting into forums from like-minded developers.
We had a question... We asked about a certain feature... One that was not present. So, what happened is that they responded quickly, but also, they developed the feature FOR US, which is unprecedented in many ways. It is not the norm, so we were taken great care of. The support was more than helpful and we would recommend them any day of the week.
The only thing to note, if you're afraid of tech, get the developer to install the code. You can do the design, but maybe get someone to install the code, again, it is done in minutes. Maybe 5. The other thing to note, keep an eye on your stats and analytics. You install this for a reason, to help with conversions. The only way to know for sure if it is right for your page(s) is to track it. If it does not aid your % it is of no use. Not EVERY page will be a candidate at all times. BUT, most are. So my advice is to go for it, get it set up. Track your before and after. If you an uplift in your % then keep it. If there is no visible change, maybe you're not tracking the right metrics over the right amount of time, so check if you can track deeper. If you have tracked really well, and not seeing an uplift, maybe change the wording, the widget, or the placement of it. And keep tracking. If there is no change short-term or long-term, then I would reflect on the usage. It is made to uplift conversions and it does so. But it is your job to place it where it matters, like on a lead magnet page, where others can see that they are not alone in both wanting and/or taking action and physically signing up to a lead magnet. So, again, my advice, get it set up. You will most likely do the job right on the first go, and from there, enjoy, and keep tracking
Amazon Simple Notification Service (SNS) is well integrated in AWS and has been there since the early days of public cloud. It is a cost effective and very inexpensive solution to meet the needs of event notifications and custom messaging. Wish to share that there is considerable number of developers who can easily build solutions using AWS SNS. So, training costs are minimal. Other solutions are emerging and we are seeing a great usage especially of Firebase notifications because of its very neat integration with open source cross platform hybrid app frameworks like ionic, xamarin. SNS needs to become better and should have plugin support for the mobile application developers using low code/no code tools too.
We have tested 3 other products in the past, all failed to have the complete solution we were looking for. Provely is here to stay and has added lots of features. 1 of the other tools we tested are low on features. 1 of the tools we tested had a short run and updates stopped and the project was abandoned. 1 of them never worked properly.
Cost of alert calls to the different stakeholders across different geographies have gone down since using Amazon SNS.
Amazon SNS has saved a lot of time for the employees that they used to spend to call multiple stakeholders so they can now focus more on productive tasks.
Amazon SNS usage needs prior knowledge of programming.
