--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/best-practices-usage.md cuppy_section: docs cuppy_doc: Q6YQ-TZZF cuppy_doc_uuid: f854700f-6434-4634-b3ec-a547bc83995e cuppy_permalink: https://cuppy.io/salesforce/d/Q6YQ-TZZF cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/best-practices-usage cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: 7e9f42490533bef12e86414638670b0cf24f887f1a9662b0fe8015dd8496c2be # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Best Practices for Optimizing Usage To stay within your consumption credits, follow best practices to optimize your service and data usage. Customer and Salesforce partners can follow these tips. Write optimized code that’s inexpensive, such as queries. You can write SQL queries to fetch only the data that you need. Queries are preferable over GET API requests because they offer more flexibility in choosing the data that you want to retrieve. To write efficient queries, add a WHERE clause to filter the returned results and retrieve the smallest set of required records. Also, specify only the fields that you need in the SELECT statement. For example, this query is efficient because it gets one Individual record for a specific Individual ID value. Connect REST API resource: SQL query: You can query data via Connect REST API. See the Query Library section in [Data Cloud Resources](https://developer.salesforce.com/docs/platform/connectapi/references/about-sample-api/about-connect-api.html) in the _Data Cloud Connect REST API Guide_. Or see [Query Data using Query API](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/c360a-api-queryservices-overview.html) and [Query Customer Profile Information with Profile API](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/data-cloud-query-api-reference/c360a-api-profile-call-overview.html) in the _Data Cloud Query Guide_. Alternatively, you can use SOQL to query data. For more information, see [Data Cloud Query Profile Parameters](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_cdp_query.htm) in the _REST API Developer Guide_. As part of your data ingestion strategy, ensure that you import relevant data records into Data 360 and that you don’t import more data than what’s needed. Sometimes it’s better to aggregate data before ingesting it rather than ingesting every data point, especially if not all attributes are relevant. When testing a custom app, limit the amount of testing data in the test org. Use a sample of records that’s sufficient to meet your functional testing needs. --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.