HATATATE

Description

HATATATE puts one call-to-action (CTA) on all of your posts without editing each post. A CTA can be a banner, an ad tag or a text link.

What it does

• Create a banner. Register a CTA (HTML, image or text) in the CTA library. Ad code from an affiliate network is kept as you pasted it, as long as the CTA’s author (its post_author) may post unfiltered HTML (the same rule WordPress applies to post content).
• Choose where it appears. Pick a position: before or after the content, after a heading, before the table of contents, in the sidebar, as a modal, or as a fixed bar at the bottom of the screen. You can also click an element on one of your posts to add a custom position.
• It shows on every post. Save the placement once and the CTA appears on all published posts. Change the position later and every post follows.
• Decide it per post. Turn the CTA on or off for a specific post, page, category or tag from the “Per page” tab. Categories and tags are listed inside the plugin, so you do not leave the screen.
• A/B test. Compare two CTAs in the same position. The report uses a Bayesian estimate so you can stop the test when one is clearly better.
• Report. Impressions (50% visible for 1 second) and clicks are counted on your own site and shown per CTA, per position and per day. Your own visits are left out while you are logged in with an account that can write posts.

First run

1. Open “HATATATE” in the admin menu. The Home tab lists what to do next.
2. Create one CTA in the CTA library.
3. Open the placement, choose a position, switch it on, and open one of your posts to confirm.

How the plugin is shaped

• You configure one placement: a list of positions, each with the CTA that goes there. The same placement is used on the whole site. Per-post, per-category and per-tag settings only turn it on or off.
• You can create as many A/B tests as you like. One position runs one test at a time; a second test in the same position waits until you pause or finish the first.

For tag managers and analytics

Every CTA is wrapped in an element with id="hatatate-cta-<ID>" and data-hatatate-cta="<ID>" (the CTA’s post ID). If the same CTA appears twice on one page, the second element gets -2 appended to its id while the data attribute stays the same. Use the data attribute when you set up click triggers in Google Tag Manager.

Requirements and what it does not do

• WordPress 6.0 or later, PHP 7.4 or later.
• The content positions rely on the the_content filter. Themes or page builders that render posts without it will not show in-content CTAs (sidebar, modal and fixed bar still work).
• Positions that depend on a table of contents work with plugins and themes that output a p-toc, toc_container or ez-toc-container element.
• The admin screens are in Japanese.
• A CTA is printed as it was saved only when its author (its post_author) has the unfiltered_html capability, which is the rule WordPress core uses for post content and for the Custom HTML widget. For everyone else the markup goes through wp_kses() with an explicit list of allowed tags, and <script> is dropped. Nobody has the capability when DISALLOW_UNFILTERED_HTML is defined, and on multisite only network administrators have it.

External services

This plugin does not send data about your site or its visitors to any external service. Impressions and clicks are stored in your own database and sent to your own site’s REST API (hatatate/v1/track).

The plugin fetches images from third-party hosts (for example an affiliate network’s image server) only to render a preview snapshot of a CTA’s own content, and only for the image URLs written in that CTA’s own HTML. This can happen in three places, all of them administrator-only:

• When an administrator edits a CTA in the block editor, a snapshot of it is captured automatically.
• On the CTA screen, a CTA whose snapshot is out of date is re-captured automatically when the screen is opened.
• When an administrator starts an A/B test, a snapshot of each side is captured.

Nothing about your site is sent in these requests beyond the image URL being fetched, and requests to private or reserved IP addresses are refused.

Third-party libraries

These libraries are bundled unmodified in admin/lib/ and are all under a GPL-compatible license. The full license text of each one is in admin/lib/LICENSES/, together with the bundled version and where the file was obtained.

• Chart.js 4.5.1 – MIT (admin/lib/LICENSES/chart.js-MIT.txt). The file header reads “Released under the MIT License”.
• Lucide 1.47.0 – ISC (admin/lib/LICENSES/lucide-ISC.txt). The file header reads “@license lucide v1.47.0 – ISC”. The 15 individual SVG icon files in admin/icons/ (all except symbol-menu.svg and symbol-mono.svg, which are this plugin’s own logo) are single icons extracted unmodified from the same Lucide release; the same license file covers them.
• html2canvas 1.4.1 – MIT (admin/lib/LICENSES/html2canvas-MIT.txt). The file header reads “Released under MIT License”. It bundles tslib, which is licensed under 0BSD by Microsoft.
• tailwind.css is not a third-party file as shipped: it is a stylesheet this plugin compiles with Tailwind CSS 3.4.17 (MIT, admin/lib/LICENSES/tailwindcss-MIT.txt). See “Source code” below for how to rebuild it.

Source code

admin/lib/tailwind.css is minified, so the files it is built from are included in the plugin: `admin/lib/src/tailwind-source.css` (the input) and `admin/lib/src/tailwind.config.js` (the build configuration, which also carries the exact command). Running that command with Tailwind CSS 3.4.17 from the plugin root reproduces the shipped file byte for byte. Every other file in the plugin is shipped in its readable form.