We now have a fancy front end form to create a new survey.
And we have a back and post request route handler to accept that survey and send it out to the outside
world.
So we've got a huge part of our application now finished.
It's time to start thinking about closing it up and wrapping up with some of the additional remaining
features.
So we really have to last big things to take care of.
First off we need to make sure that we show a list of all the different surveys that have been created
on our dashboard.
And then we also have to make sure that whenever a user clicks on one of the links inside of an e-mail
we record either a positive yes feedback or a no negative feedback for this very particular survey.
And so this is what we're going to be taking care of right now.
We're going to make sure that whenever a user clicks on one of these links inside of these e-mails we
record some amount of feedback to the appropriate survey.
Now we spoke very briefly some time ago in the past when we were putting together our back and route
handler to create a new survey about exactly how we would receive feedback from the email.
Remember we had said that we would enable click tracking side of our emails.
We did that inside of our mailer that tells send grid to automatically replace every single anchor tag
inside of our e-mail with a custom link when it does that and someone clicks on a link Saenger then
knows exactly who clicked on the link and which clip link they clicked on either the yes or no link
inside the e-mail.
And so we had said that at some point in time Sandri would send us a message telling us hey here's some
details about a click that just occurred inside of one of your e-mails.
And so it can be up to our API server to process that notification from Send grid and we can record
it somewhere inside of our Mongo database.
So this process right here receiving this feedback can send grid is what I want now.
Dive into a lot greater detail on because setting up this relationship is going to be just a little
bit challenging.
Now this relationship having said grid send an automated message to our back end server.
Remember that we refer to this as a web hook.
So I Web hook is any time that one server makes some communication to another server because of some
event that occurred on the first one we're going to learn a little bit about how web hooks work and
in particular about how they differ between the production and development environments.
So let's dive into that in the next section so I'll see you in just a minute.