Full transcript
0:00What is going on, guys? In this video,
0:01we're going to go over exactly how I am
0:04streaming any social engagement that I'm
0:06getting into my CRM and creating two
0:09custom objects to link them together.
0:11These custom objects are any social post
0:14that I do. And then the second object is
0:16any person that reacts with that post
0:19gets added there automatically, which
0:21means I can just prospect out of my CRM
0:23at a speed that's never been done
0:25before, which is awesome. And it also
0:28means I can run agents over the top of
0:29this data should I wish. So let's dive
0:32in and have a look at how I'm doing
0:33this. To get started with, we're using
0:36three tools. These tools being Triggery,
0:38yours truly, which is going to help us
0:40track anything related to social media.
0:44The second is Atio and that's the CRM
0:46that I'm using and one that I truly
0:48think is the best in the market right
0:49now and the one that we use generally.
0:51And the third one is NA10 to power the
0:54workflow behind uh linking all of these
0:56systems together.
0:58So let's have a look at it. So as you
1:01can see with ATIO they're very very good
1:04for objects and creating custom objects.
1:07So you know companies people but in this
1:09case they have two custom objects. These
1:11objects being LinkedIn engagement. So
1:13that is anyone who has liked and
1:14commented on my post and then LinkedIn
1:16posts. And that's what we're on now. And
1:18this is basically just um any uh any
1:23post that I've done essentially. So you
1:26can then actually start to see which is
1:28quite cool um all of the posts that I'm
1:32doing. And you can actually then start
1:34to see all of the LinkedIn uh engagement
1:37that I'm getting from this. So, if I go
1:39over to the LinkedIn engagement, here
1:41are all the people that are engaging
1:42with those posts and I can track them
1:44back to the specific post, which means I
1:46could reach out to them based on the
1:48post that they're doing or just have
1:50that stored in my CRM should I wish to
1:52to do that. Um, but what's really really
1:55exciting about this is
1:58you also because we're actually storing
2:00this information, we can then start to
2:02understand have has this person what is
2:05the customer life cycle? Have they gone
2:08on to book a demo? Have they gone on to
2:10speak to sales? What has happened? And
2:13that basically means we can create
2:14what's called revenue attribution all
2:17the way down to the super super minute
2:19granularity detail here, which is okay.
2:22Hey, Joe Blogs liked X post three months
2:25ago, then they signed up to a
2:27newsletter, then they booked a demo. So
2:30in olden times, most of the marketing
2:32would attribute that as maybe newsletter
2:34or something else. They could say
2:36social, but they wouldn't know where.
2:38Now, we can actually get down to that
2:39granular level, which is epic. So, how
2:44are we doing this? Well, first of all, I
2:46went and created two new objects inside
2:48of Atio. Super simple. Just create the
2:50objects. Then, what you need to think
2:52about is creating the uh attributes
2:55themselves. So in this case I added
2:58LinkedIn post post URL likes comments
3:01posted at and then I created a
3:04relationship
3:06uh attribute. So this is basically
3:08saying it's going to be a one to many
3:11and what that basically means is if we
3:13look at the engagements here you can see
3:17um that there are multiple people
3:20engaging with uh this content. Okay. And
3:24this is uh one field or one post to many
3:28different other kind of attributes. And
3:30that's effectively what we've done
3:32there, which basically means we've
3:33joined these engages to this particular
3:36post, which is really cool. So then when
3:38you go look at the LinkedIn engagement,
3:40we can then map it back in the opposite
3:42direction as well, should we wish to do
3:44that. Um the other cool thing that we've
3:46done here is we can also see the
3:47comments uh that they have coming in as
3:49well. So very handy to run workflows
3:52around this or whatever and just to have
3:55this stored in. You can start tracking
3:57exactly what these people are doing, how
3:59they're working, so on and so on. So how
4:03did we get data into here in the first
4:05place? Well, we started with uh
4:07triggery.
4:09Quite simply, we came over to triggery.
4:11Basically, we entered in the company and
4:14uh personal URL of myself. So it's here.
4:18And then what we started to do is we
4:19started to send this data um through via
4:24web hook into ATIO through using NA10.
4:28Now there's a few kind of key things
4:30that we need to think about with this is
4:33first of all we needed to go ahead and
4:36create the LinkedIn post because that's
4:39like stems is the initial kind of root
4:42part of this flow or this data point and
4:45then we attach the engagement onto that
4:47and so triggery basically sends through
4:50the uh engagement like one by one. So if
4:54we look at the people associated that
4:55are engaging with my content, every time
4:58someone new likes my content, it's then
5:01going to send this through via a web
5:04hook through to here one by one. So what
5:08that means if like let's say like uh
5:10Yseph here, it's going to send through
5:12the post they engaged with which is this
5:14post um and obviously all the details
5:17along with that and then it's going to
5:18send you know Mike Ball again for
5:20example. was going to send that through
5:21to here, but it will send the post
5:23information. So, I don't want to create
5:25a new post every time. So, what I did to
5:29stop that from happening is um I
5:33basically made the post URL a unique
5:36attribute. So, it can't duplicate it and
5:38in fact it will error if it tries to
5:40duplicate it. And so, what we do here is
5:43first step of this process is we take
5:46the data in which triggers the workflow.
5:48We're then checking inside of Atio if
5:51this post URL that's getting sent from
5:53this web web uh hook is inside of Atio.
5:58If there is no data that gets returned,
6:01it means um it means that it's not
6:04inside of Atio, which means it goes this
6:06way where we then create the social post
6:08which is creating this part and then we
6:12then basically go on to add the
6:14engagement which we would have got from
6:15the original web hook as well. If the
6:18social post is already in because we
6:20obviously would have had 10 people
6:22uh you know or more 30 40 how many
6:25people like or comment on my post it
6:27then goes down this route because it
6:28would return back okay yeah there is a
6:30post and it would then add them into
6:32here but the same thing that we've done
6:34over here is if I go back to my objects
6:38looking engagement and then do that I've
6:41made that unique as well. That means if
6:44someone is liking multiple posts across
6:47you across different posts, it won't
6:48create them every time. So it's going to
6:49create them once and the only time which
6:53is why if we look at the execution logs,
6:56it occasionally errors, which basically
6:57says, okay, hey, someone's already liked
6:59this stuff and it's just kind of
7:00repeating that um process as well, which
7:02is really really cool. And that is how
7:05we're then basically getting all of the
7:09social activity streaming in. What's
7:12really cool because the way that Atio
7:13works is I'm not convoluting it with you
7:17know sales data which is like within
7:19companies and people these are separate
7:22objects which means I could create like
7:26a I could join it in some shape or form
7:28or I can keep them separate and
7:31effectively almost have like two CRM
7:33inside of one CRM which is uh which is
7:36amazing. So that is the the whole
7:38process start to finish of how I'm
7:40basically creating this connection
7:41between social data revenue attribution
7:44because I can boil it down to see the
7:46the the lead stage of these people um
7:49and uh start creating this kind of
7:51report between atio triggery and nat
7:55very