Skip to content

Track Facebook Ads in Eloqua: Capture Campaign Data on Every Lead

You can see how many visitors an ad sent to your site, yet still not know how many became leads or customers. Capturing the ad parameters on the form itself closes that gap, so each Eloqua contact carries the campaign, ad set and ad that brought them in.

Why visits are not enough

Website analytics can count arrivals from an ad, but it cannot follow a person through a later offline sale. If the only record of the ad lives in the web session, the lead created in Eloqua has no link to the campaign that produced it.

The fix is to move attribution onto the lead record at the moment of conversion. When a visitor submits a form, the hidden attribution fields travel with the name, email and phone into Eloqua. Reporting can then count leads and customers by the campaign, ad set and ad that originated them, rather than by visits alone.

Setup checklist

Work through these checks in order:

  • Install the small site code snippet on every page where forms appear. Website builders and tag managers can usually add it through their admin or container settings.
  • Add five hidden fields to each form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Eloqua forms and third-party builders such as Gravity Forms, Typeform and Jotform each need their own field-adding steps.
  • Tag every Facebook ad URL with UTM parameters so there is something to capture.
  • Confirm a test submission arrives in Eloqua with the hidden fields populated alongside the contact details.

Do not skip the test: the whole reporting chain depends on the hidden fields being present on the form at submission.

Tagging convention for Facebook Ads

A consistent tagging pattern makes the captured data readable later. For Facebook Ads, use utm_medium to mark Paid social, utm_source to mark Facebook, utm_campaign for the campaign name, utm_term for the ad set name and utm_content for the specific ad.

You can choose your own values, but keep the mapping stable across campaigns. The drilldown fields in Eloqua will mirror these parameters, so a change in naming mid-flight will fragment campaign reporting.

How the data flows from click to Eloqua

On arrival, the site code reads the UTM parameters and stores the attribution in a browser cookie. That persistence matters: a visitor who clicks an ad, browses, leaves and returns days later still carries the original campaign data.

When they submit a form, the code writes the stored values into the hidden fields without showing them to the visitor. The submission then sends the attribution together with the contact details into Eloqua, where it can be forwarded to a CRM such as Salesforce or loaded into a BI tool such as Tableau for reporting.

What gets captured, with an example

The site code classifies each visitor into a standard channel set comparable to Google Analytics, including Organic Search, Paid Social, Paid Search and Direct. It also records the landing page URL and its group, for example a features page under /features or a blog post under /blog, so content performance can be reviewed alongside channel performance.

A worked example: a click on a Facebook ad with campaign Brand Campaign, ad set North America Ad Group and ad Green Ad produces Channel = Paid Social, Drilldown 1 = Facebook from utm_source, Drilldown 2 = Brand Campaign from utm_campaign, Drilldown 3 = North America Ad Group from utm_term and Drilldown 4 = Green Ad from utm_content. The landing page and its group are captured in addition to those five fields.

Why this approach improves accuracy

  • Coverage: attribution is recorded for every form lead, not only Facebook traffic, including Google and LinkedIn paid channels and organic sources such as Organic Search, Organic Social and Direct.
  • Persistence: cookie storage keeps the attribution across browsing and return visits, improving accuracy.
  • Normalisation: variant UTM values such as utm_source=facebook and utm_source=facebook.com are mapped to the same Paid Social channel.
  • Landing page context: the landing page URL and group show which content the campaign sent people to.

Three reports to build once data is captured

Leads by channel: because every lead carries a channel, a monthly report can compare Facebook volume against other channels and inform where budget should shift.

Customers by network: Facebook ads may also run on Instagram, Messenger or WhatsApp. Breaking customers out by network shows which placement is producing buyers, not just clicks.

Revenue by campaign: grouping new revenue by the originating campaign, then combining it with spend, lets you calculate return per dollar spent and identify campaigns running at a positive return.

Wrap up

Once the hidden fields are live, every new Eloqua lead carries its originating channel and campaign detail. That single change supports channel comparisons, network-level customer counts and campaign-level revenue reporting, and it gives marketing and sales a shared basis for deciding where the next round of budget should go. Before committing to a tool or a plan, check the current trial length, pricing and setup effort directly with the provider, since those terms can change and should be confirmed rather than assumed.

Frequently asked questions

Why is visitor traffic alone not enough?

Website visitor counts do not show how many of those visitors later became leads or customers, especially when sales close offline after the web visit.

Which hidden fields carry the attribution data into Eloqua?

Add hidden fields named Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4 to the form, then let the site code populate them from the stored attribution data at submission.

What UTM convention is recommended for Facebook Ads?

Use utm_medium for Paid social, utm_source for Facebook, utm_campaign for the campaign name, utm_term for the ad set name and utm_content for the specific ad.

What happens if a visitor leaves and returns before converting?

The attribution data is stored in a browser cookie, so it persists while the visitor browses and if they leave and return later, before being written to the form on submission.

How are inconsistent UTM values handled?

Inconsistent values such as utm_source=facebook and utm_source=facebook.com are normalised to the same Paid Social channel, reducing split reporting from naming variations.