Skip to content

Commit d15b91d

Browse files
authored
Merge pull request #556 from segmentio/repo-sync
repo sync
2 parents 6f72536 + 66f768c commit d15b91d

File tree

2 files changed

+9
-2
lines changed
  • src/connections/destinations/catalog

2 files changed

+9
-2
lines changed

src/connections/destinations/catalog/actions-google-analytics-4/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ id: 60ad61f9ff47a16b8fb7b5d9
1010
When you have Segment installed, you can use your existing tracking implementation to fulfill your data collection needs with Google Analytics 4. Segment will send your data server-side to [Google's Measurement Protocol API](https://developers.google.com/analytics/devguides/collection/protocol/ga4){:target='_blank'}.
1111

1212
> warning ""
13-
> Google Analytics 4 doesn't officially support a pure server-to-server integration. However, Segment monitors the capabilities of the Measurement Protocol API and updates accordingly to achieve a reasonable level of reporting for mutual customers. Segment doesn't plan to build a device-mode integration with Gtag for Google Analytics 4.
13+
> Google Analytics 4 doesn't officially support a pure server-to-server integration. However, Segment monitors the capabilities of the Measurement Protocol API and updates the integration accordingly to achieve a reasonable level of reporting for mutual customers.
1414
1515
> success "Good to know"
1616
> This page is about the [Actions-framework](/docs/connections/destinations/actions/) Google Analytics 4 destination. There's also a page about the [non-Actions Google Universal Analytics destination](/docs/connections/destinations/catalog/google-analytics/). Both of these destinations receive data _from_ Segment.

src/connections/destinations/catalog/actions-salesforce/index.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,5 +89,12 @@ Person Accounts are not enabled by default, and the solution above will only wor
8989
- For `update` and `upsert`, the query request used to determine whether the record already exists in Salesforce counts as one API call. A second API call is used to update or create that record.
9090
- For `create`, no query is executed so one API call is used to create the record.
9191

92+
To check how many API calls you have left in Salesforce, go to **Setup > Company Settings > Company Information**, and you’ll find a field labeled: `API Requests, Last 24 Hours`.
93+
94+
### Why do I see duplicate records in Salesforce?
95+
When using the `create` operation, it's possible for duplicate records to be created in Salesforce. This is because Segment retries records once they hit the internal timeout. It's possible Salesforce's REST API eventually processes the original record in addition to the retried record, resulting in duplicates. You may encounter this behavior if Salesforce's REST API throttles your records (for example, due to hitting API limits or complex workflow automation). To prevent duplicates, you can use [Duplicate Rules](https://help.salesforce.com/s/articleView?id=duplicate_rules_map_of_reference.htm&language=en_US){:target="_blank"} in Salesforce. See set up information in [Resolve and Prevent Duplicate Data in Salesforce](https://trailhead.salesforce.com/content/learn/modules/sales_admin_duplicate_management/sales_admin_duplicate_management_unit_2){:target="_blank"}.
96+
97+
Please note this is only a concern when using the `create` operation. You can use the `upsert` operation instead to avoid duplicates if `upsert` meets your needs.
98+
9299
### Can I send data to the Salesforce Bulk API 2.0?
93-
Segment is in the process of adding support for the Bulk API to help reduce API calls made to Salesforce. This is not yet available.
100+
Segment is in the process of adding support for the Bulk API to help reduce API calls made to Salesforce. This is not yet available.

0 commit comments

Comments
 (0)