[{"data":1,"prerenderedAt":269},["ShallowReactive",2],{"navigation":3,"page-\u002Fen\u002Fsetup\u002Fthe-integration-user":88,"\u002Fen\u002Fsetup\u002Fthe-integration-user-surround":263,"comments-\u002Fen\u002Fsetup\u002Fthe-integration-user":268},[4],{"title":5,"path":6,"stem":7,"children":8,"page":87},"En","\u002Fen","en",[9,53],{"title":10,"path":11,"stem":12,"children":13,"icon":52},"CRM Analytics Foundations","\u002Fen\u002Ffoundations","en\u002F1.foundations\u002F1.index",[14,16,20,24,28,32,36,40,44,48],{"title":15,"path":11,"stem":12},"Welcome & Dev Org",{"title":17,"path":18,"stem":19},"Graded Quiz","\u002Fen\u002Ffoundations\u002Fquiz","en\u002F1.foundations\u002F10.quiz",{"title":21,"path":22,"stem":23},"What Is CRM Analytics?","\u002Fen\u002Ffoundations\u002Fwhat-is-crm-analytics","en\u002F1.foundations\u002F2.what-is-crm-analytics",{"title":25,"path":26,"stem":27},"Architecture","\u002Fen\u002Ffoundations\u002Farchitecture-and-data-flow","en\u002F1.foundations\u002F3.architecture-and-data-flow",{"title":29,"path":30,"stem":31},"The Data Layer","\u002Fen\u002Ffoundations\u002Fthe-data-layer","en\u002F1.foundations\u002F4.the-data-layer",{"title":33,"path":34,"stem":35},"The Design Layer","\u002Fen\u002Ffoundations\u002Fthe-design-layer","en\u002F1.foundations\u002F5.the-design-layer",{"title":37,"path":38,"stem":39},"The Intelligence Layer","\u002Fen\u002Ffoundations\u002Fthe-intelligence-layer","en\u002F1.foundations\u002F6.the-intelligence-layer",{"title":41,"path":42,"stem":43},"Hands-On Tour","\u002Fen\u002Ffoundations\u002Fhands-on-tour","en\u002F1.foundations\u002F7.hands-on-tour",{"title":45,"path":46,"stem":47},"Six Adoption Steps","\u002Fen\u002Ffoundations\u002Fsix-steps-and-interview-prep","en\u002F1.foundations\u002F8.six-steps-and-interview-prep",{"title":49,"path":50,"stem":51},"Interview Questions","\u002Fen\u002Ffoundations\u002Finterview-questions","en\u002F1.foundations\u002F9.interview-questions","i-lucide-compass",{"title":54,"path":55,"stem":56,"children":57,"icon":86},"Setup & User Provisioning","\u002Fen\u002Fsetup","en\u002F2.setup\u002F1.index",[58,60,64,68,72,76,80,83],{"title":59,"path":55,"stem":56},"Provisioning Users",{"title":61,"path":62,"stem":63},"Licenses & Permissions","\u002Fen\u002Fsetup\u002Flicenses-and-permission-sets","en\u002F2.setup\u002F2.licenses-and-permission-sets",{"title":65,"path":66,"stem":67},"Integration User","\u002Fen\u002Fsetup\u002Fthe-integration-user","en\u002F2.setup\u002F3.the-integration-user",{"title":69,"path":70,"stem":71},"Security User","\u002Fen\u002Fsetup\u002Fthe-security-user","en\u002F2.setup\u002F4.the-security-user",{"title":73,"path":74,"stem":75},"Analytics Settings","\u002Fen\u002Fsetup\u002Fanalytics-settings","en\u002F2.setup\u002F5.analytics-settings",{"title":77,"path":78,"stem":79},"Hands-On Access","\u002Fen\u002Fsetup\u002Fhands-on-assigning-access","en\u002F2.setup\u002F6.hands-on-assigning-access",{"title":17,"path":81,"stem":82},"\u002Fen\u002Fsetup\u002Fquiz","en\u002F2.setup\u002F7.quiz",{"title":49,"path":84,"stem":85},"\u002Fen\u002Fsetup\u002Finterview-questions","en\u002F2.setup\u002F8.interview-questions","i-lucide-settings-2",false,{"id":89,"title":90,"access":91,"body":92,"description":253,"extension":254,"interview":91,"links":91,"meta":255,"navigation":256,"passScore":91,"path":66,"quiz":91,"seo":257,"stem":67,"video":258,"__hash__":262},"docs\u002Fen\u002F2.setup\u002F3.the-integration-user.md","The CRM Analytics Integration User & Data Language",null,{"type":93,"value":94,"toc":243},"minimark",[95,100,109,114,125,128,138,142,149,164,178,185,196,199,204,215,230,234,237],[96,97,99],"h1",{"id":98},"the-integration-user-data-language","The Integration User & Data Language",[101,102,103,104,108],"p",{},"CRM Analytics needs a way to reach into your core Salesforce data and copy it into datasets. It does this through a special, system-created account called the ",[105,106,107],"strong",{},"Analytics Integration User",". You will rarely interact with it directly, but understanding what it does — and its two big gotchas — will save you hours of confused debugging.",[110,111,113],"h2",{"id":112},"what-the-integration-user-does","What the Integration User does",[101,115,116,117,121,122,124],{},"When you sync or replicate Salesforce objects into CRM Analytics, the platform does not use ",[118,119,120],"em",{},"your"," login to read the data. Instead it authenticates as the ",[105,123,65],{}," and reads the objects and fields on your behalf, pulling records into the staging layer and ultimately into datasets.",[101,126,127],{},"Because this user is the engine behind every data sync, one rule is non-negotiable:",[129,130,132],"note",{"icon":131},"i-lucide-shield-alert",[101,133,134,137],{},[105,135,136],{},"Do not delete or deactivate the Analytics Integration User."," It is created for you automatically, and CRM Analytics data sync depends on it. Removing or disabling it breaks ingestion across the whole org.",[110,139,141],{"id":140},"standard-fields-work-custom-fields-do-not-automatically","Standard fields work; custom fields do not — automatically",[101,143,144,145,148],{},"By default, the Integration User is provisioned with access to ",[105,146,147],{},"most standard Salesforce objects and fields",". Sync an Account, an Opportunity, or a Case out of the box and it generally just works.",[101,150,151,152,155,156,159,160,163],{},"The trap is ",[105,153,154],{},"custom objects and custom fields."," The Integration User does ",[105,157,158],{},"not"," automatically have read access to your custom schema. If you try to sync a custom object — or pull a custom field on a standard object — without granting that access first, the sync will ",[105,161,162],{},"warn or fail",", and the field will silently come across empty.",[129,165,167],{"icon":166},"i-lucide-triangle-alert",[101,168,169,170,173,174,177],{},"Whenever you add a ",[105,171,172],{},"custom object or custom field"," to a data sync, remember to grant the ",[105,175,176],{},"Integration User read access"," to it (via its permission set or profile). A large share of \"why is my field blank?\" issues trace straight back to this.",[110,179,181,182],{"id":180},"locale-sets-the-language-of-your-data-values","Locale sets the language of your data ",[118,183,184],{},"values",[101,186,187,188,191,192,195],{},"Here is a subtle behavior that surprises even experienced admins. The Integration User has a ",[105,189,190],{},"locale"," setting, and that locale controls the ",[105,193,194],{},"language of the data values"," that get brought into your datasets.",[101,197,198],{},"To make the distinction concrete, CRM Analytics has two separate \"languages\" in play:",[200,201],"lesson-cards",{":columns":202,":items":203},"2","[{\"title\":\"Labels & headers\",\"icon\":\"i-lucide-tag\",\"description\":\"Field labels, column headers, and UI chrome follow the running user and the company\u002Forg language settings.\"},{\"title\":\"Data values\",\"icon\":\"i-lucide-database\",\"description\":\"The actual picklist and field values inside the data — like Opportunity Stage names — follow the Integration User's locale.\"}]",[101,205,206,207,210,211,214],{},"So if the Integration User's locale is set to, say, French, the ",[105,208,209],{},"stage values"," flowing into your dataset (the contents of records, not the column names) can come in translated to French — even while your dashboard labels appear in English because ",[118,212,213],{},"you"," are the running user. When picklist values show up in an unexpected language, the Integration User's locale is the first place to look.",[216,217,219],"tip",{"icon":218},"i-lucide-languages",[101,220,221,222,225,226,229],{},"Remember the split: the ",[105,223,224],{},"running user and company"," drive labels and headers; the ",[105,227,228],{},"Integration User's locale"," drives the language of the data values themselves. Set the Integration User's locale deliberately to match how you want your data to read.",[110,231,233],{"id":232},"why-this-matters","Why this matters",[101,235,236],{},"The Integration User is the quiet workhorse of CRM Analytics. Treat it well — keep it active, grant it access to every custom object and field you sync, and set its locale intentionally — and your data will land clean and complete. Neglect any of those and you will chase blank columns and mysteriously translated picklists.",[101,238,239,240,242],{},"Next we meet the other special account CRM Analytics relies on: the ",[105,241,69],{},", which powers row-level security.",{"title":244,"searchDepth":245,"depth":246,"links":247},"",1,2,[248,249,250,252],{"id":112,"depth":246,"text":113},{"id":140,"depth":246,"text":141},{"id":180,"depth":246,"text":251},"Locale sets the language of your data values",{"id":232,"depth":246,"text":233},"Meet the Analytics Integration User: how it reads Salesforce data into datasets, why custom objects need explicit access, and how its locale sets the language of data values.","md",{},{"title":65},{"title":90,"description":253},{"id":259,"start":260,"end":261},"0UrasqsdHXU",124,233,"Wu-pWjikYWq7VUv9raMHau7yVzkB99wVrAVb2FYTmQM",[264,266],{"title":61,"path":62,"stem":63,"description":265,"children":-1},"Understand the CRM Analytics Plus permission-set license versus permission sets, and how Manage Analytics and scoped permission sets grant the right access to each user.",{"title":69,"path":70,"stem":71,"description":267,"children":-1},"Learn what the CRM Analytics Security User does: previewing data in recipes and reading User-object fields for security predicates that drive row-level security.",[],1783463463831]