Salesforce terms starting with J

A Job in Bulk API 2.0 is the unit of work Salesforce uses to insert, update, upsert, delete, or query large volumes of records asynchronously. A client creates the job with a small JSON request, uploads the record data as a CSV, then marks the upload complete. Salesforce queues the work, splits it into batches on its own, processes the rows in parallel, and writes the outcome to result files the client downloads later. The whole exchange happens over REST, and the client never blocks waiting for the data to load. Bulk API 2.0 is the practical choice for any load above roughly 2,000 records, and the only sensible one for multi-million-row migrations or nightly syncs. It removed the manual batch management that the original Bulk API required, so a caller no longer creates or tracks individual batches. A single ingest job can take up to 150 MB of CSV data per upload, and an org can process up to 150 million records across all jobs in a rolling 24-hour window. The Job resource reports its own state, record counters, and the URLs of the success and failure files.

Journey Analytics is the set of reporting tools in Salesforce Marketing Cloud Engagement that measure how customer journeys built in Journey Builder perform. It covers two related things: the per-journey analytics built into Journey Builder (goal attainment, current population, journey health, and journey history), and the dedicated Journey Analytics dashboard that combines Marketing Cloud send-and-engagement data with website behavior from a connected Google Analytics account. A journey is a multi-step automated flow that moves a contact through messages and decisions over time. Journey Analytics is the feedback loop on top of it. It tells a marketer which steps drive action, where contacts stall, and whether the journey hit its goal. Without it, a journey is a send-and-hope exercise. With it, marketers revise wait times, content, and decision splits based on what the numbers show.

JSON (JavaScript Object Notation) is a lightweight, text-based format for representing structured data as key-value pairs and ordered lists. In Salesforce, it is the default body format for REST API requests and responses, Apex HTTP callouts, platform event and Change Data Capture payloads, and the data passed between Apex and Lightning components. Because most modern web services speak JSON, it is the common format Salesforce uses to exchange data with outside systems. Apex has built-in JSON support through the System.JSON class, which converts Apex objects to JSON strings and parses JSON strings back into Apex objects. The same class exposes a streaming generator and parser for large or custom payloads. JavaScript in Lightning Web Components and Aura already treats JSON as its native object format, so data crossing the Apex-to-browser boundary is serialized and parsed automatically. Reading and writing JSON correctly is a core skill for any Salesforce integration work.

A junction object is a custom Salesforce object that uses two master-detail relationships to create a many-to-many association between two other objects. It is the bridge record that joins one parent to another, holding the relationship details and any attributes that belong to that specific pairing rather than to either parent alone. The pattern is the standard Salesforce answer to many-to-many: Object A relates to many of Object B, and Object B relates to many of Object A. Each junction record represents one specific A-to-B link. Salesforce ships several built-in examples, including AccountContactRelation, which joins Account and Contact when a contact works across multiple companies, and CampaignMember, which links a Campaign to a Lead or Contact for attribution.