Complete developer integration documentation - #47
Merged
Conversation
✅ Deploy Preview for legendary-lollipop-e2d131 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pelcasandra
marked this pull request as ready for review
August 7, 2026 05:33
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Why
The previous developer content explained individual endpoints but did not give teams a reliable implementation sequence or clearly separate browser activity from trusted backend events. It also contained outdated session parameters, incomplete SMS guidance, and references that no longer matched the public API.
This update gives developers a practical path from initial authentication through production verification while keeping the English and Spanish documentation aligned.
User impact
Developers integrating a custom store can now follow one complete implementation guide, choose the correct tracking source, connect anonymous sessions safely, send and verify SMS messages, and troubleshoot common integration failures without reconstructing the workflow from separate API entries.
Validation
bundle exec jekyll buildgit diff --check origin/main...HEAD