Today’s buyers spend time researching before they ever reach out. That means a significant share of your paid media, social, and organic traffic arrives anonymously. Eloqua tracks these anonymous visitors and records the URLs they land on — including any query strings in those URLs. When a visitor later submits a form and becomes a known contact, this app looks back through their visit history, finds pages visited via tagged campaign URLs, and creates External Activities and campaign responses that would otherwise never exist.
Key Benefits
- Connect pre-conversion anonymous visits to the contacts they eventually became
- Create campaign responses that feed Eloqua’s attribution and ROI reporting
- Capture query string parameters — UTM values, campaign codes, and custom fields — into a Custom Data Object for reporting and segmentation
- Works within your existing Program Canvas setup — no custom development required
The app runs as a step in the Eloqua Program Canvas. When a new contact enters that step, it scans their pre-conversion visitor history for page visits that contain configured query string parameters.
For the app to create an External Activity and campaign response, your paid media URLs must include a query string field that contains the Eloqua Campaign ID. Additional parameters — UTM values, source data, custom fields — are captured into a Custom Data Object at the same time.
A typical tagged URL looks like this:
www.website.com/contact-us?utm_source=linkedin&utm_campaign=Q1-Brand&campaign_code=123
In this example, campaign_code=123 is the Eloqua Campaign ID. utm_source and utm_campaign are written to the CDO. Multiple parameters can be configured simultaneously.
Steps:
- A visitor clicks a tagged paid media URL and lands on an Eloqua-tracked page. The tracking script records the visit, including all query strings.
- The visitor submits a form and becomes a known contact. Eloqua links their anonymous visitor history to the new contact record.
- The contact enters the Program Canvas and reaches the app step. The app scans their visit history using a configurable lookback window.
- For each matched visit, the app creates an External Activity tied to the Eloqua Campaign ID, and writes all captured query string values to the CDO.
Note on cookies: Attribution depends on Eloqua’s tracking cookie linking a visitor’s anonymous history to their eventual form submission. If a visitor clears cookies, uses a different browser or device, or is subject to strict consent mode settings, the link may not be made. This is a platform-level behavior that affects all Eloqua visitor tracking.