What steps fix metadata field mapping errors when syncing historical CSV imports into Salesforce Marketing Cloud Account Engagement?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What steps fix metadata field mapping errors when syncing historical CSV imports into Salesforce Marketing Cloud Account Engagement?
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
Salesforce Account Engagement import prospects CSV field mapping custom fields sync Salesforce CRM documentation Google ↗
Salesforce Account Engagement prospect field sync behavior CRM field mapping import CSV historical data documentation Google ↗
- Map Salesforce and Account Engagement Custom Fields · help.salesforce.com
- Field does not sync in Account Engagement · help.salesforce.com
- Considerations for Prospect Imports · help.salesforce.com
- Imports | Version 5 Docs | Account Engagement API · developer.salesforce.com
- Import Prospects · help.salesforce.com
- Prospect Field Sync Behavior · help.salesforce.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Salesforce Account Engagement import prospects CSV field mapping custom fields sync Salesforce CRM documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Salesforce Account Engagement prospect field sync behavior CRM field mapping import CSV historical data documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |