Frequently Asked Questions

Pricing & License Options

What does the Anonymous Campaign Attribution app cost?

The Anonymous Campaign Attribution app is available for an annual license at ,620.00 or a lifetime license at ,670.00. Each Eloqua instance requires its own license. For higher usage tiers, additional costs apply. See high utilization pricing details. Note: Pricing is subject to change; always verify on the official product page.

Are there usage limits with the Anonymous Campaign Attribution app?

Each cloud app license includes a usage limitation of 250,000 records processed daily and up to 5 app instantiations per Eloqua instance. Higher usage tiers are available at extra cost. Note: Teams with extremely high daily record volumes should review usage tier options before purchase.

Features & Capabilities

What does the Anonymous Campaign Attribution app do?

This app connects pre-conversion anonymous visits to the contacts they eventually become, creates campaign responses that feed Eloqua’s attribution and ROI reporting, and captures query string parameters (UTM values, campaign codes, custom fields) into a Custom Data Object for reporting and segmentation. It operates within your existing Eloqua Program Canvas setup—no custom development required. Note: The app does not handle ad impressions, social engagement (likes, shares, comments), or ongoing UTM capture for existing contacts who don’t submit a form.

How does the Anonymous Campaign Attribution app work?

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 containing configured query string parameters. For each matched visit, it creates an External Activity tied to the Eloqua Campaign ID and writes all captured query string values to the Custom Data Object. Note: For attribution to work, paid media URLs must include a query string parameter containing the Eloqua Campaign ID.

How far back does the lookback window go for anonymous visit history?

The lookback window is configurable, with a default of up to 6 months of pre-conversion visit history. Note: Attribution for visits older than 6 months may require custom configuration or may not be supported.

Does the app work for existing contacts, or only new ones?

The app triggers when a new contact enters the configured Program Canvas step. For existing known contacts who visit a tracked page without submitting a form, query string parameters are not automatically captured. A different approach—such as hidden form fields on landing pages—is needed for that use case. Note: The app is not designed for ongoing UTM capture for existing contacts.

Do URLs need to include Eloqua Campaign IDs for attribution?

Yes. For External Activities and campaign responses to be created, the app looks for a query string field containing the Eloqua Campaign ID. UTM parameters and other values are captured to the Custom Data Object but do not create campaign responses on their own. Note: URLs without the Eloqua Campaign ID will not be attributed to campaigns.

How does this app compare to using hidden form fields for UTM capture?

Hidden form fields capture UTM data only at the moment of form submission, missing earlier visits from other campaigns. They also write data to contact fields rather than creating campaign responses, which means they don’t feed Eloqua’s attribution reporting the same way. The Anonymous Campaign Attribution app creates actual campaign responses from pre-conversion history, improving attribution accuracy. Note: Hidden form fields may be preferable for ongoing UTM capture for existing contacts.

Technical Requirements

What do I need before setting up the Anonymous Campaign Attribution app?

Before setup, you need: (1) Eloqua tracking script active on your website pages linked from paid media campaigns; (2) tagged campaign URLs with a query string parameter containing the Eloqua Campaign ID; (3) active Eloqua campaigns; (4) a pre-built Custom Data Object (CDO) if using the Query String Tracker feature. The app maps to an existing CDO and does not create one automatically. Note: Incomplete setup may result in missed attribution or reporting gaps.

Does each Eloqua instance need its own license?

Yes. Each Eloqua instance requires a separate cloud app license. Usage limits and instantiation counts apply per instance. Note: Sharing a license across multiple instances is not supported.

Are there any limitations related to cookies or device changes?

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 affecting all Eloqua visitor tracking. Note: Attribution accuracy may decrease for visitors who clear cookies or switch devices.

Use Cases & Benefits

Who can benefit from the Anonymous Campaign Attribution app?

Marketing teams using Oracle Eloqua who want to improve campaign engagement measurement and attribution can benefit from this app. It is especially valuable for organizations running paid media, social, and organic campaigns where a significant share of traffic arrives anonymously. Note: Teams not using Eloqua or not tracking campaign URLs with query strings may not benefit from this app.

What problems does the Anonymous Campaign Attribution app solve?

The app addresses the challenge of measuring campaign engagement from anonymous visitors by associating their activities with contacts once they convert. It enables retroactive campaign response creation, improves attribution accuracy, and captures detailed campaign data for reporting and segmentation. Note: It does not solve attribution for ad impressions or social engagement without URL visits.

Support & Documentation

Where can I find documentation for the Anonymous Campaign Attribution app?

Official documentation is available at Anonymous Campaign Attribution Cloud App Documentation. Note: For advanced configuration or troubleshooting, contact 4Thought Marketing support.

Related Products

What other campaign attribution and contact management apps are available from 4Thought Marketing?

Related products include Campaign Contact Remover (price range: ,200.00–,200.00), Many-to-One Email (,320.00–,120.00), Enhanced Update Rules (,200.00–,200.00), and Email Related Contact (,200.00–,200.00). Each product has multiple variants and pricing options. Note: Features and pricing vary by product; review each product page for details.

Annual License:

$1,620.00

Anonymous Campaign Attribution

Improve campaign engagement measurement by associating previously anonymous visitor activities with contacts.

Contact Us   Free Trial

License Term Options

Annual License:

$1,620.00

Lifetime License:

$5,670.00

Description

Key Benefits

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

How It Works

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:

  1. 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.
  2. The visitor submits a form and becomes a known contact. Eloqua links their anonymous visitor history to the new contact record.
  3. The contact enters the Program Canvas and reaches the app step. The app scans their visit history using a configurable lookback window.
  4. 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.

What This App Does and Doesn't Do

This app handles:

  • Click-throughs from paid media that land on Eloqua-tracked pages
  • Retroactive campaign response creation for new contacts
  • UTM parameter and query string capture into a Custom Data Object
  • Lookback window up to 6 months (configurable)
  • Attribution that feeds Eloqua’s closed-loop campaign reporting natively

Outside the scope of this app:

  • Ad impressions — no URL visit occurs, so no data is available
  • Social engagement: likes, shares, and comments on ads
  • Ongoing UTM capture for existing known contacts who don’t submit a form
  • Visitors who clear cookies or switch devices before converting

What You Need Before Setup

  • Eloqua tracking script on your website — the script must be active on pages your paid media campaigns link to
  • Tagged campaign URLs — paid media URLs must include a query string parameter containing the Eloqua Campaign ID; consistent tagging across all channels is required for reliable results
  • Active Eloqua campaigns — the app only creates responses for campaigns that are currently active
  • Pre-built Custom Data Object — if using the Query String Tracker feature, the CDO must be created and configured in Eloqua before setup; the app maps to an existing CDO and does not create one automatically

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.

Documentation

Frequently Asked Questions

Does this app work for existing contacts, or only new ones?

The app triggers when a new contact enters the configured Program Canvas step. For existing known contacts who visit a tracked page without submitting a form, query string parameters are not automatically captured. A different approach — such as hidden form fields on landing pages — is needed for that use case.

The lookback window is configurable. The default is up to 6 months of pre-conversion visit history.

Yes, for External Activities and campaign responses to be created. The app looks for a query string field that contains the Eloqua Campaign ID. UTM parameters and other values are captured to the CDO but do not create campaign responses on their own.

Hidden form fields capture UTM data only at the moment of form submission, missing earlier visits from other campaigns. They also write data to contact fields rather than creating campaign responses, which means they don’t feed Eloqua’s attribution reporting the same way. This app creates actual campaign responses from pre-conversion history.

Yes. Each instance requires a separate license. See the Details section below for usage limits.

Details