# Influblog public documentation > Combined, curated English documentation for the Influblog creator-marketing platform. Canonical index: https://influblog.com/llms.txt --- Source: https://influblog.com/ai/platform-overview.md ## Influblog platform overview Influblog is a creator-marketing software platform, not an influencer agency. It is a role-based platform for managing creator relationships, campaigns, applications, collaboration tasks, content evidence, contracts, and attributed commerce. It serves brands, creators, agencies, and Influblog administrators through separate product surfaces. Influblog is not a public creator directory where brands freely scrape or contact creators. Its marketplace model is campaign-first: a brand publishes a campaign, eligible creators apply, and the brand reviews applications. Influblog 2.0 is also not an end-customer product marketplace. Influblog 1.0 previously exposed WordPress, WooCommerce, and Dokan storefront pages, but those retail catalog, product, seller, cart, and checkout URLs are retired historical surfaces and are not current Influblog capabilities. ### Availability **Status:** LIVE core platform with BETA modules. Provider integrations, marketplace settlement, and country-specific legal availability can be more limited than the core campaign and task workflows. See [Product status](https://influblog.com/ai/product-status.md) before describing a capability as generally available. ### Audiences - **Brands** manage their own creator relationships, websites, products, campaigns, applications, collaboration tasks, and reusable content proof. - **Creators** manage their account, campaign applications, accepted tasks, submissions, documents, and eligible affiliate or product-test activity. - **Agencies** have a separate role and workspace. Broader managed-brand and represented-creator operations remain in staged rollout. - **Influblog administrators** operate internal review, support, legal, commerce, and audit workflows. Administrative data is not public documentation. ### Product boundaries Private brand data stays separate from Influblog network workflows. A brand's company can operate more than one website, while campaigns, products, commerce connections, affiliate activity, and related records remain scoped to the selected website. Role and tenant checks are enforced on the server. A visible page or a URL is not itself proof that a user is allowed to read or change its data. Three similarly named concepts must remain distinct: - the **Influblog campaign marketplace** is campaign-first discovery where eligible creators review opportunities and apply; - **campaigns for external marketplace shops** let a brand request eligible creator work or honest evidence for its own third-party marketplace presence; - **Brand products and shop integrations** are private, website-scoped records used for campaign selection, coupons, fulfillment, Affiliate attribution, and reporting. None of these concepts is an Influblog-operated retail storefront for end-customer product browsing, carts, or checkout. Historical Influblog 1.0 shop URLs return `410 Gone` and must not be interpreted as current product documentation. ### Public entry points - [Brands](https://influblog.com/brands) - [Creators](https://influblog.com/creators) - [Agencies](https://influblog.com/agencies) - [Pricing](https://influblog.com/pricing) - [Privacy](https://influblog.com/privacy) - [Contact](https://influblog.com/contact) ### AI discovery The public AI documentation explains the product without exposing user or tenant data. `llms.txt` is an emerging discovery convention and does not guarantee that an AI system will retrieve, trust, or fully understand this documentation. --- Source: https://influblog.com/ai/system-map.md ## Influblog system map Influblog is creator-marketing software, not an influencer agency. It is a role-based creator-marketing operating system that connects creator recruitment, campaign discovery, applications, agreements, operational tasks, content proof, brand review, reusable media, commerce automation, affiliate attribution, and reporting without turning private creator or tenant data into a public directory. This document explains how the whole platform fits together. Detailed status always comes from [Product status](https://influblog.com/ai/product-status.md). ### Availability **Status:** LIVE as the system and tenancy map. Individual modules can be LIVE, BETA, or PLANNED. A documented workflow never means that every provider, country, role, or account has every step enabled. ### Roles and product surfaces - **Public platform:** explains Influblog, exposes approved campaign and creator-program entry points, and lets a visitor start the relevant registration or login flow. Public pages do not expose private applications, creator contacts, contracts, content, or analytics. - **Brand workspace:** manages the company, brand-area capacity, websites, locations, apps, marketplace shops, creator relationships, campaigns, applications, tasks, content, integrations, Affiliate rules, and reporting. - **Creator workspace:** manages the creator's identity, profile, campaign discovery, applications, accepted work, tasks, proof, content delivery, documents, Affiliate activity, product tests, and eligible financial state. - **Agency workspace:** is a separate, role-gated BETA surface for brand agencies, talent agencies, and hybrid agencies. Access depends on explicit brand-management or creator-representation relationships; an agency account is not platform-wide access. - **Admin workspace:** is an internal, audited operational surface for support, legal-template governance, integration health, attribution exceptions, and other authorized platform operations. It is not a public data source. A user account and a product role are related but not interchangeable. The server resolves the acting role, authorized relationships, and tenant for every protected read or change. ### Tenant and relationship model - A **Brand** is the legal company root. - A **Brand Area** is package-backed operating capacity. Package count follows the greatest active count among websites, mobile apps, marketplace shops, and physical locations, with at least 1 package. - A **Brand Website** is the operational commerce tenant. Campaigns, products, shop integrations, coupons, Affiliate activity, and related attribution must stay on the selected website. - A **Brand creator relationship** belongs to the company-level creator pool. It can preserve the relationship across the company's websites without merging website-specific commerce data. - A **Creator** has one durable Influblog identity. Provider accounts, brand pool entries, applications, and agency representation attach to that identity under their own consent and access rules. - An **Agency relationship** grants only its documented brand or creator scope. Revoking one relationship must not expose or delete unrelated tenant data. One brand cannot read another brand's pool, applications, campaigns, content, orders, or analytics. One website connection cannot silently act on another website, even when both websites belong to the same company. ### Public discovery, showcases, and creator intake Influblog uses campaign-first discovery rather than an open creator directory. A brand can expose campaigns through its campaign showcase or an approved network listing. A visitor can inspect the public offer, but must use an Influblog creator account and pass the campaign's eligibility checks before applying. A brand can also publish a creator-program landing page and share it by link, embed, or QR code where the current integration supports that placement. Existing and new creators use the same verified Influblog identity flow. A successful, consented application can create exactly one relationship in that brand's creator pool; it does not make the creator public to other brands. The publicly communicated network floor is **2,800+ registered creators**. It is not the number of creators eligible for every country, niche, campaign, or Affiliate offer. ### Marketplace and product boundary Influblog 2.0 is creator-marketing software, not an end-customer product marketplace. The current **Influblog Marketplace** is campaign-first: eligible creators discover campaign opportunities and apply. A campaign may target a brand's store on an external marketplace, but Influblog does not become that marketplace or sell the store's products to consumers. Products and shop integrations inside the Brand workspace remain private, website-scoped inputs for campaigns, coupons, fulfillment, Affiliate attribution, and reporting; they are not a public Influblog retail catalog. Influblog 1.0 product, product-category, seller/shop, cart, checkout, feed, sitemap, and WordPress storefront URLs are retired historical surfaces. They return `410 Gone`, are absent from the current sitemap and public AI links, and must never be treated as Influblog 2.0 functionality. ### Campaign model Campaign configuration can describe: - e-commerce product seeding, barter, paid work, or product-plus-payment; - cafes, restaurants, stores, clinics, childcare, events, and other physical locations; - mobile apps and SaaS products; - marketplace-store review or content campaigns; - private campaigns, reusable invitation links, brand showcases, and network marketplace publication; - social deliverables, source files, website or marketplace proof, location visits, app proof, and honest review proof; - capacity, dates, eligibility, geography, platforms, content formats, compensation, shipping responsibility, usage rights, and disclosure needs. Google and Trustpilot remain possible review destinations or proof targets where the campaign configuration calls for them. Influblog requires honest experience-based proof and creator action; it does not promise an official Google or Trustpilot integration, provider approval, automatic native verification, or a positive rating. Saving a campaign does not publish it. Publishing does not create an application. An application is not acceptance. Acceptance is not task completion. A content upload is not brand approval. ### End-to-end collaboration lifecycle 1. The brand selects the correct website, location, app, or marketplace target and prepares campaign facts. 2. The campaign stays private, is shared to a controlled audience, or enters the reviewed marketplace/showcase flow. 3. The creator signs in or registers, reviews the offer, and applies. 4. The brand accepts, waitlists, or declines the application. 5. When required and legally available, Influblog freezes the presented agreement version, commercial facts, usage rights, and acceptance evidence. 6. The system creates the applicable operational work: shipment or access preparation, publication, content upload, review proof, or another requirement. 7. The creator receives the product or access, tracks the requirement, and submits the required links, media, screenshots, or source files. 8. The brand reviews each requirement independently, requests a correction where allowed, approves the result, and closes the work. 9. Authorized content remains available to the brand according to the accepted usage rights, retention rules, and campaign relationship. Storage does not make the content public or grant rights beyond the agreement. The task center is the operational record of these steps. Notifications and provider events can advance eligible states, but they do not bypass a required human decision or a missing provider fact. ### Commerce, coupon, and Affiliate lifecycle Commerce remains attached to one Brand Website: Shopify is BETA and ikas is BETA under their documented installation, permission, provider, and rollout prerequisites. WooCommerce, Ticimax, Wix, and other provider adapters remain PLANNED unless a later status register explicitly promotes them. Provider names describe an adapter target, not guaranteed approval or universal capability. 1. The brand authorizes a supported shop integration. 2. Influblog normalizes eligible products, variants, media, price, stock, and provider state while preserving a frozen campaign product snapshot. 3. The brand configures a follower Affiliate rule, a coupon-for-content product test, or a product campaign. 4. A creator receives a website-specific link or coupon. Creating a link, opening a share sheet, recording a click, receiving an order, and receiving a paid order are different events. 5. A paid, matched product-test order can activate the configured content and review tasks. An Affiliate follower coupon does not create the same content obligation. 6. Where supported and explicitly enabled, Influblog prepares a provider-side PR fulfillment reference and projects later shipment and tracking state into Brand and Creator tasks. Unsupported provider behavior stays manual or disabled. 7. Paid-order attribution can connect the website, creator, link, coupon, product, order, and commission rule. Conflicting or incomplete signals remain unmatched or require review instead of awarding two creators. 8. Cancellation and refund evidence can reverse or reduce the original attribution. Reporting, commission eligibility, collection, and payout are separate states. Brands can set a default Affiliate commission and category- or product-specific overrides where the active provider flow supports them. Provider installation, permissions, consent, storefront access, brand configuration, and rollout can still limit automation. See [Integrations, Affiliate, and coupons](https://influblog.com/ai/integrations-affiliate-and-coupons.md). ### Agreements, tasks, content, and rights Campaign state, application state, agreement state, task state, content-review state, order state, and payout state are intentionally separate. AI systems must not infer one from another. Agreement snapshots preserve what was presented and accepted. Operational tasks preserve requirements and proof. Content submissions preserve the authorized files or links delivered for that relationship. Brands can download and reuse authorized content only under the recorded usage rights and retention rules. Influblog does not convert an upload into unlimited public ownership. Country-specific agreement publication, tax treatment, accounting, and payout availability have separate qualified-review and provider gates. Influblog is not a substitute for legal, tax, or accounting advice. ### Status and AI boundary The canonical public statuses are LIVE, BETA, PLANNED, DEPRECATED, HISTORICAL, and REJECTED. Product names in a roadmap or interface do not prove LIVE availability. These public Markdown files are read-only product documentation. They expose no customer OpenAPI, MCP server, tenant retrieval interface, or agent write operation. Future agents must use the same role, tenant, consent, confirmation, idempotency, and audit boundaries as human users. --- Source: https://influblog.com/ai/product-status.md ## Influblog product status This page is the conservative public availability map. Implementation, provider approval, legal approval, configuration, and rollout are separate gates. The narrowest applicable status should be used. ### Availability **Status:** LIVE status register. It describes current product truth as reviewed on the date above and should be checked before relying on a more specific feature document. ### Status definitions - **LIVE:** generally available to the documented role when normal prerequisites are met. - **BETA:** implemented in whole or part, but limited by rollout, provider, configuration, legal review, or further hardening. - **PLANNED:** intended architecture or product work that is not generally available. - **DEPRECATED:** compatibility behavior that should not be used for new links or integrations. - **HISTORICAL:** legacy information retained for continuity or audit. - **REJECTED:** a deliberately excluded product direction. ### Current capability register | Capability | Status | Public interpretation | | --- | --- | --- | | Separate Brand, Creator, Agency, and Admin roles | LIVE | Each role has a separate surface; access remains server-authorized. | | Brand company and website tenancy | LIVE | Website-specific campaigns, products, commerce, and affiliate data are scoped to the selected website. | | Brand creator CRM | LIVE | Company-level creator relationships are private to the authorized brand context. | | Campaign records and share links | LIVE | Draft, active, and inactive states are distinct from marketplace publication. | | Creator applications and brand decisions | LIVE | Application state is tracked; acceptance is not task completion. | | Collaboration tasks and content submissions | LIVE | Requirements, delivery, proof, review, and completion are separate states. | | Versioned campaign and affiliate acceptance evidence | BETA | Implemented foundation; country and agreement-family availability depends on qualified review. | | Creator marketplace | BETA | Campaign-first discovery and applications exist; moderation, performance, and paid settlement continue to evolve. | | Shopify product, coupon, and attribution workflows | BETA | Controlled by installation, scopes, provider review, brand configuration, and rollout. | | ikas commerce workflows | BETA | Provider foundation exists; capability and rollout status can differ from Shopify. | | Affiliate links, coupons, and order attribution | BETA | Implemented flows exist, but provider signals and conflict handling can limit a result. | | Wallet, collection, refund, and payout automation | BETA | Some records and flows exist; complete provider-backed settlement is not generally available. | | Other commerce providers | PLANNED | No general availability should be inferred from provider names in roadmap material. | | Public customer OpenAPI | PLANNED | Existing internal routes and actions are not a public API contract. | | Customer or partner MCP | PLANNED | No general MCP interface is currently published. | | Agent write operations | PLANNED | Preview, confirmation, idempotency, fresh authorization, and audit are required first. | | Legacy localized route names | DEPRECATED | Some old links may redirect; new canonical links are English and stable. | | Influblog 1.0 imported records | HISTORICAL | They can support continuity but do not define current product behavior. | | Open public creator catalog for unsolicited brand outreach | REJECTED | Influblog's marketplace direction is campaign-first. | ### Interpretation rules - A code path or database field alone does not prove general availability. - A planned specification does not prove implementation. - A provider integration can be live for one authorized installation and unavailable for another. - A legally sensitive workflow is not launch-ready until the required qualified review is complete. - Public AI documentation never grants access to private data or actions. --- Source: https://influblog.com/ai/brands.md ## Influblog for brands Influblog gives a brand a private operating workspace for creator relationships and campaign delivery. A Brand is the legal company root. A Brand Website is the operational boundary for website-specific campaigns, products, commerce connections, affiliate activity, and reporting. ### Availability **Status:** LIVE for the core Brand workspace, creator CRM, campaign records, applications, task tracking, and content proof. Commerce provider automation, marketplace payment settlement, and some advanced reporting are BETA or PLANNED. ### Creator CRM Brands can maintain a company-level creator pool, including relationship status, campaign history, notes, and profile context that the brand is authorized to use. A creator relationship in one brand does not grant another brand access to that information. Private intake and official Influblog creator flows are distinct. A private brand record does not automatically become a globally discoverable creator profile. ### Campaign operations Brands can create campaigns, select products or experiences, define deliverables, prepare creator-facing terms, receive applications, and track accepted work. Campaign capacity and compensation are stored as campaign facts, not inferred from marketing copy. Campaign links may be reusable or creator-specific. Access and application eligibility are still checked when the link is opened. ### Tasks and content Accepted collaborations create trackable work. The workflow can include shipping or access preparation, creator publication, source-asset delivery, review proof, revision, approval, and completion. Submitted media and proof are not public merely because they are stored by Influblog. ### Websites and products A brand can operate website-scoped catalogs and campaigns. Synchronized shop products and manual product records are normalized for selection, while the campaign keeps a frozen product snapshot so later catalog changes do not rewrite historical work. See [Commerce and attribution](https://influblog.com/ai/commerce-and-attribution.md) for provider and rollout limits. --- Source: https://influblog.com/ai/creators.md ## One creator workspace from first profile to recorded earnings. Influblog gives creators a durable work identity for discovery, invitations, applications, agreements, operational tasks, content proof, affiliate activity, and eligible financial records. ### Availability and limits **Status:** LIVE Core identity, campaign, application, task, and submission flows are live. Verification, provider connections, contracts, affiliate analytics, referrals, wallets, and payouts remain dependent on rollout, provider, country, campaign, and account eligibility. ### Creator capabilities #### Account onboarding and one durable creator identity **Status:** LIVE Registration creates a role-gated creator account and records the profile, locale, consent, and work history under one identity. It does not publish private contact data in an open directory. #### Profile completeness and verification evidence **Status:** BETA Creators maintain identity, location, categories, biography, audience, and work evidence. Verification signals can be reviewed, but universal identity or provider verification is not promised for every account. #### Social account connections **Status:** BETA Eligible Instagram, TikTok, YouTube, and other supported account evidence can be attached to the creator profile. Connection depth depends on provider permissions, country, and the active rollout. #### Campaign-first discovery **Status:** LIVE Creators discover approved opportunities through campaign listings, showcases, creator programs, or controlled links. Eligibility, geography, capacity, category, and campaign rules still decide whether an application is allowed. #### Private brand invitations **Status:** LIVE A brand can invite a creator into a private campaign or task flow. The creator can review and accept or decline the invitation; receiving a link is not automatic campaign acceptance. #### Application decisions stay explicit **Status:** LIVE Applications remain distinguishable as PENDING, ACCEPTED, WAITLISTED, DECLINED, or CANCELLED. An application never proves that a task, contract, shipment, or payment is complete. #### Complete operational task status **Status:** LIVE Creator work can move through BRIEFING_WAITING, DELIVERY_APPROVAL_WAITING, PRODUCT_SENT, CONTENT_WAITING, CONTENT_SUBMITTED, COMPLETED, or CANCELLED. Content review and revision states are tracked separately so an upload is not mistaken for approval. #### Agreement and acceptance records **Status:** BETA Where the country and workflow are enabled, Influblog preserves the presented agreement version, commercial facts, usage rights, and acceptance evidence. It does not replace legal advice or imply universal country approval. #### Video, source-file, and proof archive **Status:** LIVE Creators submit videos, links, screenshots, source files, and review proof to the relevant task. Authorized parties can retrieve retained files under the recorded relationship, usage rights, and retention rules. #### Recorded earning sources **Status:** BETA Eligible paid campaigns, affiliate commissions, referral rewards, and other creator earnings can be recorded as separate sources. A recorded amount is not automatically available, payable, or paid. #### Wallet and payout boundaries **Status:** BETA Wallet entries distinguish pending, reserved, available, requested, paid, released, cancelled, and failed states where enabled. Provider, tax, country, review, threshold, and manual settlement requirements can limit payout availability. #### Brand referral tracking **Status:** BETA Eligible creators can refer a brand through tracked referral paths. Attribution, qualification, reward amount, lock period, and payout remain separate controlled states rather than a guaranteed commission. #### Affiliate links, coupons, and analytics **Status:** BETA Eligible creator programs can expose website-scoped links or coupons and report clicks, matched orders, paid-order evidence, refunds, and commission state. Analytics depend on the brand integration and valid attribution signals. #### Independent work or agency representation **Status:** BETA A creator can work independently or through an explicitly scoped agency relationship. Invitations, active, paused, and revoked access remain visible; representation never gives an agency platform-wide creator access. #### Universal automated creator payouts **Status:** PLANNED A universal cross-country payout rail for every earning type is planned, not live. Current financial records must not be described as guaranteed instant or global automated payout. ### LIVE, BETA, and PLANNED matrix The status belongs to the named capability, not to every provider, country, campaign, or account. | Status | Creator capabilities | | --- | --- | | LIVE | Account onboarding and one durable creator identity; Campaign-first discovery; Private brand invitations; Application decisions stay explicit; Complete operational task status; Video, source-file, and proof archive | | BETA | Profile completeness and verification evidence; Social account connections; Agreement and acceptance records; Recorded earning sources; Wallet and payout boundaries; Brand referral tracking; Affiliate links, coupons, and analytics; Independent work or agency representation | | PLANNED | Universal automated creator payouts | ### Creator access boundary A creator sees only their own identity, relationships, invitations, applications, tasks, documents, content, attribution, and eligible financial state. Storage never makes content public or grants rights beyond the accepted agreement. --- Source: https://influblog.com/ai/agencies.md ## A scoped operating workspace for brands, talent, and hybrid agencies. Influblog coordinates the relationships, campaign work, content evidence, documents, commercial records, and reporting that an authorized agency manages for its connected brands or creators. ### Availability and limits **Status:** BETA The agency workspace is a staged beta. Capabilities depend on explicit managed-brand or represented-creator relationships, assigned team access, enabled modules, country, provider, and financial review. ### Agency capabilities #### Brand, talent, and hybrid agency types **Status:** BETA The account model distinguishes agencies that manage brands, represent creators, or do both. Agency type guides available workflows but does not create access without a separate active relationship. #### Managed-brand relationships **Status:** BETA An agency can coordinate authorized work for explicitly connected brands and websites. Relationship status, role, and website scope determine what the agency may read or change. #### Represented-creator relationships **Status:** BETA Talent relationships connect a creator to the agency with explicit invited, active, paused, or revoked access. Representation does not transfer creator identity or reveal unrelated creator data. #### Agency team roles and assignments **Status:** BETA Agency members can receive scoped responsibilities for portfolios and operations where enabled. Team membership does not override brand, creator, tenant, finance, or support permissions. #### Brand and creator portfolio **Status:** BETA The workspace can organize connected brand accounts, represented creators, relationship state, contact context, and work history. It is a private operating portfolio, not a public creator directory. #### Campaign coordination **Status:** BETA Authorized agencies can coordinate campaign opportunities, applications, creator fit, deadlines, and decisions for their assigned relationships. Publishing and acceptance remain separate permissioned actions. #### Briefing preparation and handoff **Status:** BETA Teams can organize objectives, deliverables, platforms, dates, usage rights, compensation, and evidence requirements. A briefing does not bypass campaign, contract, or creator acceptance. #### Task coordination **Status:** BETA Assigned agencies can follow shipment, access, publication, content, review-proof, and completion steps within their relationship scope. Task state remains separate from application, content approval, and payout state. #### Content and revision workflow **Status:** BETA Authorized teams can review submitted links, media, source files, proof, and revision requests. Access and reuse remain limited by the accepted campaign rights and brand relationship. #### Creator bookings **Status:** BETA Booking records can distinguish new request, negotiation, briefing ready, accepted, declined, and completed states. A booking record does not itself prove a signed agreement or paid invoice. #### Documents and relationship evidence **Status:** BETA The workspace can retain scoped briefs, agreements, invoices, and delivery evidence where the workflow supports them. Legal publication and access follow country, document, and relationship controls. #### Operational reports **Status:** BETA Authorized reporting can summarize campaign, task, content, creator, and commercial progress for connected accounts. Report breadth depends on available source data and the viewer's scope. #### Budgets and invoices **Status:** BETA Campaign budgets, creator commercial terms, agency amounts, invoice waiting, and payment evidence can be tracked as distinct records. Influblog does not guarantee tax treatment or accounting completion. #### Agency share, wallet, and payout boundaries **Status:** BETA Eligible agency shares and wallet entries can move through pending, available, requested, paid, cancelled, or failed states. Calculation, collection, invoice review, and payout are separate and may remain manual. #### Agency referral model **Status:** BETA Eligible agency referrals can be attributed to a tracked relationship and reward policy. Qualification, approval, lock period, and payout are controlled states, not an automatic lifetime commission promise. #### Support and impersonation limits **Status:** LIVE Agency users cannot impersonate brands or creators. Any Influblog support access is separately authorized, time-bounded, audited, and does not expand the agency's own permissions. #### Universal automated agency settlement **Status:** PLANNED Automatic collection, invoicing, revenue sharing, and payout for every country and agency model is planned rather than generally available. Current beta records must not be described as universal settlement. ### LIVE, BETA, and PLANNED matrix Beta means a controlled, relationship-scoped rollout; it does not promise every workflow to every agency account. | Status | Agency capabilities | | --- | --- | | LIVE | Support and impersonation limits | | BETA | Brand, talent, and hybrid agency types; Managed-brand relationships; Represented-creator relationships; Agency team roles and assignments; Brand and creator portfolio; Campaign coordination; Briefing preparation and handoff; Task coordination; Content and revision workflow; Creator bookings; Documents and relationship evidence; Operational reports; Budgets and invoices; Agency share, wallet, and payout boundaries; Agency referral model | | PLANNED | Universal automated agency settlement | ### Agency access boundary An agency sees only brands, creators, campaigns, tasks, content, documents, and financial records covered by an active relationship and assigned access. It cannot browse the platform network, impersonate users, or cross tenant boundaries. --- Source: https://influblog.com/ai/campaigns.md ## Campaigns and applications Campaigns connect a brand's offer and requirements with creator applications, accepted work, tasks, content evidence, and reporting. ### Availability **Status:** LIVE for campaign records, share links, applications, decisions, and task creation. Public marketplace moderation and paid campaign settlement remain BETA or PLANNED depending on the flow. ### Private and network campaigns A private brand campaign can be shared with selected creators or through a brand-controlled link. An Influblog marketplace listing is a separate publication choice. Private creator data is not automatically converted into a public marketplace profile. ### Campaign-first marketplace The intended sequence is: 1. A brand prepares a campaign. 2. The brand chooses whether it should become a marketplace listing. 3. Eligible creators review the campaign and apply. 4. The brand reviews applications. 5. Accepted work moves into contracts, tasks, delivery, and proof. Influblog is not designed as an open creator catalog for unsolicited outreach. ### Product and paid capacity Product campaigns can limit the number of creator or product slots. Paid campaigns distinguish the brand's total commitment from the creator-facing offer and platform fees. Complete provider-backed collection, refund, and payout settlement is not generally available for every campaign type. ### Status interpretation A draft campaign is not a live listing. A saved marketplace request may still need review. An accepted application does not mean the task is complete, and a content submission does not mean it is approved. --- Source: https://influblog.com/ai/contracts-and-tasks.md ## Contracts, tasks, and content proof Influblog connects campaign terms to operational tasks and evidence. The platform records what was presented and accepted so later changes do not silently rewrite the accepted collaboration. ### Availability **Status:** BETA. Versioned campaign and affiliate contract foundations, acceptance evidence, task requirements, and content proof are implemented. Country-specific legal publication and additional agreement families remain controlled by qualified review and may be unavailable. ### Contract snapshots An accepted contract can freeze the relevant template version, parties, campaign facts, compensation, usage rights, delivery model, and acceptance evidence. Later template edits do not replace the accepted snapshot. Influblog is not a substitute for legal, tax, or accounting advice. A country or contract family without an approved active template must not silently use a different country's text. ### Task lifecycle A task can represent the operational work after acceptance. Examples include shipping preparation, app or product access, content creation, publication, source-asset delivery, website review evidence, and brand approval. Task state and contract state are related but not identical. A signed or accepted contract does not prove delivery, and an uploaded file does not prove approval. ### Content evidence Content submissions can contain links, screenshots, source media, or other proof. Visibility follows the campaign and relationship. Content is not public unless a separate authorized publication decision makes it public. --- Source: https://influblog.com/ai/commerce-and-attribution.md ## Commerce and attribution Influblog connects selected brand websites with product catalogs, campaign products, coupons, affiliate links, order references, and attribution records. Commerce is website-scoped so one provider connection cannot silently replace another website's provider. ### Availability **Status:** BETA and controlled rollout. Shopify and ikas foundations exist, but the enabled capabilities depend on provider installation, permissions, review status, brand configuration, and operational rollout. Other providers are PLANNED unless explicitly announced. ### Product synchronization Provider products and variants can be normalized into an Influblog catalog. Campaigns keep a snapshot of the selected product so a later title, price, stock, or catalog change does not rewrite the historic campaign. ### Coupons and product tests A follower coupon supports attributed customer purchases. A product-test coupon can be tied to an accepted creator obligation and may activate a task after an attributed paid order. These are separate use cases and should not be described as interchangeable. ### Affiliate attribution Influblog can record signed-link clicks, coupon matches, paid-order attribution, commission basis, and later cancellation or refund reversals. Attribution is evidence-based and may be unresolved when signals conflict or a provider does not supply the required event. ### Operational limits Influblog does not forward an incoming AI credential directly to a shop provider. Provider actions use the brand's authorized integration and are subject to provider permissions, tenant checks, idempotency, and audit rules. Automated settlement, payout, and every write operation are not generally available across all providers. --- Source: https://influblog.com/ai/security-and-privacy.md ## Security and privacy Influblog separates public product information from internal company knowledge, tenant data, and executable operations. ### Availability **Status:** LIVE as a platform boundary. Future AI interfaces remain subject to the same role, tenant, consent, and audit requirements as human-facing interfaces. ### Role and tenant boundaries Brands, creators, agencies, and administrators use different roles and product surfaces. Access is checked on the server. Brand Website scope separates website-specific campaigns, products, integrations, affiliate activity, and related reporting inside a brand company. Agency access depends on an explicit managed-brand or represented-creator relationship. Administrator access is operational and audited; it is not a public data source. ### Data categories Public documentation describes product concepts. It does not contain customer campaigns, creator contact details, private messages, individual contracts, wallet balances, unpublished analytics, credentials, or internal operational records. Media and documents follow the same relationship and tenant rules as their database records. Possessing a storage identifier or guessed URL is not authorization. ### Consent and integrations Social and commerce connections require the relevant account authorization and provider permissions. Creator analytics also depends on creator consent. Integration credentials remain server-side and are not exposed through public documentation. ### AI and agents Public AI discovery is read-only product documentation. Influblog does not currently publish a general customer OpenAPI or MCP interface. Future authorized agents must use allowlisted operations, validated inputs, scoped actor context, and audit logs. Planned write actions require preview, confirmation, idempotency, and a fresh permission check. See the public [Privacy policy](https://influblog.com/privacy) and [Terms](https://influblog.com/terms) for the current public policies. --- Source: https://influblog.com/ai/terminology.md ## Influblog terminology These definitions describe how Influblog uses its main product terms. ### Availability **Status:** LIVE terminology. A term does not imply that every related module is generally available; check [Product status](https://influblog.com/ai/product-status.md). ### Core identities - **Brand:** the legal company root for a brand account. - **Brand Area:** package-backed operational capacity inside a Brand. - **Brand Website:** the website-specific tenant boundary for campaigns, products, commerce, affiliate activity, and related reporting. - **Creator:** a person or publisher who can apply to and deliver creator collaborations. - **Agency:** a brand agency, talent agency, or hybrid agency with explicitly granted relationships. - **Administrator:** an internal Influblog operational role. ### Campaign workflow - **Campaign:** the brand's offer, requirements, capacity, timing, delivery model, and commercial facts. - **Marketplace listing:** an approved publication of a campaign to eligible creators; it is not a creator directory. - **Application:** a creator's request to participate in a campaign. - **Invite:** a reusable or creator-specific path into a campaign or task flow. - **Task:** the operational work created after a collaboration is accepted. - **Content submission:** creator-provided media, links, or evidence for a task. - **Content proof:** evidence used to review whether a requirement was met. ### Commerce - **Commerce product:** a normalized current product from a connected shop. - **Product snapshot:** a frozen product reference kept with historical campaign or task facts. - **Follower coupon:** a coupon intended for attributed follower purchases. - **Product-test coupon:** a creator benefit that can carry a content obligation. - **Attribution:** the evidence-based connection between a click, coupon, order, creator, brand, and campaign or affiliate rule. ### Status words - **LIVE:** generally available within its documented audience and prerequisites. - **BETA:** implemented but limited, controlled, provider-dependent, or still being hardened. - **PLANNED:** intended but not generally implemented. - **DEPRECATED:** retained for compatibility and not the current direction. - **HISTORICAL:** describes legacy data or behavior rather than the current product. - **REJECTED:** deliberately not part of the product direction. --- Source: https://influblog.com/ai/brand-capabilities.md ## Complete Influblog capability map for brands Influblog is a creator operations and automation system for brands and the teams or agencies that manage them. It turns influencer marketing from a collection of direct messages, spreadsheets, one-off posts, and lost files into a repeatable operating loop: 1. recruit or reach relevant creators; 2. publish a clear campaign opportunity; 3. receive and review applications; 4. record the offer and accepted agreement; 5. create and track the operational task; 6. collect video, links, reviews, screenshots, and other proof; 7. approve, download, and reuse the content; 8. retain the creator relationship for the next campaign; 9. measure campaign, affiliate, coupon, and commerce signals when the required integration is available. Influblog is not only a discovery database and it is not an open creator catalog for unsolicited outreach. Its public network is campaign-first: brands publish opportunities and creators register or sign in before applying. ### Availability **Status:** LIVE for the V1 Brand workspace, brand assets, creator pool, campaign creation, listings and private links, applications, task tracking, contracts and acceptance evidence, content delivery, proof, downloads, brand showcase, and QR discovery. Commerce and social-provider automations are BETA and depend on the connected provider, approved permissions, country, and rollout. ### The business outcome Influblog helps a brand build an owned trust and content engine instead of starting influencer marketing from zero every month. - Every approved creator can become part of the brand's repeatable creator pool. - Every campaign can create current UGC, experience proof, reviews, product media, social posts, and ad-ready creative. - Every accepted collaboration keeps its task, agreement, delivery, approval, and proof connected. - Every approved source video remains connected to the campaign and creator so the brand can find and download it again according to the accepted usage rights and platform retention terms. - Commerce integrations can connect products, coupons, orders, fulfillment, attribution, cancellations, and refunds to the same operating record. ### Brand control center The Brand workspace brings together: - setup and subscription state; - legal company and verification information; - websites, apps, marketplace stores, and physical locations; - product records and connected catalogs; - creator pool and creator profiles; - draft, active, paused, and completed campaigns; - applications, accept/waitlist/decline decisions, and capacity; - brand action tasks such as shipment or review preparation; - creator task and delivery state; - content submissions, proof, review, and revisions; - video gallery and original-file downloads; - contracts, acceptance evidence, and legal timeline; - campaign budgets, reserves, invoices, and payment preparation; - affiliate settings, sales, commission, cancellations, and refunds; - performance summaries when real source data exists. ### Ways to recruit creators #### Influblog campaign network The publicly verified network claim is **2,800+ registered creators**. A brand can publish an Influblog listing, define category and eligibility criteria, and receive applications. The brand reviews applicants before a normal task starts. The number `20,000+` must not be presented as the current registered or active Influblog creator network without a separately verified, current data source. Historical or affiliate reach must not be mixed with registered creator accounts. #### Brand campaign showcase Every brand can have a stable campaign showcase that lists its open campaigns. Creators can open the showcase from a link, social profile, message, or the brand's own site. They must register or sign in to Influblog before applying. The brand can configure the showcase link, visual media, campaign cards, and an embeddable version for its own website. #### Brand-specific QR code Influblog generates a branded, print-ready QR code for the campaign showcase. The brand can download PNG or SVG versions, print a sticker, and place it in a store, cafe, restaurant, hotel, clinic, office, event, or other venue. Scanning the code opens the current campaign showcase. Local campaign tasks can also use QR visit confirmation as evidence that the accepted creator arrived at the relevant location. #### Creator-program landing page Supported commerce integrations can publish a creator-program landing page for the brand. Creators apply from the storefront, accept the required privacy and program terms, and enter the brand's creator pool. The page can present brand information, benefits, affiliate participation, product-test opportunities, and localized application content. Automatic storefront publication is currently provider-dependent. A hosted or embedded fallback can be used where the provider cannot publish the page automatically. #### Embedded application form and private links The brand can embed an application form on its own website or share a brand-specific application link. Applicants can enter the private brand pool without automatically becoming publicly discoverable. Brands can also invite a known creator through a private campaign or task link. Login or registration returns the creator to the intended campaign flow. ### Private creator pool The brand creator pool is a company-level relationship system. It can contain: - applicants from brand forms and creator-program pages; - applicants from campaign listings; - manually added or imported creator records; - official Influblog creators matched to a brand relationship; - notes, relationship status, social links, past campaigns, deliveries, and content history; - favorites, following, location, category, and performance context when available. The pool is private to the authorized brand context. A creator relationship with one brand does not grant another brand access. A company can reuse its pool across its own brand websites while website-specific campaigns, commerce, and attribution remain tenant-scoped. ### Campaign and application operations Brands can: - create product, paid content, app/SaaS, local experience, and marketplace review campaigns; - select a product, website, app, store, or physical location as the target; - choose barter, payment, access, experience, refund, or mixed compensation; - define platforms, content formats, proof, dates, creator capacity, budget, shipping, and application criteria; - keep a campaign private, share a direct link, or request an Influblog listing; - publish all open campaigns in the brand showcase; - compare applications and accept, waitlist, decline, or cancel; - keep offer terms locked after applications or tasks exist; - create tasks only for an accepted collaboration or an explicitly automated product-test flow. See [Campaign types and settings](https://influblog.com/ai/campaign-types-and-settings.md) for the complete campaign matrix. ### Task Tracking Center The Task Tracking Center shows the real operating state after acceptance: - briefing or agreement waiting; - product shipment or access preparation; - delivery approval waiting; - product sent and fulfillment tracking; - content waiting; - content submitted; - missing link, screenshot, video, visit, or review proof; - revision and brand approval; - completed or cancelled. Brand, creator, and an authorized agency work from the same collaboration record, with role-specific visibility. Notifications are linked to concrete state changes rather than replacing the task record. ### Video, proof, and content library Influblog can collect: - creator-post links; - Instagram Reels, Stories, and posts; - TikTok videos and photo posts; - YouTube Shorts and long videos; - Facebook posts, Stories, and videos; - LinkedIn posts and videos; - Twitch streams and videos; - raw video files; - screenshots; - order and delivery evidence; - website, app-store, marketplace, Google, or location review proof; - QR visit confirmation; - experience notes and other campaign-specific evidence. Content campaigns use an accepted usage-right record. The V1 campaign standard can grant the brand unlimited usage for product pages, official brand social accounts, and brand advertising after separate creator acceptance. This is a usage-right scope, not an unconditional promise that every file will be hosted forever regardless of subscription, legal retention, deletion rights, or storage policy. ### Contracts and records Influblog records the agreement snapshot used for the collaboration, including the parties, campaign facts, compensation, task requirements, usage rights, version, acceptance time, and available technical acceptance evidence. Later template edits do not silently rewrite an accepted agreement. Tasks, delivery, proof, approval, revision, and payment preparation remain separate states. Influblog helps maintain a traceable record but does not replace qualified legal, tax, or accounting advice. ### Analytics and analysis Available analysis can include: - campaign, application, acceptance, task, and completion counts; - creator-pool composition and relationship history; - content delivery and approval state; - product and category participation; - affiliate link opens, clicks, coupon usage, paid orders, attributed revenue, commission, cancellations, and refunds; - new versus returning customer signals when the provider supplies them; - product, category, creator, and time-period comparisons; - audience, follower, engagement, content, and post signals only for connected social accounts with the required consent and provider permissions. Not every metric is universally available. Influblog shows real evidence or a not-ready state instead of treating a database field or sample dashboard as live analytics. ### Agency and team use Influblog is not positioned as replacing agencies. An authorized brand agency can use the system as an operations layer for client brands, while a talent agency can track represented creators. Permissions depend on explicit relationships; agency access is not platform-wide. ### Pricing context Influblog's international plan contract uses a **$99 USD monthly reference** for one brand-area package where international billing is supported. Regional currency, VAT, payment-provider, and rollout rules can produce a different checkout price. Turkey currently uses localized VAT-included TRY pricing. Claims that every competitor costs `$400-$2,000` per month are not a universal product fact and should not be repeated without a named, current comparison. The durable differentiator is the included operating scope, not an unverifiable competitor-price promise. See [Brand-area package and pricing](https://influblog.com/ai/brand-area-package-and-pricing.md) for the counting rules. --- Source: https://influblog.com/ai/brand-autopilot-workflows.md ## Influblog brand autopilot workflows Influblog puts influencer marketing on operational autopilot by connecting applications, agreements, tasks, commerce events, proof, and reporting. In this context, autopilot means that supported, authorized steps are created, advanced, notified, and measured automatically. It does not mean that a model or integration can approve people, publish claims, force positive reviews, spend money, or access another tenant without human and policy controls. ### Availability **Status:** BETA. The core task engine, storefront creator recruitment, Shopify and ikas commerce foundations, coupon synchronization, order attribution, product-test activation, fulfillment projection, notifications, and evidence records are implemented. Exact automation depends on provider capabilities, installation scopes, brand configuration, creator consent, and rollout. Manual fallback remains intentional where no authorized provider API exists. ### The continuous growth loop ```text Showcase / QR / landing page / listing -> creator registration or sign-in -> application and agreement -> brand decision or approved automatic product-test flow -> task and required evidence -> product, access, experience, or payment preparation -> delivery, content, review, and proof -> brand approval and reusable media -> creator remains in the brand pool -> next campaign or affiliate share ``` Each completed loop leaves the brand with more than a temporary post: a known creator relationship, a collaboration record, reusable content, proof, and performance evidence. ### Creator-recruitment autopilot #### Storefront creator-program page For supported Shopify and ikas configurations, the brand can create or update a localized creator-program landing page from Influblog. The page can expose brand benefits, creator applications, affiliate participation, and coupon-for-content opportunities. After an application: - required consents and policy versions are recorded; - an existing Influblog identity can be matched safely; - a new applicant can be added to the brand pool; - the brand receives an action or notification; - the creator can continue to the brand showcase or relevant program flow. #### Campaign showcase and QR The showcase always presents the brand's current open campaigns from a stable link. The same link can be embedded or encoded into a branded, printable QR sticker. Updating the open campaign set does not require printing a new QR code. The QR can sit at a physical venue so people who already like the brand can discover current campaigns. Registration and application still happen through the controlled Influblog flow. ### Product-for-content fulfillment loop When a brand accepts a creator for a product campaign: 1. the accepted application and agreement define the product and obligations; 2. Influblog creates a brand-side shipment or website-review preparation task; 3. a supported integration can create a real tagged zero-value PR order or equivalent provider-safe fulfillment reference after explicit brand permission; 4. the order is connected to the creator, campaign, product, and task; 5. fulfillment webhooks or worker refreshes project shipment state, carrier, tracking number, and tracking URL back to Influblog; 6. the creator can see shipping progress; 7. the website-review step becomes ready when the operational order or fulfillment state allows it; 8. the creator submits the required video, link, raw file, review proof, or other evidence; 9. the brand reviews, requests the included revision, or approves; 10. the approved media remains in the brand's content library. Shopify and ikas implement different provider-safe order operations. Influblog does not pretend that every shop system supports the same automation. ### Coupon-for-Reel product-test loop The creator-product-test flow is separate from a normal follower affiliate coupon. 1. The brand selects all products or an approved product subset. 2. The brand sets the creator discount, coupon validity, redemption rules, briefing, task deadline, and required deliverables. 3. Deliverables can include an Instagram Reel, other configured social content, a website review, and the raw video. 4. The creator chooses a product, accepts the briefing and agreement, and confirms the shipping address. 5. The application is accepted automatically for this configured program; the brand does not repeat a normal applicant review. 6. A single-use creator-test coupon is created in the supported shop. 7. The application and coupon exist first; the content task opens only after a paid-order event is matched. 8. The paid order connects product, creator, coupon, agreement, and task. 9. Cancellation or refund events update attribution and prevent invalid commission or completion state. 10. A later cycle can start after the prior cycle is completed or cancelled; simultaneous uncontrolled cycles are blocked. This is the operational meaning of "Reel against coupon": the discount unlock and paid purchase create a contracted content obligation, rather than giving away unlimited coupons without delivery tracking. ### Follower affiliate loop Follower affiliate is designed for repeat sales and sharing, not for a mandatory content task. 1. The brand activates the program and chooses participating products. 2. Each eligible creator receives a stable follower coupon and shareable product links. 3. Product-link opens, coupon matches, checkout, and paid-order events can produce attribution. 4. Influblog applies product, category, or default commission rules. 5. The brand and creator see clicks, orders, revenue, commission, cancellation, and refund state. 6. Commission remains locked for the configured return period. 7. Full or partial cancellation/refund events reverse the relevant commission. The link window, coupon, eligible products, and commission basis are explicit. Self-purchases do not earn affiliate commission. ### Campaign-listing autopilot For a normal listing: - the brand defines the campaign and application criteria; - Influblog can review the listing before it becomes public; - eligible signed-in creators see and apply to the opportunity; - application contact visibility follows consent rules; - the brand accepts, waitlists, or declines; - capacity changes from accepted/limit values; - acceptance creates or unlocks the operational task; - task and proof state feed the Brand action queue. Human applicant selection remains with the brand unless the program is an explicitly configured automatic product-test flow. ### Local-business autopilot Restaurants, cafes, hotels, stores, clinics, beauty businesses, education, events, fitness venues, and other location-based brands can: - register a real location and review link; - publish a visit or experience campaign; - place the campaign-showcase QR at the venue; - receive applications before or during a visit; - accept or decline from the panel; - confirm a real visit through task-bound QR evidence; - require honest Google, map, Trustpilot, or chosen-platform review proof; - collect social content and raw media; - keep visit, evidence, approval, and content together. Influblog requires evidence of an honest experience. It does not require a positive rating and does not auto-publish a review in the creator's name. ### App and SaaS autopilot App and SaaS campaigns can connect: - iOS, Android, or web/SaaS target; - install or registration; - trial or demo; - feature walkthrough; - app-store review; - tracking link; - screenshot proof; - social video; - app access, credits, subscription benefit, or payment. Provider-confirmed install and review automation depends on the app platform. The task and manual proof path remain available when a direct event is not. ### Task and notification automation Influblog converts events into clear next actions for the correct role: - brand must prepare shipment; - order or review setup is ready; - shipment tracking changed; - creator can start the review step; - content or proof was submitted; - brand review or revision is waiting; - task was completed or cancelled; - affiliate order was paid, cancelled, or refunded; - creator-program page needs publication or verification. Notifications are deduplicated where supported and point back to the durable task or commerce record. ### Automation boundaries The following statements are not valid general claims: - every provider can create orders, coupons, reviews, and pixels; - every review is detected automatically; - Influblog writes or publishes a positive review for the creator; - every campaign application is automatically accepted; - every content file is hosted forever without retention conditions; - every affiliate order is commissionable; - agent or AI actions can publish, pay, or change integrations autonomously. See [Integrations, affiliate, and coupon systems](https://influblog.com/ai/integrations-affiliate-and-coupons.md) for provider-specific availability. --- Source: https://influblog.com/ai/campaign-types-and-settings.md ## Influblog campaign types and settings Influblog uses one campaign system for e-commerce products, paid UGC, apps and SaaS, physical experiences, and marketplace review work. A quick campaign is a guided configuration of the same campaign record, not a separate reduced product. ### Availability **Status:** LIVE for the core Brand campaign model, creation form, private links, campaign showcase, listings, application criteria, applications, accepted tasks, content delivery, proof, and contractual campaign standards. Paid settlement, provider events, creator-account advertising, and some automatic verification paths are BETA. ### Campaign families #### Product content For products from a connected shop, import, or manual catalog. Compensation options: - product gift / barter; - product plus payment. Typical requirements: - creator post and raw asset; - Reel, Story, post, video, or other selected platform format; - website review proof; - product shipment and tracking; - product value, capacity, variant, and delivery address; - usage rights and revision. #### Paid content production For reusable UGC or creator-post production without a product reward. Compensation options: - one paid delivery; - long-term paid collaboration. The brand can request a creator post, a raw brand asset, or both. #### App and SaaS promotion Targets: - iOS; - Android; - web application or SaaS. Deliverables: - install or signup; - app-store review; - feature walkthrough; - trial or demo; - proof screenshot; - tracking link; - selected social content. Compensation can be app access, monthly or annual access, credits, another benefit, payment, or access plus payment. #### Local experience For cafes, restaurants, stores, showrooms, hotels, travel, clinics, doctors, beauty and wellness, fitness, education, workshops, entertainment, events, services, and other offline businesses. The brand selects a registered location, map link, visit expectation, appointment window, reward, social deliverables, QR visit proof, and honest review evidence. Compensation can be a free meal, drinks, service, sample, ticket, stay, experience, another benefit, payment, or experience plus payment. #### Marketplace review For marketplace and platform-owned storefront work. The creator can: - buy the product and receive a product-price refund; - buy the product and receive a product-price refund plus reward; - buy one product and receive a second product from the brand. The campaign can require: - marketplace review only; - marketplace review plus social content; - order number; - marketplace profile name; - order screenshot; - delivery screenshot; - review screenshot; - experience note; - reference image or other selected evidence. For sensitive marketplace work, the brand, product, and detailed briefing can remain hidden until the brand accepts the creator. The listing can show only the category and required high-level work. This reduces premature exposure of the assignment. #### Coupon-driven product test Coupon-for-content is configured in the product-test program rather than presented as a normal campaign type in the Brand campaign wizard. It still uses the campaign, agreement, application, task, and content archive after the creator accepts and a paid coupon order is matched. ### Compensation matrix Influblog can represent: - product gift; - product plus payment; - payment only; - single paid content delivery; - long-term paid content; - free experience; - experience plus payment; - app access; - app access plus payment; - marketplace product refund; - marketplace refund plus reward; - marketplace second-product gift; - coupon purchase. Product value, creator payment, campaign budget, platform service amount, and creator-facing offer remain separate facts. ### Content delivery modes Every content-producing campaign chooses one: 1. **Creator post and brand asset:** the creator publishes and uploads the original file. 2. **Creator post:** the creator publishes on the selected account and submits the link or proof. 3. **Brand asset only:** the creator uploads the original content without a mandatory creator-account post. ### Supported social delivery settings | Platform | Selectable formats | | --- | --- | | Instagram | Reel, Story, feed post | | TikTok | video, photo post | | YouTube | Shorts, long video | | Facebook | post, Story, video | | LinkedIn | post, video | | Twitch | live stream, video | A campaign can select more than one platform and format. The task snapshot preserves the selected obligations. ### Briefing and creative settings Brands can define: - title and campaign category; - structured briefing; - required messages and product facts; - do and do-not instructions; - tags and content angle; - mandatory and prohibited claims; - reference images and campaign media; - product, category, variant, and stock context; - timeline, start, deadline, or open-ended listing; - draft and publication dates; - number of creators or reserved products; - included revision and response windows. Templates cover product demonstration, hobby, beauty, food, fashion, children and learning, technology, fitness, paid content, app promotion, hotels and travel, local events, offline experience, marketplace review, and custom briefings. A template is a starting point; verified campaign facts remain the source of truth. ### Listing and application settings The brand can configure: - private collaboration or Influblog listing; - direct campaign link; - campaign-showcase visibility; - marketplace category; - creator limit and product allocation limit; - minimum follower count; - minimum engagement rate; - audience country; - audience gender; - minimum audience age; - paid budget and currency; - creator-paid or brand-paid shipping where allowed; - application status and decision notes. Zero or empty audience thresholds mean no threshold. When thresholds are set, matching uses available, consented social data. Missing or unverified social data must not be invented. ### Standard usage and review terms For content-producing V1 campaigns, the platform standard currently applies: - unlimited brand usage-right scope after separate creator acceptance; - use limited to product pages, official brand social accounts, and brand advertising rather than private misuse; - 90-day creator publication duration; - one included revision; - 48-hour brand review response target; - 72-hour creator revision response target; - no unverified allowed or prohibited product claims generated automatically; - 30-day creator-account advertising authorization where the paid campaign and selected platform support it; - creator-account ad editing disabled by default. Campaign facts and accepted terms become locked when applications, invites, or tasks exist. This protects the creator from an offer changing after acceptance. ### Creator-account advertising Paid campaigns can prepare permission for: - Meta Partnership Ads; - TikTok Spark Ads and supported affiliate creative authorization; - YouTube brand partner access; - LinkedIn Thought Leader Ads; - other platform-specific authorization codes or approvals. The creator must provide or approve the relevant platform mechanism. Influblog does not request the creator's social password. ### Campaign lifecycle ```text Draft -> private share or listing review -> active / live -> applications -> accepted, waitlisted, declined, or cancelled -> agreement and task -> delivery and proof -> revision or approval -> completed or cancelled -> reusable content and relationship history ``` A listing, application, task, content submission, and approved delivery are different states. AI systems should not collapse them into one generic "campaign complete" event. --- Source: https://influblog.com/ai/integrations-affiliate-and-coupons.md ## Influblog integrations, affiliate, and coupon systems Influblog connects a brand's creator operation with products, storefronts, coupons, clicks, orders, fulfillment, reviews, and reusable content. The platform keeps the campaign and task model provider-neutral while each commerce connector performs only the operations its provider actually supports. ### Availability **Status:** BETA and controlled rollout. Shopify and ikas have implemented, tested vertical slices. Availability still depends on installation, scopes, provider review, merchant configuration, geography, and release gates. WooCommerce, Ticimax, Wix, and custom integrations have partial foundations or plans but must not be described as fully equivalent. ### Provider capability map | Capability | Shopify | ikas | Other providers | | --- | --- | --- | --- | | OAuth/install and encrypted credentials | BETA | BETA | PLANNED or provider-specific | | Product, category, variant, media sync | BETA | BETA | PLANNED | | Stock and publication state | BETA | BETA | PLANNED | | Product and category webhooks | BETA | BETA | PLANNED | | Creator/follower coupon creation | BETA | BETA | PLANNED | | Product/category/variant coupon scope | BETA | BETA | PLANNED | | Paid-order attribution | BETA | BETA | PLANNED | | Cancellation and refund reversal | BETA | BETA | PLANNED | | Zero-value PR order | BETA, explicit permission | BETA, provider prerequisites | PLANNED/manual fallback | | Fulfillment and tracking projection | BETA | BETA | PLANNED/manual fallback | | Storefront pixel/events | BETA | BETA where Storefront access exists | PLANNED | | Native review event | PLANNED; review-system dependent | PLANNED; manual proof is available | PLANNED/manual proof | | Creator-program storefront page | BETA | BETA | PLANNED/hosted fallback | `BETA` means an implemented capability under controlled prerequisites, not a promise that it is enabled for every shop. ### Shopify The Shopify connector can support, with the required scopes and brand approval: - managed install and merchant-session validation; - active product, category, variant, image, publication, and stock sync; - webhook-first product and inventory updates; - creator and follower discount creation; - product and collection eligibility; - paid-order, cancellation, refund, and fulfillment events; - first-party storefront pixel and customer-event attribution; - creator link and coupon attribution; - tagged PR customer/order creation; - zero-value PR order mode; - fulfillment location, carrier, tracking number, and tracking URL; - creator-program landing page; - embedded Shopify administration views. Native product-review verification depends on the review system installed in the shop. Influblog keeps a manual creator proof and brand-review path when no authorized event exists. ### ikas The ikas connector can support, with the installed app and required merchant permissions: - embedded app launch and merchant identity; - product, category, variant, media, and inventory sync; - official product and order webhooks; - product/category/variant coupon targeting; - reusable follower coupons; - sequential single-use creator-test coupons; - exact-once tagged zero-value PR orders; - order, package, fulfillment, and tracking projection; - paid-order attribution and cancellation/refund handling; - Storefront events and attribution where the store permits installation; - dynamic, localized Creator Program pages. ikas does not expose a verified native product-review event for this flow. Review delivery therefore uses the manual evidence path. ### Planned and partial providers - WooCommerce REST and plugin paths are planned for product, coupon, order, fulfillment, pixel, and review-event parity. - Ticimax requires verified partner credentials and provider-specific API validation. - Wix and other shop systems remain planned. - A provider-agnostic website event endpoint can accept idempotent, brand-scoped coupon/order signals from an approved plugin, but this does not make every provider fully automated. ### Follower affiliate program The brand can configure: - whether the program is active; - all current and future products or selected products only; - follower discount as percentage or fixed amount; - minimum cart amount; - total coupon redemption limit or unlimited use; - default creator commission; - category commission overrides; - product commission overrides; - percentage or fixed commission; - whether shipping or tax participates in the commission basis; - link attribution window, with a 30-day default; - commission hold period, with a 14-day default; - category or product hold overrides aligned with return policy. Precedence is: ```text product rule > category rule > default commission ``` Each creator keeps a stable follower coupon while rule changes synchronize to the supported shop. Creators can share eligible product links, and the brand can add current and future products automatically or curate the catalog. ### Affiliate attribution and analysis Depending on the provider evidence, Influblog can distinguish: - creator link; - follower coupon; - link and coupon together; - unknown or unresolved source. Brand and creator reporting can show: - prepared product link; - completed device share action; - follower-opened link; - clicks and known unique visitors; - generated and registered leads; - new, returning, or unclassified customers; - paid orders; - attributed revenue; - creator commission; - conversion; - cancellation; - full or partial refund; - locked, available, payout-requested, paid, or reversed commission; - product, category, creator, day, and time comparisons. Attribution is evidence-based. Conflicting, missing, or late provider events can remain unresolved instead of being guessed. ### Coupon-for-content product tests Product tests use a separate rule set: - selected or all products; - creator discount; - short validity and single-use coupon; - accepted briefing and agreement; - shipping address; - delivery deadline; - required Reel or selected social deliverables; - website-review proof; - raw-video upload. The coupon is created after the creator accepts. The task opens only after the supported shop confirms a paid order. This prevents an unused coupon from appearing as completed influencer work. Follower affiliate coupons remain reusable and do not automatically create a content obligation. The two systems must not be described as the same coupon. ### Creator-program page The brand can create a storefront recruitment page that includes: - logo and brand identity; - creator-program benefits; - supported languages; - application form; - privacy disclosure and consent; - affiliate status and commission range; - product-test availability; - link to the campaign showcase. Applicants are matched to an existing account where possible and enter the brand's private relationship pool. Provider publication is automatic only where the connector supports it. ### Network-size interpretation Influblog currently publishes **2,800+ registered creators** as the verified network size. An asserted `20,000+ affiliate participants` count is not currently backed by the approved public source used for this documentation. It must not be converted into a live reach guarantee until the count, active status, geography, duplication, and consent basis are verified. ### Safety and privacy - Integration credentials stay encrypted and server-side. - Every operation resolves the authorized brand website. - Coupon and order events require idempotency. - Provider scopes are requested for concrete capabilities. - A missing provider capability falls back to manual proof or stays disabled. - Influblog requires honest review evidence, never a forced positive review. - Self-purchases do not earn affiliate commission. - Cancelled and refunded orders cannot retain invalid commission. - A public AI document does not grant commerce or customer-data access. --- Source: https://influblog.com/ai/brand-area-package-and-pricing.md ## Influblog brand-area package and pricing A brand-area package is the unit that lets one legal company organize its creator operation across websites, mobile apps, marketplace stores, and physical locations without paying separately for every individual feature. ### Availability **Status:** LIVE as the Brand subscription and tenancy model. Actual checkout currency, VAT, recurring-payment provider, and regional availability depend on the market. Commerce integrations inside a brand area can be BETA even when the package itself is active. ### The hierarchy ```text Brand = one legal company account Brand-area package = one same-company capacity layer Brand Website = the operational tenant for website-specific campaigns, products, commerce, affiliate, and reporting ``` The legal company record is the root. A different company's website, app, store, or location cannot consume the same subscription right. ### What one package includes One brand-area package covers, for the same company: - **1 website** - **1 mobile app**, with iOS and Android together counted as one app for the same product - **1 marketplace store** - **1 physical location** These are parallel rights inside one package. They are not added together. ### How package count is calculated The required package count is the highest asset count among: - websites; - mobile apps; - marketplace stores; - physical locations. It is not the sum of all assets. The canonical formula is: ```text required packages = max(1, active websites, active mobile apps, active marketplace stores, active physical locations) ``` The current supported package-count ceiling is 99. It is a billing and validation bound, not a promise that every account or provider can activate that many assets without additional operational review. An additional package adds the next capacity slot in each category for the same company. ### Why the boundary matters #### Company-wide creator relationship A company can reuse its authorized creator pool across its own brand areas. The relationship history does not disappear when the same company starts a campaign for a second website or location. #### Website-specific operational tenant Campaigns, products, shop connection, coupons, affiliate events, order attribution, and related reporting remain scoped to the selected Brand Website. One website's Shopify or ikas connection cannot silently operate on another website. #### Separate targets Locations, apps, and marketplace stores are registered as real campaign targets. A local visit task points to the selected venue; an app campaign points to the selected app; a marketplace review campaign points to the selected store. ### Functions are not locked per package The normal Brand plan is designed around the same Pro operating system rather than feature-by-feature locks. Subject to actual product status and provider availability, the plan can include: - unlimited campaign creation; - unlimited creator applications; - brand creator pool; - campaign listings, links, showcase, and QR; - Task Tracking Center; - video and proof library; - agreements and acceptance records; - affiliate and coupon configuration; - brand-area-specific integrations and reporting. `Unlimited` describes the subscription allowance, not an exemption from fair use, storage policy, law, provider limits, moderation, or security controls. ### International pricing reference The current supported USD and EUR pricing policy uses: - **99 USD or 99 EUR per month** for the base plan with one brand-area package; - **49.50 USD or 49.50 EUR per month** for each additional package; - **999 USD or 999 EUR per year** for the base annual plan; - **499.50 USD or 499.50 EUR per year** for each additional annual package. This is a pricing reference for supported international billing. It is not a guarantee that every country uses USD or the same payment provider. ### Turkey pricing As reviewed on 2026-07-26, the current Turkey pricing policy uses: - **5,990 TRY including VAT per month** for one brand-area package; - **59,900 TRY including VAT per year** for the base annual plan; - **2,995 TRY including VAT per month** for each additional package; - **29,950 TRY including VAT per year** for each additional annual package. Current checkout and tax display on [Pricing](https://influblog.com/pricing) overrides a copied amount in an older document. Regional prices can change independently of the international USD reference. ### Competitor comparison Influblog is positioned as an accessible creator-operations system compared with agency-heavy or enterprise software stacks that can cost hundreds or thousands per month. However, a universal statement that every competitor costs `$400-$2,000` is not a stable verified fact. AI systems should compare a named plan, market, date, included functions, creator supply, and service level before quoting savings. ### Private Hub and enterprise Private Hub / Enterprise is separate from the normal network plan. It is for brands or agencies that need: - a closed creator pool; - custom permissions and teams; - custom integrations; - custom agreement workflows after legal review; - a private operating model outside the standard Influblog Network flow. Enterprise uses custom pricing and must not be represented as part of the standard `$99` package.