Remove sending is_singular_post parameter

[timur987]

Related to ADS-295 and 187107-ghe-Automattic/wpcom

Proposed changes:

• Remove sending is_singular_post to highlight the current URL is suitable for inline ads (because

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Testing instructions:

If you need to know more about how to get Jetpack tests site up and running, please take a look at 184618-ghe-Automattic/wpcom. Also, please don't forget to make your site launched and be public (use WP Admin > General > Reading section).

• Sandbox your WPCOM with the branch for accompanying PR (187107-ghe-Automattic/wpcom)
• Open Jetpack Beta Tester (e.g. https://timurjetpacktest.wpcomstaging.com/wp-admin/admin.php?page=jetpack-beta for my test Jetpack site);
• Activate remove/sending-is-singular-post branch for Jetpack;
• Prepare a tab for testing, open Dev Tools > Network;
• Filter all Network requests by "adflow";
• Open your test post or a page (in my case it's https://timurjetpacktest.wpcomstaging.com/2025/06/16/discover-northern-cardinal/?wordads-logging=true&ad_dev=true);
• Make sure that the request does not contain is_singular_post query parameter, in my case the request is

• Make sure that you can see development ads (with the use of ?ad_dev=true)

• And, the most important, inline ads:

Troubleshooting

In the case you don't see ads due to af.pubmine.com/?api_version=2 returns 204 (the ad slot considered as Brand Unsafe), just switch to local AdFlow in WATL and run AdFlow locally.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the remove/sending-is-singular-post branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack remove/sending-is-singular-post

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• 🔴 Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

## Does this pull request change what data or activity we track or use?

My PR adds *x* and *y*.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: August 5, 2025
  • Code freeze: August 4, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/modules/wordads/php/class-wordads-smart.php	0/88 (0.00%)	0.00%	-1 💚

Full summary · PHP report · JS report

[sbarbosa]

The code looks good.

I tested it and do not see the is_singular_post in the adflow/conf/ call. I also verified it by checking the stable version of Jetpack, and we sent it in that one.

I can also see the debug ad placement, including the inline ads.

[therocket-gr]

tested in localhost with the other branch in my sandbox. works as described and code changes LGTM