Troubleshoot an issue in Eloqua where lead source metadata field mapping is overwriting original UTM parameters during batch imports from third-party vendor lists.
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Troubleshoot an issue in Eloqua where lead source metadata field mapping is overwriting original UTM parameters during batch imports from third-party vendor lists.
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Oracle Eloqua contact import field mapping overwrite existing values update rules UTM fields documentation Google ↗
Oracle Eloqua import data contact fields update existing records overwrite field values documentation Google ↗
- Using import and export properties · docs.oracle.com
- REST API for Oracle Eloqua Marketing Cloud Service · docs.oracle.com
- Importing contacts or accounts · docs.oracle.com
- Uploading contacts · docs.oracle.com
- Import data into Eloqua · docs.oracle.com
- Data import priority · docs.oracle.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Oracle Eloqua contact import field mapping overwrite existing values update rules UTM fields documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Oracle Eloqua import data contact fields update existing records overwrite field values documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |