Affilun Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
affilun (あふぃるん) helps WordPress site owners manage affiliate product links and display reusable product cards in posts.
The plugin can be used for local WordPress-side affiliate link management without affilun Cloud. Optional affilun Cloud features add managed SaaS workflows such as AI assistance, article draft generation, link health checks, revenue opportunity suggestions, top-selling affiliate candidates, and plan verification.
All local WordPress-side functionality included in this plugin is available without a license key, paid plan, quota, or trial period. Paid or trialing plan checks apply only to optional affilun Cloud SaaS endpoints where processing is performed by affilun Cloud servers.
Core features
- Save and manage product records for affiliate use.
- Render product cards with a Gutenberg block or shortcode.
- Configure provider settings for Amazon, Rakuten Ichiba, Yahoo! Shopping, Mercari, and ASP routing templates.
- Generate standard Amazon detail-page links with a configured Partner Tag when a saved ASIN is available and richer API access is not yet eligible.
- Store link display settings, button labels, templates, and provider-specific rendering options inside WordPress.
- Use optional affilun Cloud features when a Cloud API key and eligible plan are configured.
affilun Cloud boundary
The WordPress plugin distributed here is GPL-licensed software. Local product management, block rendering, saved settings, and basic link generation run inside WordPress.
affilun Cloud is an optional external SaaS. Cloud features may include paid plans, usage limits, plan verification, Stripe Checkout payments, Cloud API key issuance, AI assistance, article draft generation, link health checks, revenue opportunity suggestions, and top-selling affiliate candidates. The plugin can be used without affilun Cloud for local features.
The affilun Cloud server implementation, billing system, hosted processing, and external API relay services are not included in this plugin distribution. Cloud terms, pricing, retention, and deletion details are documented at https://affilun.st/.
External Services
affilun communicates with external services only when the related feature is configured and used. Review each provider’s terms, privacy policy, and affiliate program rules before enabling it. Some linked provider terms and privacy pages are in Japanese because the related service is operated primarily in Japan; this readme provides English summaries of each service purpose and the main data sent.
Amazon Creators API / Amazon Associates
Purpose: Amazon product search, product data retrieval, and Partner Tag link generation.
Data sent when enabled and used: search keywords, ASIN, marketplace, Creators API credentials, and Partner Tag.
Terms: https://affiliate-program.amazon.com/help/operating/agreement
Privacy: https://www.amazon.com/gp/help/customer/display.html?nodeId=468496
Rakuten Ichiba API
Purpose: Rakuten product search, product data retrieval, and affiliate link generation.
Data sent when enabled and used: search keywords, item IDs, Application ID, and Affiliate ID.
Terms: https://webservice.rakuten.co.jp/guide/rule
Privacy: https://privacy.rakuten.co.jp/
Yahoo! Shopping API and ValueCommerce routing data
Purpose: Yahoo! Shopping product search, product data retrieval, and link generation.
Data sent when enabled and used: search keywords, item IDs, Client ID, and related Yahoo! Shopping settings. If a ValueCommerce free-text-link HTML snippet is configured, affilun extracts and stores only the sid / pid values needed for link generation.
Yahoo! JAPAN Developer Network Guidelines: https://developer.yahoo.co.jp/guideline/
LY Corporation Terms: https://www.lycorp.co.jp/ja/company/terms/
LY Corporation Privacy Policy: https://www.lycorp.co.jp/ja/company/privacypolicy/
ValueCommerce Terms: https://www.valuecommerce.ne.jp/st_affiliate/terms.html
ValueCommerce Privacy Policy: https://www.valuecommerce.co.jp/privacy_policy/
Mercari
Purpose: Mercari search or item links with Mercari Ambassador afid when configured.
Data sent when enabled and used: search keywords, Mercari URLs, and afid.
Visitor-side browser requests: product cards may load Mercari Ambassador image URLs on ambassador-system.mercari.com when a saved Mercari product does not already have a primary image URL.
Terms: https://static.jp.mercari.com/tos
Privacy: https://static.jp.mercari.com/privacy
affilun Cloud
Purpose: optional SaaS features such as AI assistance, product keyword normalization, article draft generation, campaign suggestions, revenue opportunity suggestions, top-selling affiliate candidates, link health checks, plan verification, Cloud API key validation, and usage/status retrieval.
Service endpoint: affilun Cloud uses https://api.affilun.st/api/v1. Older saved settings may contain https://cbl.rio.st or https://cbl.rio.st/api/v1; the plugin normalizes those legacy aliases to the affilun Cloud production endpoint.
Data sent when configured and used: site URL, site name, administrator email, Cloud API key, selected plan context, enabled affiliate provider keys, post excerpts or content snippets for the selected operation, product link metadata, review/source URLs, and link health inputs.
The Free state is for connection checks only. Managed Cloud AI, article draft, link health, revenue opportunity, and top-selling affiliate candidate features require a paid or Stripe-trialing plan because those features run on affilun Cloud servers. Top-selling affiliate candidate retrieval does not consume the site’s monthly Cloud usage quota.
Terms: https://affilun.st/cloud-subscription-terms/
Privacy: https://affilun.st/privacy/
Stripe Checkout
Purpose: payment flow for affilun Cloud plans.
Data sent when an administrator starts checkout: email address, site information, selected plan, and checkout session information.
Terms: https://stripe.com/legal/ssa
Privacy: https://stripe.com/privacy
Remote product images
Product cards and admin previews may display product image URLs saved in WordPress. These URLs can point to provider, marketplace, affiliate-network, or CDN domains. When a page containing those images is viewed, the visitor’s browser requests the image from that external domain and the external service may receive request metadata such as IP address, user-agent, and referrer information.
Data stored in WordPress
affilun may store the following data in your WordPress database:
- Provider settings: Amazon credentials, Partner Tag, Rakuten credentials, Yahoo! credentials, Mercari
afid, and enable/disable states. - Product records: product title, provider item ID, ASIN, price, availability, image URLs, product URL, affiliate URL, sync state, and timestamps.
- Display settings: template choice, button labels, link attributes, and rendering options.
- ASP routing settings: Moshimo, ValueCommerce, or other routing URL templates.
- affilun Cloud settings: Cloud API key, site ID, endpoint, selected plan, and Cloud connection status.
- Operational data: logs, sync jobs, audit events, link health results, revenue opportunity statuses, locally cached top-selling affiliate candidates, local click events, and aggregated click/impression rollups.
- Local click metadata: provider, button key, target URL hash, product ID, post ID, variant, user-agent hash, referrer host, timestamp, and daily aggregated counts.
API keys and affiliate identifiers are stored in the WordPress database and are managed by users with administrator permissions. They are not printed on public pages.
ASP Routing
Yahoo! Shopping affiliate attribution is configured in the Yahoo! Shopping provider settings with the Yahoo Developer Client ID and a ValueCommerce free-text-link HTML snippet. affilun extracts and stores only the sid / pid values from that snippet.
affilun also supports optional advanced ASP routing templates for custom ASP or migration flows. Templates may use placeholders such as {url}, {encoded_url}, {provider}, and {product_id}.
When ASP routing is enabled, a product button URL may be transformed into the configured intermediary ASP URL. The site operator is responsible for ensuring that each template complies with the relevant ASP terms and tracking requirements.
Uninstall
When the plugin is deleted from the WordPress admin, uninstall.php runs the plugin’s uninstall routine.
The current policy removes secret-bearing and operational options, including provider credentials, affilun Cloud API keys, Cloud connection settings, local click option aggregates, cron cursors, worker IDs, and scheduled affilun cron hooks.
Custom product, log, audit, sync, link-health, analytics, and click-rollup tables are preserved unless a future explicit purge-on-uninstall setting is introduced. Back up any product data or settings you need before deleting the plugin.
Screenshots
No screenshots provided
