affilun

affilun is a WordPress plugin for managing affiliate product links used by Japanese websites. It stores products from Amazon Associates, Rakuten Ichiba, Yahoo! Shopping, Mercari, and other configured routes, then displays them as reusable product cards in posts.

The local plugin features do not require a license key, trial, paid plan, or usage quota. Product storage, product cards, provider settings, and basic affiliate-link generation run within WordPress.

You can optionally connect affilun Cloud for managed AI assistance, article drafting, link-health checks, campaign suggestions, affiliate-product suggestions, and plan information. These optional features are external SaaS services processed by affilun Cloud.

Main features

• Store and manage affiliate product records in WordPress.

• Display product cards with a Gutenberg block or shortcode.

• Configure Amazon, Rakuten Ichiba, Yahoo! Shopping, Mercari, and ASP routing templates.

• Generate a standard Amazon product-detail URL with the configured Partner Tag when an ASIN is stored.

• Fetch discounted Amazon physical products daily and display priority brands before selected categories with a configurable shortcode.

• Store button labels, display templates, link attributes, and provider display settings in WordPress.

• Use optional Cloud features only when an affilun Cloud API key and eligible plan are configured.

Amazon discount priority brands

[affilun_amazon_discounts brands="Anker,Dyson" categories="Electronics" per_category="4"] displays cached priority-brand groups before category groups.

Brand groups require a matching brand in Amazon’s product metadata; a search hit or a brand name in the product title is not enough. Matching ignores letter case and repeated whitespace and accepts parenthesized brand aliases such as Anker(アンカー). Different or missing brands are excluded during synchronization and when reading existing snapshots, before the display limit is applied.

Category groups remain independent and may include other brands.

After updating, previously stored mismatches are hidden from brand groups without waiting for the next synchronization. The next successful daily or manual synchronization replaces the stored group. If a page cache is enabled, purge it to refresh previously rendered HTML.

affilun Cloud boundary

org is a GPL-licensed WordPress plugin. Local product management, product-card rendering, saved settings, and basic link generation run within WordPress.

affilun Cloud is an optional external SaaS. Cloud features may include paid plans, usage limits, plan checks, Stripe Checkout, Cloud API-key issuance, AI assistance, article drafting, link-health checks, campaign suggestions, and affiliate-product suggestions. Local plugin features remain available without affilun Cloud.

The affilun Cloud server implementation, billing system, hosted processing, and external API relay services are not included in this plugin package. st/ for Cloud terms, pricing, data retention, and deletion information.

External Services

affilun communicates with an external service only when the related feature is configured and used. Review each provider’s terms, privacy policy, and affiliate-program rules before enabling it.

Amazon Creators API / Amazon Associates

Purpose: Amazon product search, product-data retrieval, daily brand- and category-based discount discovery, and Partner Tag link generation.

Data sent when enabled: search terms and priority-brand filters when applicable, ASINs, discount categories and thresholds, marketplace, Creators API credentials, and Partner Tag.

com/help/operating/agreement

nodeId=468496

Rakuten Ichiba API

Purpose: Rakuten Ichiba product search, product-data retrieval, and affiliate-link generation.

Data sent when enabled: search terms, item IDs, Application ID, Access Key, Affiliate ID, and the WordPress site’s Origin. The Access Key is sent in an HTTP header rather than the URL.

jp/guide/rule

jp/

Yahoo! Shopping API and ValueCommerce routing

Purpose: Yahoo! Shopping product search, product-data retrieval, and link generation.

Data sent when enabled: search terms, 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 and pid values needed for link generation.

Yahoo! jp/guideline/

jp/en/company/terms/

jp/en/company/privacypolicy/

html

jp/privacy_policy/

Mercari

Purpose: Generate Mercari search or product links containing a configured Mercari Ambassador afid.

Data sent when enabled: search terms, Mercari URLs, and afid.

com.

com/tos

com/privacy

affilun Cloud

Purpose: optional managed AI assistance, product-keyword normalization, article drafting, campaign suggestions, revenue-opportunity suggestions, affiliate-product suggestions, link-health checks, plan checks, Cloud API-key validation, and usage reporting.

st/api/v1. st are normalized to the production affilun Cloud endpoint.

Data sent when configured and used: site URL, site name, administrator email address, Cloud API key, plan context, enabled provider keys, selected Amazon category, post excerpts or content needed for the selected operation, product-link metadata, review-source URLs, and link-health inputs.

The Free state is for connection checks. Managed Cloud features may require a paid plan or Stripe trial because processing occurs on affilun Cloud servers.

st/cloud-subscription-terms/

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.

com/legal/ssa

com/privacy

External product images

Product cards and administration previews may display product-image URLs saved in WordPress. These URLs may point to provider, marketplace, affiliate-network, or CDN domains. When a page containing an external image is viewed, the visitor’s browser sends a request to that domain, which may receive the visitor’s IP address, user agent, referrer, and other request information.

Data stored in WordPress

affilun may store:

• Provider settings, including Amazon credentials and Partner Tag, Rakuten credentials, Yahoo! credentials, Mercari afid, and enabled states.

• Product records, including title, provider item ID, ASIN, price, availability, image URL, product URL, affiliate URL, synchronization state, and timestamps.

• Daily Amazon discount snapshots stored separately from manually managed affiliate products.

• Priority-brand names configured for Amazon discount synchronization and shortcode display.

• Display settings, including templates, button labels, link attributes, and display options.

• ASP routing settings and URL templates.

• affilun Cloud settings, including Cloud API key, site ID, endpoint, selected plan, and connection state.

• Operational data, including logs, sync jobs, audit events, link-health results, opportunity states, cached affiliate suggestions, local click events, and daily click/view aggregates.

API keys and affiliate identifiers are stored in the WordPress database and managed by administrators. They are not rendered on public pages.

ASP Routing

Yahoo! Shopping affiliate tracking is configured with a Yahoo Developer Client ID and a ValueCommerce free-text-link HTML snippet. affilun extracts and stores only the sid and pid values needed for link generation.

Advanced routing templates can also be configured for custom ASPs or migrations. Templates may use placeholders such as {url}, {encoded_url}, {provider}, and {product_id}.

When routing is enabled, a product-button URL may be transformed into the configured intermediary ASP URL. The site operator is responsible for confirming that each template complies with the relevant ASP rules and tracking requirements.

Uninstall

php.

The current uninstall policy removes secrets and operational options, including provider credentials, the affilun Cloud API key and connection settings, local click aggregate options, cron cursors, worker IDs, and scheduled affilun cron hooks.

Custom tables containing products, logs, audits, synchronization data, link-health data, analytics, and click aggregates are retained unless an explicit data-removal option is introduced in a future release. Back up required data before deleting the plugin.