Add the Customer.io CDP write key - #132
Merged
Merged
Conversation
Verified with one live identify through CustomerioService before committing: the call succeeded and the postal code resolved through Represent, so both the key and the payload shape are good. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Adds
customerio.api_keyto encrypted credentials, the remaining blocker from #131.Verified before committing with one live identify through
CustomerioServiceagainst the real endpoint: the call succeeded, and the location lookup resolvedM5V 1A1→ Toronto / Spadina—Harbourfront, so both the key and the payload shape are confirmed working rather than assumed.The smoke test created one person in the Customer.io workspace (
cio-smoke-test-<timestamp>@buildcanada.com) — worth deleting there. The local subscriber row was removed.Once this is merged, a deploy picks it up:
RAILS_MASTER_KEYis already in the Kamal secrets, andbin/docker-entrypointrunsdb:prepareon boot, so the two new columns migrate as part of the same deploy.🤖 Generated with Claude Code