GTM & GA4 Tracking Setup
Budget: $30 – $250 USD
Project Overview
We are looking for an experienced tracking and WordPress developer to improve the lead-generation tracking system on our site.
The website uses multi-step Elementor forms that send leads to Boberdoo through an existing API integration. TrustedForm is also currently connected and must continue working without interruption.
The developer will implement UTM tracking, form-step tracking, funnel abandonment reporting, Google Tag Manager events, GA4 events, Meta events, server-side tracking, data-layer improvements and spam protection.
All existing forms and integrations must remain operational.
Estimated Completion Time
The project should be completed within approximately 5 to 6 days.
Main Responsibilities
1. Create a Complete Website Backup
Before making any changes, create a restorable backup of:
Website files
WordPress database
Current form and tracking configurations
Work should initially be completed on a staging site, backup environment or another recoverable version of the website.
2. Implement UTM Tracking
Capture the following UTM parameters from landing-page URLs:
utm_source
utm_campaign
utm_medium
utm_content
The website uses dynamic Meta Ads tracking URLs similar to:
utm_source=meta-adsutm_campaign={{campaign.name}}utm_medium={{adset.name}}utm_content={{ad.name}}
The UTM values must:
Be captured when the visitor arrives
Remain available throughout the complete multi-step form
Be included in the lead submission sent to Boberdoo
Work with the existing Elementor and Boberdoo API integration
3. Track Different Form Sources
Each form location must include a source value identifying where the lead originated.
Required source values include:
WebsiteWP
POPUP
TOPBAR
BottomPage
Auto_Accident
These values must be sent with the lead so the original form source can be identified.
4. Track Every Step of the Multi-Step Forms
The website has several multi-step lead forms.
The Car Accident form currently has approximately 11 steps. Additional site-wide forms are used through the pop-up, top bar and bottom-of-page placements.
Create a separate tracking event for every form step, such as:
step1_event
step2_event
step3_event
Additional events for all remaining steps
The tracking must show where users abandon the form funnel, including the specific step at which they stopped.
The existing final lead event is already firing and should not be unnecessarily recreated.
5. Configure GTM, GA4 and Meta Events
Configure form-step and conversion events through:
Google Tag Manager web container
Google Tag Manager server-side container
Google Analytics 4
Meta Pixel and Meta Conversions API
Each form-step event must be passed correctly to GA4 and Meta.
Browser and server events must use the same event or lead ID so that Meta can properly deduplicate the events.
The existing final lead event must continue working.
6. Configure Customer Data Layers
For the existing PageView and Lead events in Google Tag Manager, configure functional data-layer values for:
First name
Last name
Email address
Phone number
City
State
ZIP or postal code
Country
The information must be passed correctly to Meta through the existing web and server-side tracking setup.
The implementation will be verified through Google Tag Manager and Meta event-testing tools.
7. Fire the Lead Event Only for Qualified Leads
Update the existing GTM Lead event so that it fires only when a lead is confirmed as qualified by Boberdoo.
This requirement applies to both:
Browser or web events
Server-side events
The developer must determine the appropriate method for receiving or identifying the qualified-lead status from Boberdoo.
8. Maintain Existing Elementor, Boberdoo and TrustedForm Integrations
All front-end and back-end work must use the existing Elementor forms.
Do not replace the Elementor form system unless written approval is provided.
The following must remain fully operational:
Existing Boberdoo API integration
Existing Elementor forms
ActiveProspect TrustedForm
TrustedForm certificate and lead data transmission
Existing final lead event
Boberdoo administrator access will not be provided. The developer must specify the minimum permissions required, and a limited user account may be created.
The applicable API file and field information will be provided.
9. Add Spam Protection Without CAPTCHA
Implement an anti-spam and anti-abuse system without CAPTCHA or another solution that adds unnecessary friction to the lead form.
Possible methods include:
Honeypot fields
Rate limiting
Duplicate-submission prevention
Session or IP throttling
Behavioral validation
Server-side validation
The solution must prevent repeated or abusive submissions while allowing legitimate users to complete the form normally.
10. Testing Requirements
Do not use real consumer information for testing.
Every test submission must use:
ZIP Code: 99950
TrustedForm must remain active during testing so the test data continues passing correctly to Boberdoo.
The developer must verify:
All UTM values are captured
UTMs remain available through every form step
UTMs are sent to Boberdoo
Source values are sent correctly
Form-step events fire correctly
GA4 receives the events
Meta receives browser and server events
Event deduplication works
Customer data layers are populated
Qualified-lead logic works
TrustedForm remains functional
Spam prevention works without blocking legitimate users
Required Deliverables
The completed project must include:
Complete website and database backup
Functional UTM capture and persistence
UTM transmission to Boberdoo
Source tracking for all listed form locations
Tracking events for every multi-step form page
Funnel abandonment reporting
GTM web and server-side event configuration
GA4 integration
Meta Pixel and Conversions API integration
Browser and server event deduplication
Customer data-layer implementation
Qualified-lead event logic
CAPTCHA-free spam prevention
Verification that Elementor, Boberdoo and TrustedForm remain operational
Documentation listing all events, triggers, variables, data layers and Boberdoo field mappings
Required Experience
Applicants should have proven experience with:
WordPress
Elementor forms
Google Tag Manager
Server-side Google Tag Manager
Google Analytics 4
Meta Pixel
Meta Conversions API
Event deduplication
JavaScript and WordPress development
UTM attribution
Multi-step form tracking
Data-layer implementation
API and webhook integrations
Boberdoo or similar lead-distribution platforms
ActiveProspect TrustedForm
Lead-generation spam prevention
Information to Include in Your Proposal
Please provide:
Examples of similar tracking or lead-generation projects
Experience with Elementor and Boberdoo integrations
Experience with GTM server-side tracking and Meta CAPI
Your proposed method for preserving UTMs throughout the form funnel
Your proposed method for identifying qualified Boberdoo leads
Your proposed CAPTCHA-free spam-prevention method
The access and permissions you will require
Confirmation that you can complete the project within 5 to 6 days
Your fixed-price quote
We are looking for an experienced tracking and WordPress developer to improve the lead-generation tracking system on our site.
The website uses multi-step Elementor forms that send leads to Boberdoo through an existing API integration. TrustedForm is also currently connected and must continue working without interruption.
The developer will implement UTM tracking, form-step tracking, funnel abandonment reporting, Google Tag Manager events, GA4 events, Meta events, server-side tracking, data-layer improvements and spam protection.
All existing forms and integrations must remain operational.
Estimated Completion Time
The project should be completed within approximately 5 to 6 days.
Main Responsibilities
1. Create a Complete Website Backup
Before making any changes, create a restorable backup of:
Website files
WordPress database
Current form and tracking configurations
Work should initially be completed on a staging site, backup environment or another recoverable version of the website.
2. Implement UTM Tracking
Capture the following UTM parameters from landing-page URLs:
utm_source
utm_campaign
utm_medium
utm_content
The website uses dynamic Meta Ads tracking URLs similar to:
utm_source=meta-adsutm_campaign={{campaign.name}}utm_medium={{adset.name}}utm_content={{ad.name}}
The UTM values must:
Be captured when the visitor arrives
Remain available throughout the complete multi-step form
Be included in the lead submission sent to Boberdoo
Work with the existing Elementor and Boberdoo API integration
3. Track Different Form Sources
Each form location must include a source value identifying where the lead originated.
Required source values include:
WebsiteWP
POPUP
TOPBAR
BottomPage
Auto_Accident
These values must be sent with the lead so the original form source can be identified.
4. Track Every Step of the Multi-Step Forms
The website has several multi-step lead forms.
The Car Accident form currently has approximately 11 steps. Additional site-wide forms are used through the pop-up, top bar and bottom-of-page placements.
Create a separate tracking event for every form step, such as:
step1_event
step2_event
step3_event
Additional events for all remaining steps
The tracking must show where users abandon the form funnel, including the specific step at which they stopped.
The existing final lead event is already firing and should not be unnecessarily recreated.
5. Configure GTM, GA4 and Meta Events
Configure form-step and conversion events through:
Google Tag Manager web container
Google Tag Manager server-side container
Google Analytics 4
Meta Pixel and Meta Conversions API
Each form-step event must be passed correctly to GA4 and Meta.
Browser and server events must use the same event or lead ID so that Meta can properly deduplicate the events.
The existing final lead event must continue working.
6. Configure Customer Data Layers
For the existing PageView and Lead events in Google Tag Manager, configure functional data-layer values for:
First name
Last name
Email address
Phone number
City
State
ZIP or postal code
Country
The information must be passed correctly to Meta through the existing web and server-side tracking setup.
The implementation will be verified through Google Tag Manager and Meta event-testing tools.
7. Fire the Lead Event Only for Qualified Leads
Update the existing GTM Lead event so that it fires only when a lead is confirmed as qualified by Boberdoo.
This requirement applies to both:
Browser or web events
Server-side events
The developer must determine the appropriate method for receiving or identifying the qualified-lead status from Boberdoo.
8. Maintain Existing Elementor, Boberdoo and TrustedForm Integrations
All front-end and back-end work must use the existing Elementor forms.
Do not replace the Elementor form system unless written approval is provided.
The following must remain fully operational:
Existing Boberdoo API integration
Existing Elementor forms
ActiveProspect TrustedForm
TrustedForm certificate and lead data transmission
Existing final lead event
Boberdoo administrator access will not be provided. The developer must specify the minimum permissions required, and a limited user account may be created.
The applicable API file and field information will be provided.
9. Add Spam Protection Without CAPTCHA
Implement an anti-spam and anti-abuse system without CAPTCHA or another solution that adds unnecessary friction to the lead form.
Possible methods include:
Honeypot fields
Rate limiting
Duplicate-submission prevention
Session or IP throttling
Behavioral validation
Server-side validation
The solution must prevent repeated or abusive submissions while allowing legitimate users to complete the form normally.
10. Testing Requirements
Do not use real consumer information for testing.
Every test submission must use:
ZIP Code: 99950
TrustedForm must remain active during testing so the test data continues passing correctly to Boberdoo.
The developer must verify:
All UTM values are captured
UTMs remain available through every form step
UTMs are sent to Boberdoo
Source values are sent correctly
Form-step events fire correctly
GA4 receives the events
Meta receives browser and server events
Event deduplication works
Customer data layers are populated
Qualified-lead logic works
TrustedForm remains functional
Spam prevention works without blocking legitimate users
Required Deliverables
The completed project must include:
Complete website and database backup
Functional UTM capture and persistence
UTM transmission to Boberdoo
Source tracking for all listed form locations
Tracking events for every multi-step form page
Funnel abandonment reporting
GTM web and server-side event configuration
GA4 integration
Meta Pixel and Conversions API integration
Browser and server event deduplication
Customer data-layer implementation
Qualified-lead event logic
CAPTCHA-free spam prevention
Verification that Elementor, Boberdoo and TrustedForm remain operational
Documentation listing all events, triggers, variables, data layers and Boberdoo field mappings
Required Experience
Applicants should have proven experience with:
WordPress
Elementor forms
Google Tag Manager
Server-side Google Tag Manager
Google Analytics 4
Meta Pixel
Meta Conversions API
Event deduplication
JavaScript and WordPress development
UTM attribution
Multi-step form tracking
Data-layer implementation
API and webhook integrations
Boberdoo or similar lead-distribution platforms
ActiveProspect TrustedForm
Lead-generation spam prevention
Information to Include in Your Proposal
Please provide:
Examples of similar tracking or lead-generation projects
Experience with Elementor and Boberdoo integrations
Experience with GTM server-side tracking and Meta CAPI
Your proposed method for preserving UTMs throughout the form funnel
Your proposed method for identifying qualified Boberdoo leads
Your proposed CAPTCHA-free spam-prevention method
The access and permissions you will require
Confirmation that you can complete the project within 5 to 6 days
Your fixed-price quote