Update custom-domain.md #6923
Merged
Update custom-domain.md #6923
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prigiattiperrut
requested review from
forstisabella,
alanjcharles and
atitsh
and removed request for
alanjcharles
atitsh
previously approved these changes
Aug 13, 2024
forstisabella
approved these changes
Aug 13, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This update adds two new FAQ sections to the documentation page:
Benefit of Migrating Server-Side Sources to Custom Domain: Explains why server-side tracking is generally more reliable than client-side tracking and recommends keeping business-critical events server-side for more accurate and reliable tracking.
Configuring Non-JavaScript Sources to Use Custom Domain: Provides guidance on how to configure non-JavaScript sources to use Custom Domain for consistency, including specific instructions for updating implementations to use the subdomain as an endpoint when using the Tracking API.
Merge timing
ASAP once approved?
Related issues (optional)
Slack: https://twilio.slack.com/archives/CTTKLTS76/p1723156941435869