Frequently asked questions before buying Afftrix.

Afftrix is primarily sold as commercial source code, managed private hosting, or custom delivery. The website uses SaaS-style clarity, but the buying model is built around ownership, private deployment, and scoped services.

Afftrix is built for affiliate networks, CPA networks, performance agencies, lead generation teams, WooCommerce merchants, and technical teams that want more control over tracking, offers, postbacks, payouts, reports, and deployment.

The Afftrix Source Code License is available through the current website offer at $599 one-time and includes one complimentary standard installation, 1 year standard technical support, and 1 year product updates. The Standard Source License price is $799.

Yes. The demo path is designed for buyers who want to review admin, offer, tracking, postback, payout, report, and integration workflows before purchasing source code or requesting services.

Start with the dashboard, offer list, conversion evidence, postback debugging, payments, reports, WooCommerce connector, anti-spy or link protection concepts, conversion notifications, and source package scope. The goal is to confirm that Afftrix matches real operating work, not only a marketing feature list.

No. The $599 source code license covers the commercial source-code package and one standard installation. Managed hosting, migration, third-party integrations, advanced installation, renewal support, and custom development are scoped separately.

Yes. The Source Code License is available for teams that want to own the codebase, database path, deployment model, and future customization. Hosting, migration, advanced installation, and custom work remain optional.

The source code license includes the Afftrix source code, one complimentary standard installation, commercial use for one business, one production installation, installation documentation, 1 year standard technical support, and 1 year product updates.

Yes, source-code ownership is intended for teams that need to inspect, modify, and extend the platform. Custom changes made by your team should be managed carefully because they can affect future update and support work.

The source code license is positioned for one business and one production installation. Multi-business, reseller, agency, or multi-environment use should be discussed before purchase so the license boundary is clear.

A source-code delivery normally includes the application code and the database migration or schema path needed to run the product. Exact handoff details should be confirmed before purchase.

No. Afftrix is positioned as a commercial affiliate infrastructure product with source-code licensing, private deployment, product updates, support, and optional managed or custom delivery.

The included standard installation covers one clean supported server or agreed environment, basic application deployment, environment and database configuration, storage permission checks, queue and scheduler checks, and admin login verification.

Prepare server or hosting access, domain and DNS plan, SSL approach, database credentials, mail settings, queue worker access, and the initial admin account details. A clean environment helps the included installation stay within standard scope.

Server purchase, cloud bills, control panel licenses, long-term monitoring, migration, third-party API work, custom modules, repeated installs, complex hosting-panel troubleshooting, and advanced infrastructure repair are not included in the standard installation.

If the server is not ready, the standard installation may need to wait until access, DNS, SSL, database, queue, mail, storage, and permissions are prepared. Complex server repair, repeated attempts, or unsuitable hosting environments can be treated as advanced installation scope.

Shared hosting is usually not ideal for an affiliate tracking platform because queues, scheduled jobs, storage permissions, redirects, and performance controls matter. A VPS, cloud server, or dedicated private environment is a safer path.

Yes. Technical teams can self-host Afftrix and use the documentation as their starting point. The included standard installation is there to remove the first setup barrier for buyers who want a working private system quickly.

Additional environments can be scoped separately. The source code license includes one production installation, so staging, testing, repeated installs, or advanced deployment workflows should be discussed as separate scope.

Yes. Afftrix includes Storage & CDN settings for public media such as Media Library uploads, platform logo, favicon, login background, offer thumbnails, offer creatives or previews, email editor images, and payment method icons. Supported storage options include local storage, Amazon S3, Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2, MinIO, Alibaba Cloud OSS, Tencent Cloud COS, Qiniu Kodo, and custom S3-compatible storage.

Yes. Managed Private Hosting starts from $299/month plus infrastructure. The $299/month plan is the managed hosting care fee. Server, storage, CDN, mail, backups, bandwidth, and high-traffic infrastructure are billed separately or scoped at cost.

No. Managed hosting is a private delivery path for your Afftrix instance. It is closer to a dedicated private platform than a shared SaaS account, with scope defined around your infrastructure and operating needs.

Managed private hosting can include server setup, SSL, queues, Redis, backups, basic monitoring, update assistance, and technical support. Cloud server, storage, CDN, traffic scale, and special SLA requirements are scoped separately unless they are included in a written hosting plan.

Usually yes, managed hosting is a service around the Afftrix platform. If you want hosting without owning the source license, that commercial arrangement should be confirmed before purchase.

That can be planned if your license and deployment scope allow it. The migration should cover files, database, domains, SSL, queues, storage, mail, and tracking paths.

Self-hosted buyers pay their own server costs. For Managed Private Hosting, the public $299/month price is the hosting care fee; cloud server, storage, CDN, mail, backup, bandwidth, and traffic-dependent resources are billed separately or scoped at cost before launch.

Yes. Afftrix supports core affiliate tracking workflows such as offers, tracking links, clicks, conversions, postbacks, sub IDs, reports, payouts, affiliates, advertisers, and partner portals.

Yes. Smartlink workflows are part of the platform, including offer pools, routing logic, traffic context, and fallback behavior depending on configuration.

Offer Health and automation workflows are designed to help operators review broken destinations, geo issues, payout changes, duplicate records, stale offers, and upstream supply quality.

Yes. Postback debugging is a core proof area: operators can review click IDs, advertiser responses, callback attempts, failed postbacks, conversion evidence, and related parameters.

Yes. Afftrix includes conversion notification workflows for teams that want real-time or digest updates when conversion events are created, reviewed, approved, rejected, or need attention. Delivery can use in-app notifications, email, Telegram, or webhook channels depending on configuration.

Notification rules can be scoped around the events that matter to your team, such as new conversions, approved conversions, rejected conversions, offer health changes, payout review, failed postbacks, fraud signals, or daily summaries. Sensitive data and channel behavior should be confirmed during setup.

Afftrix includes protected redirect concepts, rule-based traffic checks, allow or block lists, suspicious probe signals, and evidence logs. Deeper anti-spy workflows should be evaluated in the demo and scoped according to deployment needs.

Yes. Afftrix includes Automation Rules for patterns such as one affiliate sending high click volume to one offer with zero valid conversions inside a configured lookback window. The rule can log the signal, create an AM task, mark the case for manual review, pause an offer, or disable that affiliate access to that offer when the action is configured and enabled. This keeps the workflow auditable instead of silently blocking traffic without evidence.

Afftrix is designed with protected redirect and anti-spy concepts so networks can reduce upstream link exposure while still giving operators the evidence they need. Exact behavior depends on configuration, traffic source, and redirect rules.

Yes. Afftrix provides an embeddable affiliate application form that can load inside your own website, pass landing-page parameters, auto-resize after loading, and follow simple visual settings such as theme, accent color, logo visibility, and locale.

Yes. Afftrix includes a WordPress and WooCommerce connector path for click ID capture, coupon attribution, orders, refunds, product context, and conversion callbacks.

Shopify should be treated as custom or roadmap until a complete Shopify app is delivered. If Shopify is required, it should be scoped as integration work before purchase.

Afftrix includes payment workflows for reviewing payable balances, creating payment records, tracking paid lists, and connecting finance work to conversion and payout evidence.

Yes. Batch payment workflows are part of the finance control story, helping operators create payment bills from approved unpaid balances and selected payable records.

Yes. Single payment workflows support manual corrections, special payouts, selected periods, or individual affiliate payout handling when batch payment is not the right path.

Afftrix includes invoice and payment record concepts, including PDF export paths and payment item evidence. Exact invoice formatting or local tax requirements may require custom scope.

Yes. Upstream reconciliation is an important product area. It can help compare upstream statements with internal conversions, revenue, payout, status, missing records, and mismatches.

Yes. Profit Guard and finance review workflows help teams check margin, revenue, payout, reversals, refunds, status changes, and suspicious records before payout decisions.

Yes, but migration must be scoped after export review. The key work is field mapping, legacy IDs, domains, postbacks, payout states, historical data quality, and cutover planning.

That depends on your current domains, redirect structure, URL format, and export access. A migration plan should identify which links can be preserved and which need a controlled switch.

Historical import depends on export quality, table structure, IDs, volume, and whether the data is needed for reporting, reconciliation, or partner access. This should be reviewed before quoting migration.

Yes, if the source platform can export the records in a usable format. The migration should review users, roles, approvals, passwords, postbacks, payment details, and access rules.

Timeline depends on export quality, custom fields, data volume, current platform behavior, tracking domains, postback complexity, and whether new workflows are added during the move.

No serious migration should be promised as fully automatic before data review. Some records can be imported directly, while IDs, links, statuses, payout rules, and custom fields often need mapping and validation.

Yes. UI changes can be scoped as custom development. This can include dashboards, reports, fields, menus, branding, portals, and workflow-specific screens.

Yes. Custom payout logic, approval rules, caps, commission models, hold behavior, and finance checks can be scoped after reviewing your commercial model.

Yes, advertiser or offer-source API work can be scoped. The quote depends on API quality, authentication, field mapping, sync frequency, error handling, and review requirements.

Payment gateway work should be scoped separately. Many affiliate networks still use manual, bank, crypto, or export-based payout processes, so gateway needs should be confirmed before development.

Yes. Custom reports can be built around your dimensions, metrics, filters, exports, and user roles. The scope depends on data availability and whether the report is for admin, affiliate, advertiser, or finance users.

Notification integrations can be scoped based on the event type, delivery channel, formatting, retry behavior, and whether sensitive data must be redacted.

Yes. Afftrix can be delivered as a Custom Enterprise project for companies that need a dedicated affiliate system shaped around their own business model. This can include private deployment, branded portals, custom modules, payout rules, approval workflows, integrations, reports, permissions, and handoff requirements. The exact scope is confirmed after requirements review so the delivery plan, timeline, and quote are clear.

Standard support covers product usage guidance, setup questions, update guidance, and product-defect assistance for the delivered Afftrix codebase. It does not automatically include custom development, migration, hosting operations, or third-party integration work.

It means buyers receive access to product updates during the first year. Applying updates to a customized or self-hosted system should be handled carefully, especially if your team modifies core code.

Support and updates can be renewed. If you do not renew, your existing installed system can continue according to your license, but new updates and support assistance may no longer be included.

They can. If your team or a third party modifies core behavior, support may need to separate product defects from custom-code issues. Large custom changes should be documented.

Priority incident response or emergency support should be scoped separately, especially for managed hosting, high-traffic networks, or time-sensitive payout and tracking operations.

Yes. Feature requests can be reviewed as roadmap ideas or custom development. If the feature is specific to your workflow and needed quickly, custom scope is usually the faster path.

With private deployment, tracking domains, database access, backups, reporting retention, and workflow logic can be scoped around your operating model.

Yes. Staff roles, employee access, affiliate and advertiser portals, and permission boundaries are important product areas for private network operations.

Afftrix includes audit and activity concepts for system changes, sensitive actions, login behavior, and operational review. Exact retention and compliance needs should be scoped.

Sensitive data handling depends on deployment, roles, permissions, logging, exports, notifications, and custom workflows. Private deployment gives more room to define controls around your business requirements.

Compliance depends on how you deploy, configure, operate, and process data. Afftrix can support privacy-aware workflows, but your legal and compliance team should review your actual use case.

Self-hosted buyers are responsible for their own backup strategy unless backup work is separately scoped. Managed hosting can include backup coverage depending on the agreed service plan.

Send your current platform, monthly clicks and conversions, number of offers and partners, hosting preference, migration needs, required integrations, and whether you want source code, managed hosting, or custom delivery.

The website stores the request as a lead and can notify the admin through configured channels. If email or messaging settings are not available, the request should still be saved for review.

Yes. Basic validation and rate limiting are useful first steps. If public traffic grows, CAPTCHA, stricter throttling, IP rules, or manual review can be added.

The purchase link can point to your dedicated buying page when it is ready. Until then, the website can route buyers to contact, pricing, or source-code information.

Yes. The website already separates demo, purchase, and tutorial destinations so final external links can be connected when those pages are ready, without rewriting the commercial story.

Choose source code if you have technical capacity and want ownership. Choose managed hosting if you want server work handled. Choose custom delivery if migration, integrations, special workflows, or UI changes are central to the project.

Inspect the live demo, review pricing and source-code scope, then contact Afftrix with your current platform, traffic scale, migration needs, and preferred deployment model.