Skip to content

Use connected publication for RRM datapoints - #14124

Merged
hussain-t merged 23 commits into
developfrom
enhancement/#13429-use-connected-publication
Nov 18, 2026
Merged

hussain-t merged 23 commits into
developfrom
enhancement/#13429-use-connected-publication

Conversation

@nfmohit

@nfmohit nfmohit commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Related issue(s):

Relevant technical choices

The datapoints require organizationID and publicationID, and the data store reads them from the module's settings before each request, so callers pass nothing.

Settings saved before express setup hold a publication ID without an organization ID. getPublicationParams() reads the organization from the publications list in that case.

getPublication() and getCTAs() take no arguments and read through keyed selectors that carry the resolvers, so changing the publication requests the new one's data on its own. There are inline comments on both.

Publications fetched one at a time are stored under their ID, separately from the publications list. Before, getPublication() wrote the publication it fetched into the list, so getPublications() saw a loaded list of one and never requested the real one, and the connect-publication step offered only the connected publication.

The branch was reset to develop and force-pushed, so the history is new. The earlier commits are kept at the archive/13429-connected-only tag.

Deviations from IB

  • The datapoints require the identifiers. The IB has them read the connected publication from settings. Agreed with @aaemnnosttv after @JakePT's third review found a case the IB's approach could not cover: with no identifier in the request, the client cannot tell which publication a response describes, so changing the publication while a request was in flight left the CTA list empty.
  • Missing_Required_Setting_Exception is deleted. A missing identifier is a missing parameter now.
  • Synchronization::get_datapoint_data() is kept. The IB has it deleted. The crons pass the identifiers the datapoints now require, so Synchronization.php is unchanged.
  • The CTAs stay keyed by publication ID. The IB asks for a single list, which needs a manual reset when the publication changes.
  • submitChanges() no longer touches the CTAs or the publication. Keyed resolution requests the new publication's data on its own.
  • Publications are stored by ID. Not in the IB. It is included here because it fixes the connect-publication step.
  • No new test in SynchronizationTest. The datapoint tests cover that each request carries the identifiers, and CronTest covers that a cron fires it.

PR Author Checklist

  • My code is tested and passes existing unit tests.
  • My code has an appropriate set of unit tests which all pass.
  • My code is backward-compatible with WordPress 5.2 and PHP 7.4.
  • My code follows the WordPress coding standards.
  • My code has proper inline documentation.
  • I have added a QA Brief on the issue linked above.
  • I have signed the Contributor License Agreement (see https://cla.developers.google.com/).

Do not alter or remove anything below. The following sections will be managed by moderators only.

Code Reviewer Checklist

  • Run the code.
  • Ensure the acceptance criteria are satisfied.
  • Reassess the implementation with the IB.
  • Ensure no unrelated changes are included.
  • Ensure CI checks pass.
  • Check Storybook where applicable.
  • Ensure there is a QA Brief.
  • Ensure there are no unexpected significant changes to file sizes.

Merge Reviewer Checklist

  • Ensure the PR has the correct target branch.
  • Double-check that the PR is okay to be merged.
  • Ensure the corresponding issue has a ZenHub release assigned.
  • Add a changelog message to the issue.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the Reader Revenue Manager module to automatically use the connected publication from the saved settings for CTA and publication-related actions and selectors, rather than passing publication identifiers (publicationID and organizationID) as parameters. On the JavaScript side, getCTAs, createCTA, getPublication, and updatePublication have been updated to no longer accept these identifiers, and new actions/selectors like clearCTAs, resetCTAs, getSavedPublicationID, and getSavedOrganizationID have been introduced. On the PHP side, a new Connected_Publication_Datapoint base class has been added to handle retrieving the connected publication settings, simplifying the Create_CTA, Get_CTAs, Get_Publication, and Update_Publication datapoints, as well as the synchronization crons. All corresponding tests and stories have been updated to align with these API changes. I have no further feedback to provide as no review comments were submitted.

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

🤖 This comment is automatically updated by CI workflows. Each section is managed independently.

📚 Storybook for 072ce5a:

📦 Build files for 072ce5a:

  • Build files have been deleted.

🖼️ VRT report for 072ce5a:

  • Reports have been deleted.

🎭 Playwright reports for 072ce5a:

  • Reports have been deleted.

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Size Change: 0 B

Total Size: 3.55 MB

ℹ️ View Unchanged
Filename Size Change
dist/assets/blocks/reader-revenue-manager/block-editor-plugin/editor-styles.css 124 B 0 B
dist/assets/blocks/reader-revenue-manager/block-editor-plugin/editor-styles.js 0 B 0 B 🆕
dist/assets/blocks/reader-revenue-manager/block-editor-plugin/index.js 47.1 kB 0 B
dist/assets/blocks/reader-revenue-manager/common/editor-styles.css 307 B 0 B
dist/assets/blocks/reader-revenue-manager/common/editor-styles.js 0 B 0 B 🆕
dist/assets/blocks/reader-revenue-manager/contribute-with-google/index.js 7.25 kB 0 B
dist/assets/blocks/reader-revenue-manager/contribute-with-google/non-site-kit-user.js 6.46 kB 0 B
dist/assets/blocks/reader-revenue-manager/subscribe-with-google/index.js 7.26 kB 0 B
dist/assets/blocks/reader-revenue-manager/subscribe-with-google/non-site-kit-user.js 6.46 kB 0 B
dist/assets/blocks/sign-in-with-google/editor-styles.css 84 B 0 B
dist/assets/blocks/sign-in-with-google/editor-styles.js 0 B 0 B 🆕
dist/assets/blocks/sign-in-with-google/index.js 18.5 kB 0 B
dist/assets/css/googlesitekit-admin-css-********************.min.css 78.8 kB 0 B
dist/assets/css/googlesitekit-adminbar-css-********************.min.css 12.7 kB 0 B
dist/assets/css/googlesitekit-authorize-application-css-********************.min.css 851 B 0 B
dist/assets/css/googlesitekit-wp-dashboard-css-********************.min.css 9.09 kB 0 B
dist/assets/js/492-********************.js 970 B 0 B
dist/assets/js/959-********************.js 3 kB 0 B
dist/assets/js/1020-********************.js 1.03 kB 0 B
dist/assets/js/1212-********************.js 2.26 kB 0 B
dist/assets/js/1315-********************.js 3.08 kB 0 B
dist/assets/js/3022-********************.js 2.41 kB 0 B
dist/assets/js/3741-********************.js 3.84 kB 0 B
dist/assets/js/6174-********************.js 3.67 kB 0 B
dist/assets/js/7603-********************.js 61.5 kB 0 B
dist/assets/js/7792-********************.js 110 kB 0 B
dist/assets/js/9397-********************.js 477 kB 0 B
dist/assets/js/analytics-advanced-tracking-********************.js 428 B 0 B
dist/assets/js/googlesitekit-activation-********************.js 31.8 kB 0 B
dist/assets/js/googlesitekit-ad-blocking-recovery-********************.js 71.4 kB 0 B
dist/assets/js/googlesitekit-admin-pointers-********************.js 6.88 kB 0 B
dist/assets/js/googlesitekit-adminbar-********************.js 38.8 kB 0 B
dist/assets/js/googlesitekit-api-********************.js 9.91 kB 0 B
dist/assets/js/googlesitekit-block-tracking-********************.js 6.88 kB 0 B
dist/assets/js/googlesitekit-components-********************.js 7.02 kB 0 B
dist/assets/js/googlesitekit-consent-mode-********************.js 25.5 kB 0 B
dist/assets/js/googlesitekit-data-********************.js 1.84 kB 0 B
dist/assets/js/googlesitekit-datastore-forms-********************.js 8.6 kB 0 B
dist/assets/js/googlesitekit-datastore-location-********************.js 1.6 kB 0 B
dist/assets/js/googlesitekit-datastore-pdf-********************.js 1.23 kB 0 B
dist/assets/js/googlesitekit-datastore-site-********************.js 21.7 kB 0 B
dist/assets/js/googlesitekit-datastore-ui-********************.js 8.76 kB 0 B
dist/assets/js/googlesitekit-datastore-user-********************.js 26.9 kB 0 B
dist/assets/js/googlesitekit-entity-dashboard-********************.js 97.4 kB 0 B
dist/assets/js/googlesitekit-events-provider-contact-form-7-********************.js 1.27 kB 0 B
dist/assets/js/googlesitekit-events-provider-content-events-********************.js 3.16 kB 0 B
dist/assets/js/googlesitekit-events-provider-easy-digital-downloads-********************.js 651 B 0 B
dist/assets/js/googlesitekit-events-provider-mailchimp-********************.js 1.24 kB 0 B
dist/assets/js/googlesitekit-events-provider-ninja-forms-********************.js 1.26 kB 0 B
dist/assets/js/googlesitekit-events-provider-optin-monster-********************.js 1.28 kB 0 B
dist/assets/js/googlesitekit-events-provider-popup-maker-********************.js 1.35 kB 0 B
dist/assets/js/googlesitekit-events-provider-woocommerce-********************.js 895 B 0 B
dist/assets/js/googlesitekit-events-provider-wpforms-********************.js 1.3 kB 0 B
dist/assets/js/googlesitekit-feature-discovery-********************.js 26.7 kB 0 B
dist/assets/js/googlesitekit-features-********************.js 91 kB 0 B
dist/assets/js/googlesitekit-features-badge-********************.js 835 B 0 B
dist/assets/js/googlesitekit-i18n-********************.js 4.43 kB 0 B
dist/assets/js/googlesitekit-intents-********************.js 9.33 kB 0 B
dist/assets/js/googlesitekit-key-metrics-setup-********************.js 66.5 kB 0 B
dist/assets/js/googlesitekit-main-dashboard-********************.js 230 kB 0 B
dist/assets/js/googlesitekit-metric-selection-********************.js 68.9 kB 0 B
dist/assets/js/googlesitekit-modules-********************.js 30.9 kB 0 B
dist/assets/js/googlesitekit-modules-ads-********************.js 62.1 kB 0 B
dist/assets/js/googlesitekit-modules-adsense-********************.js 158 kB 0 B
dist/assets/js/googlesitekit-modules-analytics-4-********************.js 319 kB 0 B
dist/assets/js/googlesitekit-modules-pagespeed-insights-********************.js 32.5 kB 0 B
dist/assets/js/googlesitekit-modules-reader-revenue-manager-********************.js 144 kB +41 B (+0.03%)
dist/assets/js/googlesitekit-modules-search-console-********************.js 79.5 kB 0 B
dist/assets/js/googlesitekit-modules-sign-in-with-google-********************.js 41.2 kB 0 B
dist/assets/js/googlesitekit-modules-tagmanager-********************.js 35 kB 0 B
dist/assets/js/googlesitekit-notifications-********************.js 98.8 kB 0 B
dist/assets/js/googlesitekit-polyfills-********************.js 227 B 0 B
dist/assets/js/googlesitekit-settings-********************.js 90.1 kB 0 B
dist/assets/js/googlesitekit-splash-********************.js 74.2 kB 0 B
dist/assets/js/googlesitekit-user-input-********************.js 62.4 kB 0 B
dist/assets/js/googlesitekit-vendor-********************.js 315 kB 0 B
dist/assets/js/googlesitekit-vendor-lazy-pdf-********************.js 24.6 kB 0 B
dist/assets/js/googlesitekit-widgets-********************.js 187 kB 0 B
dist/assets/js/googlesitekit-wp-dashboard-********************.js 47.7 kB 0 B
dist/assets/js/runtime-********************.js 1.98 kB 0 B
dist/assets/js/sign-in-with-google-********************.js 1.35 kB 0 B

compressed-size-action

@JakePT JakePT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks @nfmohit! It looks like there's some potential issues with clearCTAs() and possible conditions where the CTA list can be incorrect or for the wrong publication.

They don't seem likely to occur in practice, but the issues look like they can be avoided if we keep CTAs keyed by publication ID internally in state even though we're not accepting the parameter anymore. That could eliminate the need for separate clearCTAs() and resetCTAs() methods and a strict order in which things are called. It could be even more robust if we return the publicationID that the server used with the response.

I had a 🤖 summarise the cases and solution in more detail:

CTA state can go stale or get stuck when the publication changes

getCTAs() holds a single list with no record of which publication it belongs to. Two calls keep it in sync: clearCTAs() in selectPublication() and resetCTAs() in submitChanges() (settings.js:208-214). Three cases slip through:

  1. The list gets stuck empty. With A saved and its CTAs loaded, select B, then select A again (or cancel the edit). clearCTAs() emptied the list but left the getCTAs resolver marked as finished. The publication ID no longer differs from the saved one, so resetCTAs() never runs, and getCTAs() returns undefined until the page reloads.
  2. The previous publication's CTAs can come back. If getCTAs hadn't resolved before clearCTAs(), the next read fetches from the server. The server answers for the saved publication, so the list holds the previous publication's CTAs, despite what the clearCTAs() docblock says.
  3. A late response can overwrite the list. RESET_CTAS doesn't cancel a request that's already running, so a response that arrives after the reset writes the previous publication's CTAs back into the store.

Suggestion: key the CTAs by saved publication ID internally

Store ctas as Record< publicationID, CTA[] >, filled by an internal selector and resolver keyed by the saved publication ID. Keep getCTAs() without arguments. It should return undefined while the selected publication differs from the saved one, and the saved publication's list otherwise.

This covers all three cases:

  • Selecting the saved publication again shows its list.
  • Each response is stored under the publication it was requested for.
  • After a save, the first read fetches the new publication's CTAs without any manual invalidation.

clearCTAs(), the resetCTAs() call in submitChanges() and the comparison in selectPublication() can then be removed.

Optional: return the publication ID from GET:ctas

A narrow race remains. A save that lands while the request is running means the server answers for the new publication, but the client stores the result under the old one. CTAs only identify their publication through name, so an empty list can't be identified. Returning { publicationID, ctas } from the datapoint closes this gap. Resolving the publication once in Get_CTAs would also stop parse_response() from syncing one publication's CTAs into another's configuredCTAs.

@nfmohit

nfmohit commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks @JakePT! The CTAs are keyed by publication ID again. GET:ctas now returns the publication ID with the list, so the store keys each response by that rather than by the saved setting. That closes all three cases. clearCTAs() and RESET_CTAS are gone, selectPublication() no longer compares publication IDs, and resetCTAs() only invalidates the resolution.

I took the optional suggestion too. An empty list has no CTA names to read the publication from. POST:create-cta keeps its shape, because a created CTA always has a name. Its reducer reads the publication ID from there now, instead of from the settings. That was the same bug in the write path.

getCTAs() returns undefined while the selected publication differs from the saved one. That also covers the transition period you raised in #13979.

@JakePT JakePT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks @nfmohit! It looks like we might still have a couple of gaps. I think the PHP-side one will need to be covered but the other suggestion that would let us get rid of resetCTAs is probably not as important. Let me know what you think.

Comment on lines +85 to +86
$publication = $this->get_connected_publication();

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit I think we still have an issue here where this connected publication may not be the same one that was used in create_request() if the publication had been changed during the request.

It looks like similar issues have been solved elsewhere by returning a closure from create_request(), which is what Batch_Search_Analytics seems to do. If we did that we would just need to avoid calling synchronize() if the publication from create_request() is no longer the connected publication at the time of parse_response().

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Updated, thanks!

Comment on lines +877 to +879
it( 'should clear the CTAs when a different publication is selected', async () => {
// Reading the cleared CTAs starts their resolver, which
// requests the saved publication's CTAs.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit I don't think we're clearing CTAs anymore so this is probably better described as "should not return the CTAs while a different publication is selected"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Renamed, thanks!

Comment on lines +905 to +917
it( 'should keep the CTAs when the connected publication is selected again', async () => {
connectPublicationWithCTAs();

await registry
.dispatch( MODULES_READER_REVENUE_MANAGER )
.selectPublication( {
publicationId: 'publication-1',
onboardingState: 'ONBOARDING_COMPLETE',
} );

expect(
registry.select( MODULES_READER_REVENUE_MANAGER ).getCTAs()
).toEqual( [ cta ] );

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit I think we should also cover that switching to another publication and back should return the first publication's CTAs again.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Added, thanks!

@nfmohit
nfmohit requested a review from JakePT November 15, 2026 18:44

@JakePT JakePT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit It looks like we still have some small gaps, but I wanted to check your feelings on them before I send them back for execution since they're not necessarily blockers and I know we're going long on this already.

The issue is that getPublicationCTAs is treated as resolved for the requested publication ID even if it responds for a different publication than we expected because the saved publication ID was different on the server by the time the request was received. If I save the publication as ABC123, getCTAs() will fetch getPublicationCTAs( 'ABC123' ) but if the saved publication changes to DEF456 before the server builds the request it will respond with the CTAs for DEF456. The latest changes mean that the returned CTAs will be correctly filed against DEF456, which is good, but getPublicationCTAs will still be treated as resolved for 'ABC123'. So if I change the publication back to ABC123 then getCTAs will return undefined and not attempt to fetch the CTAs again until the page is reloaded.

It seems like it's very unlikely that this will cause problems in practice, because it would require another user or tab to be saving settings at the same time, but it's still a flaw with how the datastore is structured. I can't help but feel that the choice to always use the server's saved publication is the problem. Fundamentally what we're fighting is that with this approach we are making requests assuming a certain publication ID but we actually have no idea what publication ID the server is going to respond for, so the datastore needs to account for this uncertainty, which complicates things.

It seems like things would be far cleaner on the JavaScript side if we went the opposite direction to the AC and always required the parameters, and updated the Datapoints to require them. Then we have a far cleaner 1:1 relationship between what we think we're fetching and what we're receiving that avoids all of these issues.

A smaller fix for now would be to call invalidateResolutionForStoreSelector() for getPublicationCTAs inside submitChanges(), just like we currently do with getPublication. It still leaves us the problem of depending on certain call orders etc. that I've been trying to avoid with my feedback, but it solves the practical issue for now in a way that's consistent with other selectors for the time being.

Let me know what you think.

Thanks, and sorry for dragging this out!

@nfmohit nfmohit left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for your feedback, @JakePT!

We went with your suggestion of requiring the parameters. The datapoints now require organizationID and publicationID, and the data store reads them from the settings before each request, so callers still pass nothing. @aaemnnosttv agreed to it, and the acceptance criteria on #13429 are updated.

That closes the case you found. The request says which publication it wants and the server responds for that one, and the resolution is keyed on the same identifiers, so changing the publication and changing back both work without any invalidation.

clearCTAs(), resetCTAs(), the { publicationID, ctas } response shape, the property on the PHP datapoint that recorded which publication a request used, and the guard comparing the selected publication against the saved one are all gone.

Your two test comments from the last round are in, though in ctas.test.ts now, since getCTAs is what they cover.

The branch was reset to develop and force-pushed, so the history is new. I've also folded in publicationsByID, because without it getPublication() writes the publication it fetched into the publications list and the connect-publication step then offers only the connected publication. That and the keyed selectors are why the diff grew to +1614/-1030 from +1012/-934.

Thanks for pushing on it.

@nfmohit
nfmohit requested a review from JakePT November 17, 2026 23:37

@JakePT JakePT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks @nfmohit! Looking good! I just flagged a couple of pretty minor things that need attention.

Also, the QAB is using resolveSelect with getPublication and getCTAs, which don't have resolvers anymore. Can you update the QAB to use select() and cover that they may need to be called twice to see the results of a fetch? Alternatively we could add thin resolvers for each so they can be used with resolveSelect.

switch ( type ) {
case 'RESET_PUBLICATIONS':
state.publications = baseInitialState.publications;
state.publicationsByID = baseInitialState.publicationsByID;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit I don't think we want to wipe publicationsByID here. resetPublications() only invalidates getPublications(), so wiping publicationsByID here means getPublicationByID stays resolved and won't re-fetch.

I think we can simply remove this line as there's no harm in keeping the publications indexed by ID when resetting publications because it's only used for looking up the selected publication, which is reset by refreshPublication().

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Good catch, removed, thanks!

} );
} );

describe( 'getCTAs', () => {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit Can we add an equivalent to the 'should associate a publication fetch error with the request identifiers' test that getPublication() has?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Added, thanks!

$this->synchronization = new CTA_Synchronization( $this->settings );
}


Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit Nit: An extra line break snuck in here.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

🦅 👁️ Removed, thanks!

).toEqual( [ otherCTA ] );
} );

it( 'should not return the CTAs while a different publication is selected', async () => {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit Nit: This wording is a bit misleading. I think what is actually being tested is "should return undefined after selecting a publication that needs to load its CTAs" or similar.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Renamed to should return undefined after selecting a publication whose CTAs are not loaded, thanks!

@nfmohit

nfmohit commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator Author

I've addressed the comments and updated the QAB, thanks @JakePT !

@nfmohit
nfmohit requested a review from JakePT November 18, 2026 10:38

@JakePT JakePT left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nfmohit LGTM. Thanks for putting up with me! ✅ CR.

@hussain-t hussain-t left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks, @nfmohit! LGTM 👍

@hussain-t
hussain-t merged commit 96b54a7 into develop Nov 18, 2026
51 checks passed
@hussain-t
hussain-t deleted the enhancement/#13429-use-connected-publication branch November 18, 2026 16:45
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.

Use the connected publication for Reader Revenue Manager publication and CTA requests

3 participants