This article will provide Feathr ID customers with step-by-step instructions for how to submit an implementation request.
Implementation Wizard walkthrough
In this video, our Support Engineer, Haadi Munshi, walks through the steps to submit a custom data request:
Start by logging into Feathr and navigating to the Data section on the lefthand side of the page, then clicking on Super Pixel, and finally Implementations.
At this point, you should see the following page:
This form is what we refer to as the Implementation 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. Name and Context
In a few words, describe the specific activity you are trying to track with this implementation request.
Some examples of activities that Feathr ID customers often track are event registrations and membership renewals.
Ex: "CookieCon 2022 - Event Registrations"
Ex: "Association of Cookie Distributors - Member Renewals"
Paste your GTM Container ID.
*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.
Provide a couple of sentences to state your goal for this implementation request.
The more context you can offer here, the better!
Paste the URL that marks the first step of the registration flow you are trying to track.
In some cases, the URL at this first step may remain the same throughout your entire registration flow.
If your registration flow requires payment in order to reach the Ending URL, please provide a 100% off promo code that Feathr engineers can use to bypass payment and test the implementation.
*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
What is this?
One of the major benefits of Feathr ID is the ability to not only track specific activities, like registrations and renewals, but also capture other data about your users as they complete these activities.
This step will determine which specific pieces of data you are trying to capture about your users as they proceed through a registration flow.
*Note: any custom 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 reg flow for that event must contain a field where the registrant can enter their occupation.
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, as highlighted in the screenshot below:
"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", as shown in this screenshot:
- Suppose we are trying to capture name, email, and occupation for registrants as they proceed through the reg flow for CookieCon 2022.
- 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."
With these thoughts in mind, here is what we would want our Field Capture section to look like for this example scenario:
You can also add any 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 custom data that Feathr ID customers often capture:
- Payment method used at checkout.
- Ticket type.
- User-submitted data from form field fills.
- User-selected data from dropdown menus.
4. Form Submit Capture
This step allows you to create a custom field within Feathr that refers to the activity being tracked by your implementation request.
This custom field can then be used to create an audience segment consisting only of users who have completed the tracked activity. Other Feathr campaigns that you run in the future can also take advantage of this segment. For example, a segment of confirmed registrants for CookieCon 2022 could be retargeted with highly tailored ads in the lead-up to CookieCon 2023.
*Please do not enter anything besides "REG_CONFIRM" in this field unless a different name has already been explicitly agreed upon by your organization and Feathr.
Form Submit Text
The name that you would like the activity being tracked to have within Feathr.
*Be sure to choose a name that is relevant to the activity being tracked. For example, if you are trying to track all membership renewals during the second half of 2022, a good name to use here might be, "2022H2Renewals."
- Once CookieCon 2022 has ended, we want to be able to retarget only the specific part of our audience that registered for the event with highly tailored ads.
- We also want to create a goal segment, for reporting purposes, where a completed registration is considered a conversion.
For this example scenario, here is what our Form Submit Capture section should look like:
5. Special 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.
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?
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!