This article provides Data Services customers with step-by-step instructions for how to submit an implementation request and enhance tracking on any webpage where the Super Pixel is placed.
These requests are typically used to track form submissions as conversion activities, and to capture data from the forms themselves. Reach out to your Customer Success Manager for information about adding a Data Service package to your Feathr license if this form is not available in your account.
Start by logging into Feathr and navigating to the Community section on the lefthand side of the page, then clicking on Super Pixel, and finally Implementations.
To create a new implementation request, select + Add Data Request in the top right of the Implementations page. That will bring you to the Data Request wizard.
There are a total of six steps to fill out this wizard, all of which are labeled on the left side of the form. Detailed instructions and screenshots for completing each step can be found below.
1. Context
Description
In a few words, describe the specific activity you are trying to track with this implementation request. Some examples of activities that customers often track are event registrations and membership renewals. This is helpful information for our implementation engineers.
Ex: "CookieCon 2024 - Event Registrations"
Ex: "Association of Cookie Distributors - Member Renewals"
GTM Container
Paste your GTM Container ID, the seven-character alphanumeric string after GTM. If you need help locating your Container ID, or you have not yet created a GTM container and installed it on your website, please see this article.
*IMPORTANT*: before continuing, please make sure that implementation@feathrapp.com has been granted publishing rights for your GTM container.
GTM Account ID
This step is optional, but this helps Feathr's Implementation Engineers complete data requests.
Learn how to find your GTM Account ID in this article.
Context
Provide a couple of sentences to state your goal for this implementation request.
Remember that one of our implementation engineers will read this. The more context you can offer here, the better. It will inform the final result of your request. Consider it a plain-language message to Feathr about what you're hoping to accomplish with this data request.
2. Locations
Starting URL
Paste the URL that marks the first step of the registration flow or form submission you wish to track. This helps our implementation engineers see the form in the context of your website or platform.
Feathr engineers will then test the workflow themselves to best determine how to track the data you are requesting. Since every request is different, Feathr engineers will be manually testing and re-testing it.
Promo Code
If your registration flow requires payment in order to reach the end or submit the form, please provide a 100% off promo code that Feathr engineers can use to bypass payment and test the implementation. It is essential that Feathr engineers be able to test their code without having to pay a fee on your form.
Note: If using a promo code causes the URL to change at the checkout page, please mention this in step 5, the "Instructions" section of your request.
3. Field Capture
One of the major benefits of data implementation is the ability to not only track specific activities, like registrations and other form submissions, but also capture other data about your users as they complete these activities and submit information. This data can be used for targeting and conversion tracking in your Feathr account.
This step will determine which specific data you wish to capture about your users as they proceed through a registration flow.
*Note: any data that you would like to capture must be submittable by that user as they proceed through your registration flow. For example, if you are trying to capture a user's occupation as they complete an event registration, the form for that event must contain a field where the registrant can enter their occupation.
Default fields
Upon arriving at this step, you will see that Feathr automatically lists four default fields for data capture: Name, Email, Companies, and Occupation.
You do not have to track any of these four default fields if you do not wish to do so. If this is the case, please click the "Trash Can" icon next to the corresponding field.
"Form Field" refers to the name of the field, as it is labeled in your reg flow, from which you are trying to capture data.
"Feathr Field" refers to the name that you would like the captured data to have within Feathr.
Both of these fields can be edited by clicking the "Arrow" icon to the left of "Feathr Field."
Example scenario:
- Suppose we are trying to capture name, email, and occupation for registrants as they proceed through the reg flow for CookieCon 2024.
- We know that it is possible to capture this data because anyone who registers for the event must enter these pieces of information into corresponding fields as they progress through the reg flow.
- However, within our reg flow, we notice that the field where registrants will enter their "Occupation" is actually labeled as "Job Title." Within Feathr, we would like for this data to also be labeled as "Job Title."
If your license includes Custom Data, you can also add additional custom data fields you would like to capture by clicking the blue "Add Data" button at the bottom of the form.
Here are a few examples of common custom data fields:
- Membership level
- Ticket type
- User-submitted data from form field fills
- User-selected data from dropdown menus
4. Conversion Capture
In addition to capturing data through specific fields, Conversion Pixels can be used to track activities like purchases from a shopping cart containing multiple items.
If you have a conversion pixel already created, select it from the dropdown menu under Conversion pixel. If not, choose Create group in the dropdown, and name your new conversion pixel in the next field.
Learn more about conversion pixels in this article.
The field Conversion category is for more specific information. In the example above, the newly created conversion pixel is labeled "Donations" and the conversion category is labeled "Fall Donation Drive."
5. Instructions
This section is where you can provide any additional information that may be useful to Feathr engineers as they write the custom code for your implementation request.
If you're not sure whether something is relevant or not, mention it anyway. Too much information in this section is far better than too little. Feathr wants to know what you wish to accomplish with your request and make it happen for you.
Here are a handful of things to consider mentioning:
- Are you using a third-party registration vendor for this reg flow? If so, who is it?
- Does the promo code you submitted in the "Locations" section cause the URL to change at checkout?
- Is there something you submitted in the Field Capture section that you are unsure whether or not we can track?
- Have you or your third-party reg vendor had any notable past experiences with GTM installation?
- Who is the best point-of-contact in your organization for Feathr engineers to reach out to if any questions arise regarding your request?
- Do you have any general questions about your implementation request that require clarification?
6. Review
Take a moment to review the details of your implementation request.
If you need some time to gather more information before submitting, you can click the "Save as Draft" button at the top left of the wizard, and come back to it when you are ready.
If you are good to go, click the green "Submit" button to send the request straight to Feathr's engineers. You're all set!
7. What Happens Next?
When the data request is complete, you will receive an email confirming the request and providing an time estimate for the completion of the request. Implementation requests average about one week of time required to complete. Within that time, a Feathr engineer may email you to request more information, so please watch your email.
When the request is complete, you will receive another email from an implementation engineer confirming the completion. That email will contain the information you need to begin using your newly capturable data, including a list of fields that are being captured, which email was used to test the flow, and any conversion pixels that were created for the implementation request.
Once the data is being captured and any conversion pixels that needed to be created are active, you will be able to use them as intended to track conversions.