To set up field mapping on a data pixel:
Go to control settings, integrations, and pixels on your website
Create a data pixel and add it to your website using the bed script
Go to the pixel integration and click on field mapping
Go to the external website and inspect the element of the form field by clicking on it and selecting "inspect"
Copy the name attribute, which is typically located in the brackets or between the quotation marks
If there are brackets, only copy the information inside the brackets
Paste the name attribute into the field mapping section of your data pixel
Map the field name to the global field in your system
Repeat this process for all the fields that you want to map
If you are not comfortable with inspecting elements or mapping fields, you can use the embedded data forms instead.
Video Transcript:
Okay, so now mentioned in the previous video, that you can actually pull data from forms that are currently on your own website, and if you watch through that data form video, you realize that there's a mapping component to ensure that that data mapped to our global fields. So you need to do that with your pistol as well.
If you plan on using data pixels and not using our data form system, you can map your data fields to your forms that are on your website and you can do that in your pixel section. So if you come over here under control settings, integrations and go to pixels, you'll see I have that pixel is set up in earlier videos. This pixel I'm using for my tracking and I'm also using an external data form on my website to track leads that come in through the external data form.
However, you may have an external website that already has data forms or lead forms and you don't want to go through creating your data forms and embedding those. You just want to put a pick on and let data scrape. So to do that once you create your data pixel you have this bed script right here so you can grab this in bed script and put the whole thing on your website at the open close of the body or in the head. Or you know either one is fine, then you can go in by clicking this edition.
So when you come into it now, you have the option of setting up field mapping. So the way field mapping works, and let me go out to an external website. So this external website. This is not our form, that is not our data form. So there is a data form built-in element or some other within were pressed and to get this data into our system. What we're doing is we're listening for someone to submit this form. However, first name, last name, work, email company are similar to ours and they do. But there may be the name of this field, even though you see it as first name, the name of the form field. Maybe something were like and or maybe you know name or something like that, to where we can't map it.
So when you set up a data pistol and you want a map, data from pulling from a data form like this, you need to map the actual fields to your data form and to do that real simple is you're goin to write, click on the form field and do inspect. So when you do inspect the element and automatically highlight the code, if you're not an advanced user, don't freak out or if you've never seen, you know, this may be a little bit more difficult. You may want to use imbed data forms that we have, but for the pixel to scrape data, you know, and again, it can scrape data without needing to do the mapping.
So I think you would want to map your data fields or your data pico if, once you put it on your side and it's not mapping the data over, because you may have just a simple form that's very easy to understand. When you submit where it's easy for us to understand what the data is that's coming to us and we can, we can pull it. However, in this case this one's unique. This one has almost like a well it is. It's an array of data that's sent over, even though it has first name, it's in an array with first name right. It's also first underscore name, so it's it's you know, it's just this may not map properly out-of-the-box so to ensure that old map we have data pixel mapping.
And so once you go into your pixel integration you have these data fields that you can add for field mapping. And so what I'll do is I'm going to hit a field mapping. You're looking for the field name and the global field that we want a map to in our system. So in this case first name you're looking for the name attribute. So this is already highlighted. You're looking for name. So here's name equal and then you see how it says modic form and then there's brackets and first name, underscore name.
If there is these brackets right, so open bracket, close bracket. You only want what's inside the bracket. Most cases you won't have a bracket. So you'll just copy whatever's in here. But if you see brackets only grab what's in between the brackets. So in this case there's brackets. So I'm going to grab that. I'm going to place that there and then I'm going to map that first name and I'm gong next, going to grab the last name and copy over last name here, words in brackets. And I'm going to come over here to add field mapping but that his last name then work email, scrap work, email and add field and then to email.
Now i'm going to grab company just again. If there's no brackets, copy everything in between the quotation marks. If there is brackets only what's in between the brackets, that company phone number. So what we do for all this other data here we actually will. That comes into the system as well, but it just doesn't map to our global fields, phone number. And let's try pretty much so now, when someone fills out this form and submit, what this is doing is passing all that data over and instead of its not being able to see it, because it's all in this. You know this funky array that we have to look through. We're able to see it and map because we know when we get that attribute, the name attribute with first name just like that.
We know to push it right into the lead system with first names. So really simple if you, you know, if you've never done inspect element and you know you freek out if you see any type of code at all, you know, install the pistol. Most of the time it's going to pull the data regardless without any help. This is just for additional help for any forms that you may have that may have ideas for names, may have. You know, like this one has an array for name with brackets. It may have just a weird alternative name for the actual field name that you know we wouldn't be able to find out what that field is. You know what they're submitting to the map to our system if we didn't need a little help.
So think of this is just a little added help. If your pistol doesn't work and data is not coming across and you're not capable of going through here and and really just finding out the attribute name and mapping it, then you're better off using our embedded data forms, which you know work very similar to any other form system that's out there.
