Add documentation sections explaining how to track conversions with backend SDKs and reverse ETL #6502
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Based on our collaboration with customers beta testing our destination, we have found that they wanted to use it in ways we didn't expect, such as sending events from their own backend servers or using Reverse ETL sources. This PR is to add additional documentation to cover how to use our destination with those use cases.
Merge timing
ASAP once approved
Related issues (optional)
N/A