FUN-2085: Pass attribution metadata through purchase results#827
Open
FUN-2085: Pass attribution metadata through purchase results#827
Conversation
jholwill
changed the title
jholwill
force-pushed
the
codex/fun-2085-attribution-metadata-pass-through
branch
from
eabb325 to
e4ac5ca
Compare
jholwill
commented
Apr 2, 2026
api-report/purchases-js.api.json
Outdated
| "kind": "PropertySignature", | ||
| "canonicalReference": "@revenuecat/purchases-js!PresentPaywallParams#customVariables:member", | ||
| "docComment": "/**\n * Custom variables to pass to the paywall at runtime, overriding defaults set in the RevenueCat dashboard.\n *\n * Variables must be defined in the dashboard first. Reference them in paywall text using the `custom.` prefix (e.g. `{{ custom.player_name }}`).\n *\n * @example\n * ```ts\n * presentPaywall({\n * customVariables: {\n * player_name: CustomVariableValue.string('Ada'),\n * level: CustomVariableValue.string('42'),\n * },\n * });\n * ```\n *\n */\n", | ||
| "docComment": "/**\n * Custom variables to pass to the paywall at runtime, overriding defaults set in the RevenueCat dashboard.\n *\n * Variables must be defined in the dashboard first. Reference them in paywall text using the `custom.` prefix (e.g. `{{ custom.player_name }}`).\n *\n * @example\n * ```ts\n * presentPaywall({\n * customVariables: {\n * player_name: CustomVariableValue.string('Ada'),\n * level: CustomVariableValue.number(42),\n * is_premium: CustomVariableValue.boolean(true),\n * },\n * });\n * ```\n *\n */\n", |
Contributor
Author
There was a problem hiding this comment.
not sure what updated this?
The customVariables example update was picked up during rebase but is unrelated to this PR's attribution metadata changes. Co-Authored-By: Claude Opus 4.6 (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.
Summary
We need to enrich the Purchase event for funnels users who have set up the Meta integration. This PR allows the forwarding of any applicable
attribution_metadataassociated with a purchase back to any consumers as part of the response.By proxying this optional metadata from the BE , we can now send Meta Pixel events using the same event_id which allows for deduplication.
Marked the new field as
@internalas this is currently only available to use for therc-workflowsclient.Testing
Unit testing