linkboo for peptide sellers

linkboo is a link-in-bio and link-routing platform with structural support for compliance, audit-log retention, and payment processor flexibility. This page describes how the platform applies to operators in the research-peptide retail category, including the operational features relevant to compliance reviews, processor transitions, and click-attribution.

Set up linkboo →

platform overview

linkboo is a neutral infrastructure tool. The platform handles the link-routing layer between a social-platform profile (bio link, post link, ad destination) and a downstream destination URL controlled by the operator. The platform does not host the operator's product catalog, transaction layer, or customer data; it routes the click and records the routing event.

The platform's primary technical feature is structural mitigation of the in-app browser logged-out problem documented across major social platforms. When a click originates inside a social-platform webview (Instagram, TikTok, Threads, X, Facebook, Snapchat, Pinterest, LinkedIn, Reddit, and other in-app browsers), the platform detects the webview from the user-agent string and routes the click out to the device's default browser (Safari on iOS, Chrome on Android) before the destination loads. The structural effect is that the destination receives the visitor in their default browser context, with the cookies and session state the destination expects.

audit logging

The platform retains structured audit logs of routing events. Logs are accessible via the operator's dashboard and via API. Each routing event records:

• The originating social platform (where the click came from), based on referrer headers and user-agent analysis
• The detected browser context (in-app webview type, or default-browser if not in a webview)
• The destination URL the click was routed to
• The timestamp of the routing event
• The geographic region (country-level), inferred from IP geolocation, not stored at IP-precision
• Whether the click required an escape from a social-app webview, and whether the automatic hand-off to the device's real browser succeeded or fell back to the one-tap manual prompt
• The user agent string

Log retention is configurable per workspace. The default retention is 13 months, which supports annual compliance review cycles common to operators in this category. Longer retention is configurable on paid plans. Logs are exportable in CSV and JSON.

The audit log is the primary record of where traffic was routed and from what context. Operators in this category commonly use audit logs as part of compliance documentation packages provided to payment processors, banking partners, and counsel.

payment processor flexibility

The platform does not process payments and does not have a direct dependency on any specific payment processor. The destination URL routed to is configurable by the operator and can be changed at any time without disrupting the upstream links (the linkboo URL the operator has put in social bios, ad destinations, and external content).

This processor-portability matters in this category. Operators commonly transition between merchant processors over time due to underwriting decisions or processor portfolio changes; transitioning a destination URL inside linkboo is a single configuration change at the platform level, not a re-paste of new URLs across every social profile and external placement. The linkboo URL stays the same; the destination it routes to is updated centrally.

attribution

The platform records click-source attribution per routing event. The operator's dashboard surfaces:

• Click volume per source platform
• Click volume per destination URL
• Click volume per link (where the operator uses multiple linkboo URLs for different campaigns)
• Detected-webview-share per source platform (the share of clicks that arrived in a social-app webview vs the device default browser)

The attribution layer is independent of the operator's destination-side analytics. The platform does not set or share cookies with the destination; the destination's own analytics (Google Analytics, server-side logs, processor-side attribution) operate independently and are unaffected by the routing layer.

acceptable use

This page is intended for operators whose business model complies with applicable law and with the terms of the platforms they advertise on and route traffic to. The platform's acceptable use policy is the document of record for category-eligibility, content restrictions, payment-routing restrictions, and routing-destination restrictions. Operators in any category should review the acceptable use policy before signup.

The platform applies the acceptable use policy uniformly. The policy is the single source of truth for what is and is not supported infrastructure use; it is not category-specific, not negotiated per operator, and applies identically across all signups.

signup

Signup is direct, no sales call, no underwriting interview at the platform level. The operator is responsible for ensuring their downstream destination, business model, and advertising comply with applicable law and with each social platform's terms.

Set up linkboo →

Direct any policy questions to the acceptable use policy.