外掛標籤
開發者團隊
原文外掛簡介
“Well, Actually…” turns your archive of blog posts into a Tinder-style knowledge game. Mark any post with a one-line “Swipe Statement” and a True/False/Debatable verdict, and visitors at your chosen URL (default /swipe) will see it full screen. They swipe right to agree, left to disagree, or up if they’re not sure. Get it wrong — or aren’t sure — and they’ll see the post that explains why.
Progress is tracked locally for anonymous visitors and synced to their account when logged in, so their score follows them.
The swipe page also includes configurable social sharing metadata. Pick its preview title, description, and image under Settings → “Well, Actually…” so links shared on social networks and messaging apps look intentional.
Because the focused swipe template does not inherit analytics from your theme, it can optionally add a Google tag, Meta Pixel, or LinkedIn Insight Tag directly. All three are off until you enter an ID.
External Services
By default, activating the plugin and playing the public swipe game do not contact an external service. Administrators can optionally configure page-view tags for Google, Meta, or LinkedIn under Settings → “Well, Actually…” → Analytics and advertising. Blank fields load nothing.
Optional tracking services
When configured, the selected tags load when a visitor opens the swipe page. Like ordinary web requests, the providers can receive the page URL, IP address, browser information, and referrer, and may set cookies or similar identifiers. The plugin sends only each provider’s standard page-view signal: it does not send swipe answers, scores, post content, WordPress accounts, or custom events.
Google tag: loads https://www.googletagmanager.com/gtag/js and sends the standard Google tag page-view configuration. Google Analytics Terms and Google Privacy Policy.
Meta Pixel: loads https://connect.facebook.net/en_US/fbevents.js, sends a PageView event, and provides the standard no-script fallback at https://www.facebook.com/tr. Meta Business Tools Terms and Meta Privacy Policy.
LinkedIn Insight Tag: loads https://snap.licdn.com/li.lms-analytics/insight.min.js and provides the standard no-script fallback at https://px.ads.linkedin.com/collect/. LinkedIn Ads Agreement and LinkedIn Privacy Policy.
Site owners are responsible for configuring consent tools and privacy disclosures appropriate for their visitors. Developers can return false from the wellactually_tracking_allowed filter to suppress every configured tag for a request.
Optional AI drafting service
The optional “Draft with AI” feature sends post content to an external AI service.
What is sent: the post’s title, plus either its manual excerpt (if one exists) or up to the first 3,000 characters of the post’s body as plain text (HTML and code blocks stripped). No reader data, user accounts, or site credentials are ever sent.
When it is sent: post content is sent only when a logged-in administrator or editor clicks “Draft with AI” on the Swipe Setup screen, and only for the posts queued in that run — nothing automatic, nothing on a schedule. Separately, when an administrator opens this plugin’s settings or Swipe Setup screens, the plugin asks the selected provider plugin whether it’s configured; depending on the provider, that check may involve a round-trip to the provider’s API (no post content is included in it, and the result is cached briefly).
Where it goes: to the AI provider you select and configure. This plugin does not bundle or default to any vendor — it talks to whatever provider plugin the site administrator has registered with the WordPress AI client (see the WordPress AI documentation) and chosen in Settings → Well, Actually… Examples include Nano-GPT or any other AI-client-compatible provider. You will generally need your own account and API key with that provider.
Terms and privacy: because the destination is your chosen provider, its terms of service and privacy policy govern the transfer — consult the documentation of the provider plugin you install (for example, Nano-GPT’s terms and privacy policy if you choose Nano-GPT). Review them before drafting content you consider sensitive.
What comes back: a suggested swipe statement and verdict, stored as a draft suggestion on the post. Nothing goes live until a human reviews and saves it.
