Skip to content

Add presented offering context to paywall events#818

Draft
rickvdl wants to merge 1 commit intomainfrom
rickvdl/add-presented-offering-context-to-paywall-events
Draft

Add presented offering context to paywall events#818
rickvdl wants to merge 1 commit intomainfrom
rickvdl/add-presented-offering-context-to-paywall-events

Conversation

@rickvdl
Copy link
Copy Markdown
Member

@rickvdl rickvdl commented Mar 24, 2026

Summary

  • Include placement_identifier, targeting_revision, and targeting_rule_id in paywall events under a presented_offering_context nested object
  • Field is omitted when no placement or targeting data exists
  • Consistent with iOS and Android implementations

Related PRs

Test plan

  • Unit tests for all context permutations (full, placement-only, targeting-only, none, empty string)
  • JSON round-trip serialization tests
  • Integration test verifying context flows from offering to event payload
  • Manual testing with targeting rules and placements in demo app

Include placement_identifier, targeting_revision, and targeting_rule_id
in paywall events when available, nested under presented_offering_context.
The field is omitted entirely when no placement or targeting data exists.
Matches the iOS and Android implementations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant