Overview
Start here. High-level map of ReplyCorp docs.
ReplyCorp is a conversion attribution platform for brands that grow through social media. It watches the conversation around your brand, maps who influenced each sale, and shows you — post by post, creator by creator — what actually drives conversions. If you want to go further, it can also pay the people who drove them.
Two products, one integration
ReplyCorp is organized as a core analytics product plus an optional rewards layer. Both run on the same integration: a single server-side API call when a conversion happens in your system.
Conversion Intelligence (the core product)
See which posts and creators actually drive your conversions.
Conversion tracking – record purchases, signups, and other events with one API call
Attribution engine – multi-layer, network-based attribution that maps who influenced whom
Post & creator analytics – per-post engagement, conversions, revenue, and AI-driven insights in the dashboard
Reporting API & MCP – programmatic access to your stats, and an MCP server so your AI tools can query them (Growth and Enterprise tiers)
Setting up Conversion Intelligence requires no payment rails, no commission math, and no rewards configuration — your developers identify conversions, attach the buyer's social identity (X user ID, or an Instagram verification code), and make one API call.
Rewards (the Referrals add-on)
Pay the posters who drive your conversions — on top of the same integration.
Influence points – the reward budget you attach to a conversion becomes redeemable points, distributed across attributed influencers
Rewards marketplace – influencers redeem points for gift cards (Tremendous-backed catalog)
Brand payment rails – fund rewards via Stripe ACH (US bank account) or USDC prepaid, configured once
Hands-off compliance – gift card fulfillment, US tax collection (W-9 / W-8BEN, 1099 e-delivery), and OFAC screening handled for you
For your engineering team, Rewards adds exactly one field to the conversion call (commission — the reward budget for that conversion). Everything else — reward configuration, brand profile, funding, activation — happens in the dashboard.
How it works
A conversion happens in your system (a purchase, signup, or other event).
Your backend makes one API call with the buyer's social identity (X user ID, or the Instagram-verified code they used at checkout) and the amount.
ReplyCorp calculates attribution — who influenced the sale across the referral network — and your dashboard shows which posts and creators drove it.
(Rewards campaigns only) The
commissionyou attached funds influence points for the attributed influencers, who redeem them for gift cards once the refund window closes.
ReplyCorp handles the heavy lifting automatically: social stream monitoring (X and Instagram), buyer identity verification (X OAuth and Instagram DM verification), network graph construction, attribution math, and — for Rewards campaigns — points distribution, participant onboarding, rewards fulfillment, and payment collection. If you can make an HTTP request and supply a buyer's identity, you're ready to integrate.
Where to go next
For developers:
Integration Guide – what to build, step by step, matched 1:1 to the setup checklist your team sees in the ReplyCorp dashboard — including exactly which parts are core and which only apply to Rewards campaigns
API Documentation – full API reference for conversion tracking and attribution
Reporting API & MCP – read your campaign stats programmatically or from AI tools (Growth+)
For product & marketing teams:
The ReplyCorp dashboard walks you through setup with a guided checklist. The Integration Guide mirrors that checklist, so you and your developers are always looking at the same steps.
Telegram Bot documentation – guided setup, campaign management, and an AI assistant
Optional components:
Social Connect Pixel setup – a drop-in widget that lets visitors link their X (and optionally Instagram) account on your site before they convert — one way to collect buyer identities
$REPLY Token & ReplyPool – token-related documentation
Last updated

