Pixel Tracker integration

Feature Snapshot

Summary:
Pixel Tracker integration is a LeadConduit recipient step that fires a small web beacon—commonly known as a tracking pixel—to external third‑party services (such as Google Analytics and HasOffers) to record conversions and track user events in real time.

Key Benefits:

• Enables real‑time tracking of lead events without complex coding
• Integrates seamlessly with popular analytics and marketing platforms
• Requires minimal configuration within your LeadConduit flow
• Provides immediate insights into campaign performance and conversion tracking

Typical Use Cases:

• Tracking conversion events in Google Analytics by transmitting lead‑specific data
• Integrating with services like HasOffers to measure marketing campaign performance
• Monitoring user interactions and conversions across multiple channels without extensive development work

How the Pixel Tracker Integration works?

The Pixel Tracker integration functions by inserting a recipient step into your LeadConduit flow that calls a designated web beacon URL. When a lead reaches this step, LeadConduit maps the necessary parameters—such as the tracking version, tracking ID, a unique lead identifier, and event type—onto the beacon URL. As a result, the integration fires a tracking pixel to the external service with all mapped data, enabling real‑time event tracking and conversion measurement.

Step‑by‑Step Instructions

1. Open Your Flow Editor:
   Log into LeadConduit and navigate to your flow’s Steps list.

2. Add the Pixel Tracker Step:
   Click “Add to Flow > Integration” and select the “Pixel Tracker” integration from the available options.

3. Edit Field Mappings:
   Click on the Pixel Tracker step, then click the “Edit Field Mappings” button.

4. Configure the Base URL:
   In the Field Mappings editor, paste the web beacon’s base URL. For example, use: http://www.google-analytics.com/collect

5. Map the Required Parameters:
   Add mappings for the key name‑value pairs as follows:

   • v: Set to “1”
   • tid: Enter your Google Analytics Tracking ID (e.g., UA-XXXXXXX-YY)
   • cid: Map this to the LeadConduit Lead ID (e.g., using {Lead.ID})
   • t: Set to “event”

6. Save and Activate the Flow:
   Click “Confirm” to close the Field Mappings dialog and then save your flow.

Validation & Monitoring (optional)

• Test the Setup:
  Submit a test lead through your flow and verify that the Pixel Tracker step fires correctly. Check that the constructed URL includes all the required parameters and that your external service (e.g., Google Analytics) logs the corresponding event.

• Where to Monitor?:
  Review the LeadConduit event log to confirm the execution of the Pixel Tracker step. Additionally, verify the recorded event details in your external tracking service’s dashboard.

Best Practices

• Double‑check that you have entered the correct base URL and that it is accessible without redirection issues.
• Ensure that the parameters, especially the dynamic Lead ID for “cid,” are mapped accurately to guarantee unique and traceable tracking hits.
• Test the integration across different lead scenarios to make sure all dynamic parameters transmit correctly.
• Use URL‑encoding where necessary if parameter values contain special characters to ensure the external service properly interprets the data.

Troubleshooting

Frequently Asked Questions (FAQ)

What is the Pixel Tracker integration?

It is a LeadConduit recipient step that fires a web beacon (tracking pixel) to external third‑party services in order to track conversions and user events in real time.

Why is the Pixel Tracker integration important?

It provides real‑time tracking and immediate insight into lead behavior without requiring complex coding changes, thereby enhancing campaign performance analysis and conversion measurement.

How do I use the Pixel Tracker integration?

You add the Pixel Tracker step into your LeadConduit flow, configure it by editing field mappings to set the base URL and required parameters (v, tid, cid, t), and then activate your flow. Each lead passing through this step will trigger a web beacon call that is captured by your external service.

Do I need programming skills to set this up?

No, the Pixel Tracker integration is designed for ease of use through LeadConduit’s intuitive point‑and‑click interface, so no programming skills are necessary.

Can I integrate the Pixel Tracker with any external service?

Yes, as long as the external service accepts HTTP GET calls with URL parameters, you can use the Pixel Tracker integration to send tracking data.

Glossary