Alright, so now that we've got over the concept of what a conversion is, we now need to feed the data to the conversion through what we call a conversion source. So, for context, I'm going to go ahead and edit this lead. You can either do that by clicking the lead button or by clicking this configure conversion button and then coming in and adding a new source. I already have one added, but again to add one, we're going to select webhook from here and then I always recommend like a GHL - Form Submitted type thing. So we always do in the source name, so like HighLevel, Typeform, you know, wherever it's coming from, and then the action that triggered the webhook.

So I already have one set up. Once you set it up, you're going to see this "Setup Webhook" button, where when you click on it, it's now going to give you a URL and start listening for events. So we can then take this URL, go to any sort of automation builder or honestly even platforms like Stripe and Typeform and subscribe directly to certain events. In this example, we are going to do an automation. I'm going to use HighLevel for the automation, but again it works the same across Make.com, n8n, wherever an automation can send a webhook or any platform that can send a webhook, we can pick it up.

So again, we are then going to come in here, add a webhook, paste that URL from this other page. Right, this page here, we're going to copy this webhook URL, then we're going to come in here, we're going to paste it, and then hit save action and hit save. I'm then going to come back and I am going to add some details and fill out this form... and then I'm going to go ahead and hit submit.

If I then check HighLevel, you'll see that I just did that now, 2:02 AM, added to workflow, and then the webhook should have triggered. And then if I come back here, you'll now see that we picked it up, right? Boom, the webhook hit our system and we now picked it up.

So in here is where you're going to go ahead and dial in the different fields for our system to track based off of the webhook data that you got. Now as you see, GoHighLevel sends a lot of data. It can be very ugly and confusing. That's why we have a nice little search button up here so we can search for things like name, and you'll see full_name. Perfect, that's me there. And then if we go and search for email, we're going to go test email here. Then if we search for phone, you're going to see the phone number that I added in there.

Again, very important, if you see here, we use the email to track the lead's page view history and link their activity to the conversion, right? So we can track the user's page views and the contact by using email and/or phone number. If you only have one, we can use one or the other, but adding both always allows you to track, get the contacts with more data, meaning you'll have a higher match rate as well. Add a full name if you want to track the name.

Then we can go ahead and we can add some revenue. So if this is like a purchase event, then we can add some revenue. This was not a purchase event, but let's say that there was data in here, we can add the revenue. Again, this works also from Stripe, so if you want to use a Stripe payment or a Stripe subscription creation or anything like that, you can go ahead and do that as well. And then choose a currency for the actual conversion. So let's just say this is going to be US dollar. Cool. So now I have the tracking fields, which again is essential for tracking conversions.

Then I can go down to the attribution. We have an entire training video up above, it is called "Attribution Tracking Through Webhooks," so I'm not going to restate all of that in here, but the concept is simple. You are then going to just map your attribution. So if you have like a campaign, nothing came in here... medium... you know, maybe it was a form so it didn't come, there's no ad tracking, but if you do have the ad tracking and you can get the ad tracking data from your webhook, then you can go ahead and pass it here. If you guys really want to dive deep into that again, please go check out the other video which is "Webhook Attribution Tracking."

From there, guys, we can also add contact fields. So if you see inside of contact fields, we will have the standard fields, so it's like the company name, address, city, state, country, time zone. And this is going to be beneficial because our system is also a CRM and we also have AI sales agents, so you can pass this data through to an AI sales agent. If you have custom fields, you see we don't have any here, we can add a custom field that says, you know, "source.medium," create the field, and then we can populate the data in here.

So if, guys, just the real-world use case for this would be, let's say you have a form and you are running lead ads for a realtor, and the realtor is looking for homebuyers. And you know, they ask on the form, 'what type of home are you looking to buy?' right? Like how many bedrooms, how many bathrooms, etc. So you have all that data in a form submission. You could then pass the data through to the custom field, save it, so every time this trigger or this webhook triggers, we'll save that data, and then you can pass this data through to the AI sales agent so the AI sales agent can create hyper-personalized follow-ups and hyper-personalized communication. You can also just map it if you want to save the data in the CRM, that is obviously also a thing, but the more practical use case for saving contact fields is again going to be to send this data through to an AI agent.

Now, once we're happy with our form mapping, we can then come, we can hit "Save Mappings," and then you will see that that has been saved. The status is on. You can always turn the status off if you no longer want to track this source or leave it on. And you can also see all of the requests. Important to mention is you can always click on this and you can actually see the conversions. So we have this one here, we can see the data, right? It was from this... this was the... right, this was me, so like all the GoHighLevel webhook data that was sent is going to be in here and we can track this data.

And then also, we can delete data from in here, we can remap. So if there's another type of webhook that comes and you want to change the mapping, you can do that in there as well. And all of that can be done. You can check any sort of failed, it'll tell you what the failed reason was, and any sort of successful too. So if you guys are ever curious and you're like, 'hey, are we tracking, are we missing, you know, conversions?' that is why we show this to you guys because we want you to be able to track the time when it occurred, the user's name, and all these different things.

And if I show you on another account that has a bit more data, guys, you'll see here, you know, 489 successful. You can then click, you can see the timestamp, the contact, right, where they came from. You can again view the data, you can delete the data, and then this way you guys can track for certain who these contacts were, what conversions, when did they happen, and it gives you full insights into absolutely everything. And then you can always remap the fields as well if, you know, you want to update the field mapping or if something changed or whatever it may be, you can always update the field mapping again from in here.

And then one last thing to mention is you can also configure the webhook from here, which will show you literally the same data again, right? The webhook name, the webhook URL, right? We can show you the analytics, which is literally what we just showed you before. So the successes, you know, the tests, and then you can also see the fields that you already mapped. So we mapped email, phone, full_name on this one. If I go back here, you guys can see the one that we just did, right? I did email, phone, full_name, order LTV was revenue, and then attribution source medium was on this custom field here.

So all of that is the conversion source and adding a webhook as a conversion source. Once you do this, you have it set up properly and mapped and you turn it on, then every time this webhook triggers—so for example, every time this automation fires off and it sends data to the webhook—our system is going to count it and then inside of your attribution table...

Just so I can show you guys the lead. So again, I... we had set up the conversion setup for the lead. I went and I triggered it again, and I used the same contact. So if you guys watched the page views, you would have known that at 12:44, I went and I did a page view at testingthings.com, and I added my email, name, and phone number, and it tracked my page view. Then, when I just submitted my conversion data, you'll see I did it at 2:18 AM, so we had a major difference of a few hours, which is how long it took between training videos, and now it's still showing it under the same source. Now, why it's doing that, again, is because it's matching the email that we sent. So it was the same email that we got in the webhook, and because it was the same email, we were able to see, ah, this contact actually clicked on this page view, or this website, and he had the source 'this,' medium was 'amazing,' and the campaign was 'cool.' So again, if I filter out this source, go to campaigns, you'll see 'cool,' right, that one page view and that one lead. If I go to medium, it'll show 'amazing,' right, the one page view and the one lead, and it is still me two hours apart. So I wanted to come back and record this to show you guys how that attribution works. Again, once we can track the actual user inside of the page views by contact, email, and phone number, then when we get a conversion, we match the email and the phone number to see if we can find the contact. If we can find the contact which is [email protected] from the page view and the lead, then we'll show you the exact same attribution, which as you see was 'testingthings,' 'cool,' 'amazing,' and we didn't add an ad. So I wanted to come back and record this to show you guys how that works once you actually start tracking your conversions.