Skip to content

Conversation

@thomson-t
Copy link
Collaborator

Background

The Rokt integration start time is not captured when the partner invokes selectPlacements.
Add PlacementOptions and add support for integrationStartTimestamp to pass it down to the Rokt Kit.

What Has Changed

  • Add integration start timestamp to the PlacementOptions object and pass it down to RoktKit
  • Add unit tests

Screenshots/Video

N/A

Checklist

  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have tested this locally.

Additional Notes

  • {Any additional information or context relevant to this PR}

Reference Issue (For employees only. Ignore if you are an outside contributor)

- Add integration start timestamp to the `PlacementOptions` object and pass it down to RoktKit
- Add unit tests
@thomson-t thomson-t requested a review from a team as a code owner January 15, 2026 22:21
@sonarqubecloud
Copy link

@Nullable Map<String, WeakReference<Typeface>> fontTypefaces,
@Nullable RoktConfig config);

void execute(@NonNull String identifier,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given this will end up changing in next major release is it worth calling it select placements and removing callbacks now to save the deprecation?

Additionally is it worth investigating making a dedicated interface / protocol for Rokt specific functions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants